satish@msft https://docs.microsoft.com/archive/blogs/sathar/feed.xml Bits and bytes Wed, 17 Apr 2019 03:51:48 GMT en-US hourly 1 Running Coded UI Tests built using Visual Studio 2013 with Team Foundation Server 2015 https://docs.microsoft.com/archive/blogs/sathar/running-coded-ui-tests-built-using-visual-studio-2013-with-team-foundation-server-2015 Mon, 01 Aug 2016 00:00:56 GMT https://blogs.msdn.microsoft.com/sathar/?p=26 Recently some users have reported issues while executing tests using TFS 2015 for the projects built with Visual Studio 2013. The test execution fails with this error message:

 

2016-06-08T18:04:59.8268353Z ##[warning]DistributedTests: UnExpected error occured during test execution. Try again.

2016-06-08T18:04:59.8268353Z ##[warning]DistributedTests: Error : MSTestAdapter failed to discover tests in class 'TestProject.CodedUITest1' of assembly 'C:\TestDrop\CUITProject.dll'. Reason Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.CodedUITestFramework, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified..

 

Test execution is failing in this scenario because test execution engine is not able to resolve version 12.0 binaries (Visual Studio 2013) while executing tests in a 14.0 environment (TFS 2015).

 

As a workaround to this issue, add an 'app.config' file to your solution (See how to add app.config https://msdn.microsoft.com/en-in/library/ms184658.aspx) and update the contents of the file with the shared on OneDrive . The updated configuration files contain assembly redirects from version 12.0 to 14.0, which will make sure that the test agent machine is able to resolve the framework assemblies.

Check-in the updated configuration file into the source control repository and run the BDT scenario once again. The tests should run fine this time.

 

If the test execution again throws an error complaining version mismatch for some other assembly, add the assembly to the app.config file and retry.

]]> Executing tests remotely using Visual Studio 2015 with Test Controller and Test Agent 2013 Update 5 https://docs.microsoft.com/archive/blogs/sathar/executing-tests-remotely-using-visual-studio-2015-with-test-controller-and-test-agent-2013-update-5 Sun, 31 Jul 2016 23:43:51 GMT https://blogs.msdn.microsoft.com/sathar/?p=25 Unable to cast transparent proxy to type 'Microsoft.VisualStudio.TestTools.Controller.IControllerExecution' Visual Studio 2015 fails to execute the tests remotely with Test Agent and Test Controller 2013 because it is not able to cast remote object due to different assembly versions of Visual Studio and Test Controller.  Users can perform the following steps on the machine with Visual Studio 2015 as a workaround to get unblocked:
  1. Navigate to the directory path '%systemdrive%\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow'.
  2. Make a backup of TE.ProcessHost.Managed.exe.config
  3. Replace the original file with the file shared on OneDrive.
  4. Restart Visual Studio 2015
**Note: For a x64 project, update TE.ProcessHost.Managed.exe.config present in '%systemdrive%\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\x64' directory. After completing the above steps, remote test execution using Visual Studio 2015 with Test Controller and Test Agent 2013 should run fine. This issue is fixed in Visual Studio 2015 Update 3.]]> Hello world! https://docs.microsoft.com/archive/blogs/sathar/hello-world Fri, 22 Jul 2016 06:21:58 GMT https://blogs.msdn.microsoft.com/sathar/?p=1 Developer Network. This is your first post. Edit or delete it, then start blogging!]]>