3

I am attempting to run tests on a remote agent by using a test controller that is on the same remote machine. I have set up my TestSettings file as follows:

<RemoteController name="MachineName" />
<Execution location="Remote">
    <AgentRule name="AllAgentsDefaultRole">
    </AgentRule>

When I tell MSTest to execute a selected test in release or debug mode, it successfully builds the project and then returns "Failed to queue test run 'run name': No connection could be made because the target machine actively refused it." Visual Studio 2013 has been installed on the controller/agent machine, and the agent, controller, and client can all communicate successfully. Default ports are being used for communication (6901 and 6910), and telnet is able to connect. How do I get the test executing successfully?

2
  • Have this exact same problem. Did you find the solution?
    – JL.
    Commented Oct 23, 2014 at 13:18
  • It looks like you cross posted this on SO stackoverflow.com/questions/21489997/…. Can you add the answer here as well?
    – Dan Snell
    Commented Jan 22, 2015 at 19:14

1 Answer 1

1

Found the answer. Agents cannot debug remotely, and while the build I was executing against in the above post was "release" (in one instance), I was still attempting to debug. If I select the test and click "Run" instead, it executes successfully on the remote agent.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.