Recommended Tests is not displaying expected results

Question

We have setup TFS along with a VM environment utilizing Lab Mgmt.  We have setup many environments with 2 Web Servers, a Database server.  We've setup sucessfully all build agents, test agents and lab agents on these environments.  We are able to successfully automatically build and deploy our application. 

We are now trying to use the Recommened test feature.  We've setup a new Test Setting that includes Test Impact on all the servers and the ASP.Net Clien Proxy for Test Impact on the local role.

When I run MTM locally on my own machine connecting to the actual environments, I am able to generate the test impact file fine.

Its called "eviti Web Server.testimpact.xml"

It looks like the xml marked as "Sample - Regular Manual Tests w/Test Impact" below.

When I change the code related to this test case, check in and run a build, the recommended tests is empty. 

Whats wrong?  I'm out of ideas.  The warning file does not show any errors related to the server in question.  I'm getting errors for other servers because I didn't execute any code on those servers.  Besides that I'm not getting anything out of the ordinary.

<?xml version="1.0" encoding="UTF-8"?>
-<Test AutomatedTestId="00000000-0000-0000-0000-000000000000" TestCaseId="7172" IsTestCase="true" Name="Sample - Regular Manual Tests w/Test Impact - Env 2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> -<Signatures> <Signature>E28EDF7EB2D7BAA0EFC32E4940228B0D8FCF1D1F</Signature> <Signature>9F505477E14AE0EE0A0DDC4239B6A3E3C0BCB552</Signature> <Signature>2986183AB4B54A57211483A041799BF28D9BCEAF</Signature> <Signature>F9D2B139C6CACB3DE9E3071E76F31B7428E42407</Signature> <Signature>F2B055B6164ACDFB1512A9A914268174407D8D0D</Signature> <Signature>CB5F482B073CB3DFC27DC70C18DE8C03FA6834A4</Signature> <Signature>0CF62FC0FA6E96F6FE400CCB8F6AEAC4CDEF5B49</Signature> <Signature>E588C654FBC2984756BB25A6955A844B7275CAD3</Signature> <Signature>E2107B887F987C61C1E2A8882EB72CFC2C39E4A9</Signature> <Signature>A2BE3F37310C874E586718057DC10490AC489200</Signature> <Signature>826F41B61DE71F9A1B130B035513024920D37F8A</Signature> <Signature>C396052B2CC6A09A228CFDB05F28B43B19D2A2C4</Signature> <Signature>0EF0F3A1A9B480885DC354B016331DF1CED5E86B</Signature> <Signature>B938C82BA2F40C7F88AFC4A0E027EE25FE53EED9</Signature> <Signature>4D7757894F9E0AC7126F0BBD18F7A69B3555E4F4</Signature> <Signature>FFD9D49645F71EAD8E9BA54FB7B7540D38228105</Signature> <Signature>9DF99383ED5FDDF729DCE59E94116F9DAD583948</Signature> <Signature>7E07E8396953DE4B4889040B1EC809FD3FF6B50B</Signature> <Signature>C5FA4F20AB175806092719A8580214AA73042FFE</Signature> <Signature>8260A4BEAD79919FF91AFDF1D4D2C12DB92C9C4D</Signature> <Signature>7286938BFB63EF32B1F3C1685515289D99E5A639</Signature> <Signature>0D10F0BB754B7BB724B2DE95057615B5B204E4F1</Signature> <Signature>928387A731E1E3134D2F383F7A64B23050F22BBA</Signature> <Signature>6C7751EE73BCB7C1DF3A709E7403D8D547A0EFCF</Signature> <Signature>B504D4CE2918CE456E96517E0396264F3953FB37</Signature> <Signature>F5C8F50C3CE00575371FC87DC7F4AB05278046FA</Signature> <Signature>93636E5985FB10A00182FAC2265F144D4590879E</Signature> <Signature>2BB7F10BADB97356BF20006763987EF34BC39F77</Signature> <Signature>92B189C6108EFFDBDF69BCCB2D6F41F5F26AF389</Signature> <Signature>B5D973C703E04D0EA87A93D64A8F09F495DFC8B6</Signature> <Signature>D6E2F5FC74258C5E6A5828E5FB8BDCFE62AE32C2</Signature> <Signature>FB53601D34DE1A5952A921F38C703D2975DEE076</Signature> <Signature>9623A8493B6023B477139C47BB48AF6050ABA201</Signature> <Signature>0970C73435A81D537AD16C7BA6E76157BFEC8DA1</Signature> <Signature>DC5BE9236749CEA33DDF640DEBBEE325FD3998F2</Signature> <Signature>7AAD200AD63C630DACF23AA3C09D44FB03F985D8</Signature> <Signature>F83DBE587C5591B2EA9A0F2E9861587A2D1C01B7</Signature> <Signature>8798B583F248E99C44FD5728D7E77AA7FB2A512B</Signature> <Signature>FC85FA783DCC0177E6AB394E4649A46FF0D09601</Signature> <Signature>14DAE27ACC05E7B1EED21F7443B95F4249A17C3C</Signature> <Signature>058F05007F06CF0DA391997234D412419E5E8E0F</Signature> <Signature>B67A482756A993F4665ED4E5459783A5A15EE860</Signature> <Signature>7A9DFD76EA289D03A83D04CE17AF51F5394927DE</Signature> <Signature>DDF1BF683E6C23AB6DC7C87FB43515FB81561981</Signature> <Signature>A457759CC1A8724CB90431D83D8E7BB2E5BF1CCE</Signature> <Signature>F143E17283C342BDF6F0BA597E148A9D6884124C</Signature> <Signature>1BA416B8045455C91C06E06058A161A2F122D903</Signature> <Signature>93EE113DA2F8C7B6733ADC775787986A36A1F91E</Signature> <Signature>D034A1603905795610E7564E17A9A136ED359676</Signature> <Signature>25EC76F851BAB1D2E14B77416A2555432847578D</Signature> <Signature>BE49971DD95386B47CBA2272EE35472E31F9DD47</Signature> <Signature>CEBFC4DE2ABEE8E2D6AB4CF55351AD42E06CFA78</Signature> <Signature>C0B0672E7B69701C8E5B3C3F91EBED233141E7C2</Signature> <Signature>92E22629F07CAE3376133529A1F56FB179F329E8</Signature> <Signature>C1742BECB43C174B625A9F6A333CDD6598F94B1B</Signature> <Signature>9E5248B1BDB4C410C3E538929ECF9619E6152C14</Signature> <Signature>830E5B9A3EDFAAFAF6EA6A25DE204110DF72A4BD</Signature> <Signature>C50A35100DD6ABF7E0AB9DF9340748240A3CD71B</Signature> <Signature>9DF803D51C4FF7A0DC9BDA3B03A18A14C74015F1</Signature> <Signature>528B65D12BFD5B58B0627ED5B2F340A2EC5AC77F</Signature> <Signature>CEE59B12E663E17A57CCEE260F673DA6934AD24A</Signature> <Signature>67B1B200D4C386B2B0803706AAEE0C0F35957DCF</Signature> <Signature>39D571421B4CBD35DC68ED688C6FAAC738F27B60</Signature> <Signature>D8F6DAB7182DFCCEA20C66B2B23920BAA944B16D</Signature> <Signature>CBB7345AE0FAA78C78F6E15A50C6307777F4E3E2</Signature> <Signature>51D366BFE5BE8B649D5760CBBDF420EEDEB6FF1F</Signature> <Signature>D07F6E4A3A72C2C13023DC89A3A242FD2DF2B1FB</Signature> <Signature>7E621F855D363BF742A4D1362A4FD53DE5EFE8A5</Signature> <Signature>50A705DEA11D3856881E3016E4FD55B775EC1249</Signature> <Signature>152A717EC725E16C0AA6534CF6D510C65A36F6B0</Signature> <Signature>BDC45238321C470FF4BFB435441E1DC158C2873C</Signature> <Signature>37410DEA53C714919691493204C427B56A98F04B</Signature> <Signature>6B646B7035AD9501D3A6B6C4DEDC50BF6323F659</Signature> <Signature>1538E7BDF0490ECB81F566E37394454ACA14405B</Signature> <Signature>6EA02F75B646BDE8D2730F6CA89ABE1544FC750B</Signature> <Signature>A9E47366AA378E20FD56A9A9E9D1ADC6616F2E5D</Signature> <Signature>A66903AA877A26991F4A106FDB9EEAC5A51A9AB4</Signature> <Signature>8EF4C62CD846CB01CEF8E211DA6C96D9DEBD1378</Signature> <Signature>E69643C5D927ADC4ABE1BDA3F81252A60B3B8DCB</Signature> <Signature>AC689A06D01FFE014E1FB8628778141B4090B020</Signature> <Signature>1728C61E4FBBCC2EBFD799E37A4D91DEC35BD8D8</Signature> <Signature>04446C0370E6C3C851A70F635671721635A2FC69</Signature> <Signature>A0F40250F463CD0552CF295EDABBE252E255EFE1</Signature> <Signature>52E84A0243E343F6E95F34897C4C244A9570942A</Signature> <Signature>CD66BA541A7A62441700922E1EDEF44219C64605</Signature> </Signatures> </Test>

