Hi Southpaw,
There should not be any difference between distributed run of TC tests and standard tests, except that TestComplete test adapter should be installed on remote machines. You should also understand that *.tcTest (or *.tc12Test) files are actually considered as tests by TFS, not *.pjs.
As far as I understand, this error
No tests were discovered from the specified test sources
can occur in two cases:
1) TestComplete test adapter is not installed on a remote machine (Have you installed Visual Studio integration or Visual Studio Test Agent integration on your remote machines?)
2) Test files are not found in the "Drop location folder" (Are you sure that *.tc*Test files are present in your \\ussdvucsd107 share?)
Please also note that Microsoft marked "Run Functional Tests" step as deprecated and recommends to use "Visual Studio Test" step instead in next versions of TFS. And it is a good practice to store tests in a source control.
Best regards,
Roman
When you say TestComplete test adapter - what exactly is this? Ive installed TestExecute on the remote machine that I am testing out these features on. I also have the VS Integration installed on the remote machine.
I'm aware of the deprecated task. I do not know what else to use as this task allows me to enter a machine group that contains the remote machine for this effort. The Visual Studio Test task doesnt offer that and when I run my build it attempts to run the test(s) on the build machine.
If you know the task when on TFS2015 to get the test to actually kick off on the remote machine(s) please let me know.
Hi Southpaw,
Don't worry about TestComplete test adapter. I meant that you need Visual Studio integration or Visual Studio Test Agent integration. Since you have installed one of them on the remote computer, probably the reason is that .tcTest files are absent on the remote machine.
Regarding Visual Studio Test task, next versions of TFS provide with a new more flexible release pipiline which allows to distribute tests among machines, and it uses this task.
Thanks for the help, Julia, Roman!
Southpaw, was the issue resolved? Please give Kudos to replies and accept the best answer as a solution to say thanks to guys.
Hi - No the issue is not resolved. My build def runs without error. However, the test is not executed. I have a support ticket opened for this same issue that has yet to be resolved. No one has explained how this - having test execute or test complete actually runs the test(s) - when TFS Build Def's are used to kick off remote test execution. On a side note, I also have a ticket open regarding using TestComplete for the remote test execution using a Network Suite. I am unable to verify the host machine. Ive had destop engineering, AT&T engineer's (they manage our clients firewall) and the security team all try and assist me in why I keep getting a verification failure that says server not started. All the requirements are met. So from my side, this feature does not work. Sorry, I wish this all was resolved because Ive put a mountain of time into proving this feature works for my management team.
Hi Southpaw,
It's sad to hear this. Have you contacted the TestComplete Support team regarding this question? If you haven't, I suggest that you reach out to them:
