In TFS 2013 I have Build A which compiles and runs unit tests. I also have Build B which deploys to a dev server. How can I start build B when Build A succeeds in TFS 2013?
You create a custom Workflow, Download the build Definition and then add the "Start Build"-Activity. Choose your build-workflow in the build-definition and voilà
Related
We work with TFS 2015 and it works really great. We have two different build sets one for our production environment and one for our test environment. We also use CI. Our current workflow is that we "Queue build..." and then everything is done automatically.
What we would like to accomplish on our production build is one of the following:
On "Queue build..." the person has to acknowledge the build or
You have to somehow start the queue manually, so the queue build doesn't start automatically
Don't use builds for deployment. If you're on TFS 2015 RTM or Update 1, upgrade to TFS 2015 Update 2 (or, ideally, TFS 2017 Update 1). Starting in TFS 2015 Update 2, there is a Release hub that has exactly the kind of capabilities you're asking for. It allows you to define a release pipeline for the binaries generated by a build, where you can put optional approval requirements in place prior to a deployment occurring on a given environment.
In our project we have Unit tests specific to VS2013 and VS2015.We have a requirement of using one build definition (Virtual machine) to run both VS2013 and VS2015 Tests on different timings.
I have installed on that VM Team Foundation Server 2015 Console and created one controller and 2 agents(each for specific version of visual studio).
We are using 2013 build template.
I have ran successfully 2015 UTs on that Virtual Machine(VM) but when I try to run VS2013 specific UTs it is picking up 2015 vstest.exe and throwing exception.
Is there any way to achieve this??
I tried to include MTest Activity build template.Activity is running but it is saying no tests to execute.
I even tried to run throught batch file invoke,this way it is running but through MSTest Activity it is not running scripts.Below is snapshot of TFS log for MSTEST activity
By default, TFS calls the corresponding version of VS to run tests. There is no way to specify the VS version for a test in XAML build with default build process template. You would need to customize your build process template by adding InvokeProcess activity to invoke 2013 vstest.exe to run tests.
Since you are using TFS 2015, I'd like to suggest you use new build system, which is tasks based. In new build system, you can add Visual Studio Test task to run tests. In this task, you can specify VSTest version:
Check this article for more information: https://www.visualstudio.com/en-us/docs/test/continuous-testing/getting-started/getting-started-with-continuous-testing
I have a visual studio loadTest project and LoadTest2010 result database, when I run the test from visual studio then test work fine and test data save in the LoadTest2010 DB but when run the test from VNext then test run fine (did all the configurations) but data does not save in the DB LoadTest2010.
In VNext VsoAgent agent is running the test.
Did any one face this issue?
vNext is TFS Test Agent and it is VS2015 Test Agent, we ever used Test Controller and Test Agent for VS2013 Update5. vNext is Test Agent for VS2015.
According to your description, whether you have added a web test project in load test, if no, please make sure you have added it.
and then please use MSTest to run load test locally to see the results.
What test steps do you use in your build definition? If you use the steps Visual Studio Test Agent deployment and Run functional test to run your load test, it may get the result like you posted above. Because these 2 steps are using VS Test agent 2015 and if you want to run load test, you need to install VS Test Agent 2013 according to this document.
So about using the VS 2013 test agent in Vnext build, you could follow the step below:
Add a test setting file for your test solution.
Next, specify test controller and Load test result store in the setting file.
Then add a Visual Studio Test step in your build definition and in this step, remember to specify the testsetting file.
this is the only one option right now in the VNext to run the loadtest and data will save to the loadtest database. Below is the snapshot from VNext
Is there a way to run xUnit tests for UWP with TFS 2015 vNext build?
I try to do it with my local build Agent with it running in interactive mode.
When test needs to be done, the UWP test app runs but no tests discovered.
Is it supported to run this tests?
Yes, assuming you have installed xunit via Nuget and your packages are at the root level of your sources folder, you just need to set the Path to Custom Test Adapters to your packages folder.
In my case: $(Build.SourcesDirectory)\packages - adjust as you need to.
On my tfs if I select the default template (tfvstemplate.12.xaml).
I wan't to run mstest for my unittest's but i can't select a other test runner
I have installed tfs 2013 and visual studio ultimate 2013.
The selection field is just disabled
In the 2013 build template Microsoft has defaulted to the new Agile Test Runner and no longer supports the selection of the old test runner for 2013 (12.0) templates.
When you select a 2012 or 2010 build template (10.0 or 11.0), Team Build will still run using the MsTest runner. If you customize the 2013 template to use the old Run Tests activity it will still run tests using the MsTest runner. You need to run these older templates against a Team Build server that's still running Team Build 2010 or 2012.
The new Test Runner can execute MsTest based tests, but doesn't support the old Test Settings files. Instead it uses the new Run Settings files instead. The next version of TFS and Team Build will most likely drop support for the old test runner completely.