---

-Ivan R. Perez

Answer 1

Hi,

The recommended tests for the runs from MTM are the functional tests.

The recommended tests in the build which uses DefaultTemplate.xaml are the unit tests. So if you have any unit tests and the corresponding code changes, you should see those in the recommended tests on the build output.

See http://geekswithblogs.net/jakob/archive/2009/06/04/vsts-2010-enabling-test-impact-analysis.aspx

Thanks,

Anuj

---

http://www.anujchaudhary.com/

Answer 2

Ok,

So in MTM we are not seeing our manual test run from the above test case to show up as a recommended test.  This should show up correct?

 

We are more concerned with MTM's manual test runs, not unit tests at the moment.

Any info on this?

 

MSFT any help would be great!

---

-Ivan R. Perez

Answer 3

Are you using a physical/virtual environment. You will need that for collecting test impact data.

You can then follow the steps at http://msdn.microsoft.com/en-us/library/dd286589.aspx

Thanks,

Anuj

---

http://www.anujchaudhary.com/

Answer 4

We are using a virtual environment that is hooked up with Lab Mgmt.

We have installed and configured Test Agent, Lab Agent, Build Agent.

With MTM, the environment is listed as ready for test and workflows.

We have configured a TestSetting to collect Test Impact data for the servers and the local role is setup to collect via the ASP.Net Client Proxy for Test Impact & Intellitrace.

