{"id":13851,"date":"2016-03-31T07:39:24","date_gmt":"2016-03-31T07:39:24","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=13851"},"modified":"2019-02-14T17:34:10","modified_gmt":"2019-02-15T01:34:10","slug":"executing-automated-tests-in-build-vnext-using-test-plan-test-suites","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/executing-automated-tests-in-build-vnext-using-test-plan-test-suites\/","title":{"rendered":"Executing Automated tests in Build vNext using Test Plan, Test Suites"},"content":{"rendered":"

With Sprint 97 deployment on VSTS, users who have\u00a0invested in planned testing using Test Plan, Test Suites can trigger automated runs in Build vNext. This functionality has been added to the Run Functional Tests task (formerly called Run Tests using Test Agent) as shown below. This functionality is also shipping\u00a0in\u00a0Team Foundation Server\u00a02015 Update 2.\u00a0If you are new to testing in Build vNext, please see https:\/\/msdn.microsoft.com\/en-us\/library\/vs\/alm\/test\/continuous-testing\/continuous-testing<\/a>.<\/p>\n

\"RunFunctionalTestsTaskwithTestPlanOption\"<\/a><\/p>\n

Existing ‘Lab Build and Test’\u00a0workflow users will find the settings in the task familiar to the\u00a0Test section of the workflow. Once you choose Test Selection to be Test Plan, choose the Test Plan from which you want to run your tests. You can then select one or more test suites from a Tree view control followed by a Test Configuration.<\/p>\n

\"TestSuiteTreeControl\"<\/a><\/p>\n

In the Lab Build and Test workflow, you would choose a Test settings file that was stored in MTM. There were issues with this approach, including the fact that you could not use the same settings file to run tests in your IDE and your BDT workflow.\u00a0With Build vNext, we are enabling you to specify runsettings or testsettings file from the source code repo or from disk.<\/p>\n

That’s it. You\u00a0can queue your\u00a0Build Definition and your automated\u00a0tests from the suites selected will be run. Test results can we viewed in the same way as\u00a0results from Assembly based execution – in the Tests tab of the Build Summary page.<\/p>\n

\"TestsSummary\"<\/a><\/p>\n

To see the results per Test Suite, just select “Test Suite” in the “Group by” drop down<\/p>\n

\"GroupBy<\/a><\/p>\n

Clicking on a Test Suite name will navigate you to the Test Hub where you can see the Test Plan, Test Suite and Test Cases and\u00a0the history of test case results<\/p>\n

\"TestHub\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

With Sprint 97 deployment on VSTS, users who have\u00a0invested in planned testing using Test Plan, Test Suites can trigger automated runs in Build vNext. This functionality has been added to the Run Functional Tests task (formerly called Run Tests using Test Agent) as shown below. This functionality is also shipping\u00a0in\u00a0Team Foundation Server\u00a02015 Update 2.\u00a0If you […]<\/p>\n","protected":false},"author":176,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13851","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"acf":[],"blog_post_summary":"

With Sprint 97 deployment on VSTS, users who have\u00a0invested in planned testing using Test Plan, Test Suites can trigger automated runs in Build vNext. This functionality has been added to the Run Functional Tests task (formerly called Run Tests using Test Agent) as shown below. This functionality is also shipping\u00a0in\u00a0Team Foundation Server\u00a02015 Update 2.\u00a0If you […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/13851","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/176"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=13851"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/13851\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=13851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=13851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=13851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}