{"id":3863,"date":"2012-11-27T10:54:00","date_gmt":"2012-11-27T10:54:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2012\/11\/27\/integrating-existing-testing-systems-with-microsoft-test-manager-team-foundation-server-and-visual-studio\/"},"modified":"2019-02-14T17:57:53","modified_gmt":"2019-02-15T01:57:53","slug":"integrating-existing-testing-systems-with-microsoft-test-manager-team-foundation-server-and-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/integrating-existing-testing-systems-with-microsoft-test-manager-team-foundation-server-and-visual-studio\/","title":{"rendered":"Integrating existing testing systems with Microsoft Test Manager, Team Foundation Server and Visual Studio"},"content":{"rendered":"

I have been working with different partners in the testing space for the last couple of months and a frequently asked question is: <\/p>\n

\n

\u201cWhere do we start integrating our test tools with the Microsoft application life cycle platform?\u201d<\/em><\/font><\/p>\n<\/blockquote>\n

And the answer is relatively straight simple<\/p>\n

\n

\u201cYou need to integrate yourself into the development workflow\u2026we use Team Foundation Server for that ALM workflow engine\u201d<\/em><\/font><\/p>\n<\/blockquote>\n

Unfortunately simple doesn\u2019t always mean comprehensible\u2026so I typically go on to say: <\/p>\n

\n

\u201c\u2026So that you can your tests run as part of the build process \u2013and let the development team know if the tests passed\/failed\u201d<\/font><\/em><\/p>\n<\/blockquote>\n

\u2026At this point the light comes on and the question usually becomes:<\/p>\n

\n

\u201chow do I do that?\u201d<\/em><\/font><\/p>\n<\/blockquote>\n

A generalized pattern for a tool targeting a manual test team might be: <\/p>\n

    \n
  1. File bugs from your IDE into TFS \u2013 if you can extend the existing IDE <\/li>\n
  2. Create Test Cases in TFS <\/li>\n
  3. Create a Tests type in Visual Studio that knows how to execute your existing tests <\/li>\n
  4. Set the newly created Visual Studio Tests to be executed during the automation testing <\/li>\n<\/ol>\n

     <\/p>\n

    Below i list a couple of ways of achieving these steps: <\/p>\n

    Step1. File bugs from your IDE into TFS<\/font> <\/font><\/font><\/font><\/p>\n

    This is very straightforward and I have covered it in the post: <\/p>\n

    Notepad for Workitems: how to programmatically create workitems in Visual Basic for Team Foundation Server 2010<\/a><\/p>\n

    <\/font><\/p>\n

    Step2. Create Test Cases in TFS<\/font><\/p>\n

    This is just pretty much the same thing as the TFS Notepad \u2013 but instead of a bug it is a test case. <\/p>\n

     <\/font><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>static<\/font><\/span> <\/span>ITestManagementTeamProject<\/font><\/span> GetProject(<\/span>string<\/font><\/span> serverUrl, <\/span>string<\/font><\/span><\/font> project)<\/font><\/span><\/font><\/p>\n

            <\/font><\/span>{<\/font><\/font><\/span><\/p>\n

               <\/font><\/span><\/span>TeamFoundationServer<\/font><\/span> tfs = <\/span>new<\/font><\/span> <\/span>TeamFoundationServer<\/font><\/span><\/font>(serverUrl);<\/font><\/span><\/font><\/p>\n

               <\/font><\/span><\/span>ITestManagementService<\/font><\/span> tms = tfs.GetService<<\/span>ITestManagementService<\/font><\/span><\/font>>();<\/font><\/span><\/font><\/p>\n

              <\/font><\/span><\/span>return<\/font><\/span><\/font> tms.GetTeamProject(project);<\/font><\/span><\/font><\/p>\n

            <\/font><\/span>}<\/font><\/font><\/span><\/p>\n

     <\/font><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>private<\/font><\/span> <\/span>void<\/font><\/span> Button_Click_1(<\/span>object<\/font><\/span> sender, <\/span>RoutedEventArgs<\/font><\/span><\/font> e)<\/font><\/span><\/font><\/p>\n

            <\/font><\/span>{<\/font><\/font><\/span><\/p>\n

                <\/font><\/span><\/span>string<\/font><\/span> serverurl = <\/span>"http:\/\/localhost:8080\/tfs"<\/font><\/span><\/font>;<\/font><\/span><\/font><\/p>\n

                <\/font><\/span><\/span>string<\/font><\/span> project = <\/span>"Training1"<\/font><\/span><\/font>;<\/font><\/span><\/font><\/p>\n

                <\/font><\/span><\/span>ITestManagementTeamProject<\/font><\/span><\/font> proj = GetProject(serverurl, project);<\/font><\/span><\/font><\/p>\n

                <\/font><\/span><\/span>ITestCase<\/font><\/span><\/font> tc = proj.TestCases.Create();<\/font><\/span><\/font><\/p>\n

                <\/font><\/span>tc.Title = <\/font><\/span>"Training1"<\/font><\/span><\/font>;<\/font><\/span><\/font><\/p>\n

                <\/font><\/span>tc.Save();<\/font><\/font><\/span><\/p>\n

            <\/font><\/span>}<\/font><\/font><\/span><\/p>\n

    <\/font><\/p>\n

    Step3. Create a Tests type in Visual Studio knows how to execute your existing tests<\/font><\/p>\n

    This step is probably the most work as you will need to create a wrapper for the existing test execution engine so testers using the Microsoft test tools can interact and get the results of the test being run. <\/p>\n

    In the example below I am just shelling out to and checking for return\u2026Hoping anything done in the wild will be a little more sophisticated than this!<\/p>\n

    \n

    Imports<\/font><\/font><\/span> System.Text<\/font><\/span><\/font><\/p>\n

    Imports<\/font><\/font><\/span> Microsoft.VisualStudio.TestTools.UnitTesting<\/font><\/span><\/font><\/p>\n

     <\/font><\/font><\/span><\/p>\n

    <<\/font><\/span>TestClass<\/font><\/span>()> <\/span>Public<\/font><\/span> <\/span>Class<\/font><\/span> <\/span><\/font>UnitTest1<\/font><\/span><\/font><\/span><\/p>\n

     <\/font><\/font><\/span><\/p>\n

        <\/font><\/span><<\/font><\/span>TestMethod<\/font><\/span>()> <\/span>Public<\/font><\/span> <\/span>Sub<\/font><\/span><\/font> TestMethod1()<\/font><\/span><\/font><\/p>\n

            <\/font><\/span><\/span>Dim<\/font><\/span> p <\/span>As<\/font><\/span> <\/span>New<\/font><\/span> System.Diagnostics.<\/span><\/font>Process<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>‘ \/\/ Redirect the output stream of the child process.<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span>p.StartInfo.UseShellExecute = <\/font><\/span>False<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span>p.StartInfo.RedirectStandardOutput = <\/font><\/span>True<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span>p.StartInfo.FileName = <\/font><\/span>"c:mobiletestermobiledevicetester.exe"<\/font><\/span><\/font><\/p>\n

            <\/font><\/span><\/span>‘\/\/ The line above just shows how you could launch ANYTHHING<\/font><\/span><\/font><\/p>\n

            <\/font><\/span>p.Start()<\/font><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>‘\/\/ Do not wait for the child process to exit before<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>‘\/\/ reading to the end of its redirected stream.<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>‘\/\/ Read the output stream first and then wait.<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>Dim<\/font><\/span> output <\/span>As<\/font><\/span> <\/span>String<\/font><\/span><\/font> = p.StandardOutput.ReadToEnd()<\/font><\/span><\/font><\/p>\n

            <\/font><\/span>p.WaitForExit()<\/font><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>If<\/font><\/span> <\/span>CType<\/font><\/span>(output.ToString, <\/span>Integer<\/font><\/span>) = 2 <\/span><\/font>Then<\/font><\/span><\/font><\/span><\/p>\n

                <\/font><\/span><\/span>Assert<\/font><\/span>.Fail(<\/span>"Test Failed"<\/font><\/span><\/font>)<\/font><\/span><\/font><\/p>\n

                <\/font><\/span><\/span>‘At this point consider automatically filing a bug <\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>Else<\/font><\/span><\/font><\/span><\/p>\n

            <\/font><\/span><\/span>End<\/font><\/span> <\/span><\/font>If<\/font><\/span><\/font><\/span><\/p>\n

        <\/font><\/span><\/span>End<\/font><\/span> <\/span><\/font>Sub<\/font><\/span><\/font><\/span><\/p>\n

     <\/font><\/font><\/span><\/p>\n

    End<\/font><\/font><\/span> <\/span><\/font>Class<\/font><\/span><\/font><\/p>\n<\/blockquote>\n

    After the Test is created you will want to make it available as a template.  <\/p>\n

    This way testers and Automation engineers won\u2019t have to manually add a bunch of references or paste in blocks of code\u2026luckily we make this pretty straight forward. <\/p>\n

     <\/p>\n

    Note: Anna Russo has done a better sample using the generic test; please see: <\/p>\n

    http:\/\/visualstudiogallery.msdn.microsoft.com\/ef313348-8fd1-463b-9404-7472db99fda5<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

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

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

     <\/p>\n

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

     <\/p>\n

    Step4. Set the newly created Visual Studio Tests to be executed during the automation testing <\/font><\/p>\n

    In step 2 you created a Test Case- but how do you get it to execute your Visual Studio created in step 3?   <\/p>\n

    Turns out there are a couple of ways to do this; using Visual Studio, import the test cases using TCM finally and probably the method our partners and ISV will want to use programmatically. <\/p>\n

    Here are the directions for each: <\/p>\n

    1.  How to: Associate an Automated Test with a Test Case<\/a> <\/p>\n

    2. tcm: Importing Automated Tests into Test Cases<\/a><\/p>\n

    3. How To: Associate automation programmatically<\/a><\/p>\n

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

     <\/p>\n

    For its worth, in Microsoft Test Manager \u2013 there is a tab called \u201cAssociated Automation\u201d but it is intended to show testers which tests were set to run during automation and therefore is read only. <\/p>\n

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

    I have been working with different partners in the testing space for the last couple of months and a frequently asked question is: \u201cWhere do we start integrating our test tools with the Microsoft application life cycle platform?\u201d And the answer is relatively straight simple \u201cYou need to integrate yourself into the development workflow\u2026we use […]<\/p>\n","protected":false},"author":81,"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-3863","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"acf":[],"blog_post_summary":"

    I have been working with different partners in the testing space for the last couple of months and a frequently asked question is: \u201cWhere do we start integrating our test tools with the Microsoft application life cycle platform?\u201d And the answer is relatively straight simple \u201cYou need to integrate yourself into the development workflow\u2026we use […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3863","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\/81"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=3863"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3863\/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=3863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=3863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=3863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}