When we run the test case, we get a file called "eviti Web Server.testimpact.xml" as shown above.  Is this not the data collected?

Example:

<?xml version="1.0" encoding="UTF-8"?>
-<Test AutomatedTestId="00000000-0000-0000-0000-000000000000" TestCaseId="7172" IsTestCase="true" Name="Sample - Regular Manual Tests w/Test Impact - Env 2" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> -<Signatures> <Signature>E28EDF7EB2D7BAA0EFC32E4940228B0D8FCF1D1F</Signature> <Signature>9F505477E14AE0EE0A0DDC4239B6A3E3C0BCB552</Signature> <Signature>2986183AB4B54A57211483A041799BF28D9BCEAF</Signature> <Signature>F9D2B139C6CACB3DE9E3071E76F31B7428E42407</Signature> <Signature>F2B055B6164ACDFB1512A9A914268174407D8D0D</Signature> <Signature>CB5F482B073CB3DFC27DC70C18DE8C03FA6834A4</Signature>

....

What are we missing?

 

---

-Ivan R. Perez

Answer 5

Hello?  Is anyone there from MSFT?

---

-Ivan R. Perez

Answer 6

I am having this exact same problem, has anyone figured out what is wrong?

Scott

Answer 7

In our case, we had all the settings correct.  However, we were overloaded with attachments in the database.  All the test data that was recorded in the last two years made our database huge.  So we cleaned it out with the TFS attachment cleaner. 

Now we did it not for this effort, but because we were running out of disk space.  And after we did that we noticed that this feature started to work. 

Go figure.

---

-Ivan R. Perez