Forum Discussion
Additionally:
Running TestComplete Tests Remotely with Visual Studio Test Agents
Test Controller
Test agents for Visual Studio 2015 do not support running functional tests remotely from Visual Studio. To run tests, use test controllers and test agents for Visual Studio 2013. You can find more information on it in the MSDN Library.
-
Microsoft Test Controller for Visual Studio 2013.
-
TestComplete 12 (or TestExecute 12).
-
TestComplete 12 Visual Studio Integration Package.
The Integration Package installer is shipped along with TestComplete. You can find it in the TestComplete folder after installing the product:
<TestComplete 12>\VS Integration\VSIntegration.exe
Run this installer after installing TestComplete on the test controller machine. In the installation wizard, select Build and Test Integration or Test Agent Integration feature appropriate for your test controller version.
I'm facing the same message - under certain circumstances:
I have VS 2013 and the VSO agent installed on the test server, as downloaded from http://{your_server}:8080/tfs/_admin/_AgentPool (in TFS 2015).
Now there's two scenarios:
1)
- I can run the agent using the runAgent.cmd on the test server, (and can even close the RDC window via "tscon 1 /dest:console" to keep the user session open (if I just close RDC, GUI tests will fail).).
- I start the TFS build
- TFS deploys the test agent on the test server
- I can start batch scripts from TFS that call msTest.exe on the .tc12Test file I got from integration of TC into VS 2013.
- I can also use the build step "visual studio test" to test the .tc12Test assemblies.
- The tests run, and produce a .trx file I can use with the TFS extension
-> I tend to assume I meet the requirements for running TestComplete tests remotely with Visual Studio Test Agents
2)
- I use the task scheduler to call runAgent.com on system start with highest privileges
- I reboot the test server
- I start the TFS build
- TFS deploys the test agent on the test server
- upon either running those batch scripts, or the "visual studio test" build step, I will get the message mentionned in the first post.
I do not quite understand the difference...and hope to help with the OPs problem.
- AlexKaras7 years agoChampion Level 3
Hi,
Usually, the error 5 means 'Access denied'.
The major difference between your scenario 1) and 2) is that the former one is executed on behalf or the active interactive user that has its desktop, while the latter one, most probably, is executed unattended from the scheduler without any user desktop.
I believe that the root of the problem is somewhere in this area.
Have you checked that all requirements mentioned in http://support.smartbear.com/testcomplete/docs/working-with/integration/ms-vs/index.html have been met?
- Florian_Hofmann7 years agoContributor
Hi,
well, looks like I checked out almost all requirements on the site you linked, resp. another link from there (http://support.smartbear.com/testcomplete/docs/working-with/automating/via-com/configuring-manifests.html):
I had set uiAccess="false", but failed to read the line about to "Disable the Enable support for testing Windows Store applications option in TestComplete."..now I disabled it, TestComplete starts and runs the test.
Thanks for the link, I might not have looked there again soo soon...
Related Content
Recent Discussions
- 3 hours agoSubhraDas
- 22 hours agotramuntana