Home Dashboard Directory Help
Search

Test Agent 2012 - mstest.exe - no longer working with Update 2 by opmet


Status: 

Closed


7
0
Sign in
to vote
Type: Bug
ID: 783438
Opened: 4/11/2013 5:58:34 AM
Access Restriction: Public
0
Workaround(s)
view
5
User(s) can reproduce this bug

Description



it seems the test agent got broken with update 2:

i have installed "Agents for Visual Studio 2012 with Update 2" (vstf_testagent.exe) on windows xp.

mstest.exe fails to execute unit tests because it cannot find "Microsoft.TeamFoundation.Client".

i can also see various assembly references to "Microsoft.VisualStudio.TeamSystem.*" failing.

it seems some files are missing in the installation.
Details
Sign in to post a comment.
Posted by Microsoft on 6/9/2013 at 10:40 PM
Hi,
The bug history shows 2 issues:
1. mstest not working in XP : This issues was fixed in VS 2012 Update 3 RC.
2. CUIT not working in XP: We are using https://connect.microsoft.com/VisualStudio/feedback/details/788809/ to track this one.

I am resolving this issue as fixed.
Posted by opmet on 6/4/2013 at 2:15 PM
hello?

this current ID 783438 is about a regression defect introduced with "update 2" and addressed with "update 3 (RC)".
the proper resolution status would be: accepted / reproduced / resolved / fixed!

the "windows xp" aspect mentioned in the previous comment is rather applicable for connect ID's 788833 and 788809.
Posted by Microsoft on 6/2/2013 at 4:39 AM
Hi Opmet,
Thank you for reaching out to us. We have taken a look and concluded that the issue only pertains to Windows XP. For VS 2012 and it's subsequent updates, Windows XP is not a supported OS.
Because of this, we are resolving this issue as by design.

Thanks!
Posted by opmet on 5/28/2013 at 1:44 PM
the symptom initially outlined in this topic looks like a defect that got introduced with test agent 2012.2:
mstest.exe no longer works in test agent "standalone" environments.

it seems this got fixed with test agent 2012.3 (RC1).


for the other symptom (specific to running coded UI tests) raised dedicated connect topic 788809:
https://connect.microsoft.com/VisualStudio/feedback/details/788809/
Posted by opmet on 5/14/2013 at 9:10 AM
we are talking about "windows XP".
there is no .NET 4.5 for windows XP.

just to clarify on the test assemblies in attached file "repro.zip":

1) they got _compiled_ with VS 2012.2 running on windows 7

2) i'm trying to _execute_ them on windows XP (with .NET 4.0 installed)
- test agent 2012.2 failed as it tried to load "Microsoft.TeamFoundation.Client" (which is not there).
- test agent 2012.3 (RC1) now fails because it tries to load "Microsoft.VisualStudio.TestTools.UITest.Extension.CrossBrowser" (which is not there).

i have also attached the solution's source files as "repro_src.zip".
Posted by Microsoft on 5/14/2013 at 8:13 AM
Hi,
Can you please ensure .NET 4.5 is installed on your machine?
Was CUITest01.dll working earlier in Update 2?

Thanks,
Vishnu
Posted by opmet on 5/8/2013 at 10:09 AM
i have just tried the first CTP (RC) of "Update 3" - which is not the RTM, yet.
the assembly "UnitTest01.dll" from attached file "repro.zip" now goes through fine.
however, for the assembly "CUITest01.dll" i'm getting the following exception:

Error calling Initialization method for test class CUITest01.CodedUITest1: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.TestTools.UITest.Extension.CrossBrowser, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)


Error calling Initialization method for test class CUITest01.CodedUITest1: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.TestTools.UITest.Extension.CrossBrowser, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
--- End of inner exception stack trace --- at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence) at System.Reflection.Assembly.LoadFile(String path) at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestExtensionPackageManager.LoadAssembly(String assemblyFile)

--- End of inner exception stack trace ---
    at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestExtensionPackageManager.LoadAssembly(String assemblyFile)

Posted by opmet on 5/6/2013 at 6:47 AM
will this be fixed with upcoming "Update 3"?
Posted by opmet on 4/25/2013 at 5:20 AM
thanks for the suggestion. however, the proposed workaround is invalid as Team Explorer 2012 won't install on windows XP ...
Posted by Microsoft on 4/25/2013 at 5:06 AM
Thanks for reporting this. Please note that the workaround is to install Team Explorer 2012, whereby mstest.exe will start working.
Posted by Microsoft on 4/15/2013 at 4:12 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by opmet on 4/11/2013 at 7:40 AM
note: everything is working fine with "update 1". this issue is a defect that was introduced with "update 2"!
Posted by Microsoft on 4/11/2013 at 6:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
repro.zip 4/12/2013 4 KB
repro.txt 4/12/2013 135 bytes
test_error.png 4/24/2013 8 KB
repro_src.zip 5/14/2013 7 KB