The test agent being used does not support the feature to execute tests by selecting Test Suite(s)

Scenario: You are trying to execute tests using the “Run Functional Tests” task, in a vNext build. Under Test Selection, you have chosen “Test Plan”, and have provided the plan and suite details, as indicated below.   However, the test execution fails with the below message: “The test agent being used does not support the…


Test execution failing when a Data-Driven test methods is referring parameter values from a test case WorkItem

Recently we are getting cases, where users get the below error when a data-driven test method is referring parameter values from a test case WorkItem. Test execution failure error: The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this error, see “Troubleshooting Data-Driven…


Build association with work Items in vNext

When switching from XAML to vNext, I realized the newer build model doesn’t update Global List. Old XAML builds enabled a work flow where work items were created on build failure and then updated those work items, associated with check-ins on successful builds. I couldn’t find a similar feature happening out of the box on…


vNext Build fails with error message ‘Cannot find solution’ because it does not exist.

Issue Recently we have seen some cases where a vNext build, when queued, would fail with a message like below: · Cannot find path ‘<build agent working folder>\<team project name>\path to solution> because it does not exist. ·        MSBUILD : error MSB1009: Project file does not exist. ·        Unexpected exit code received from msbuild.exe: 1…


Building ClickOnce apps using build vNext

We had earlier posted a blog that explains how to build ClickOnce applications using XAML build definition http://blogs.msdn.com/b/tfssetup/archive/2015/09/15/build-and-publish-a-clickonce-app-using-team-build-vso.aspx Based on popular demand, we’ll now see how to build ClickOnce Apps using Build vNext, on-prem/VSO First, create a new build definition of Type vNext. We have two steps – Visual Studio Build and Publish Build Artifacts…