Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
I have seen a lot of customers who use TCM.exe to execute tests on remote environments, but I have not seen many who use the same command-line to execute the tests locally. Here by locally, I mean tests running on the developer’s/tester’s box, which does not have any test controller or test agent and has only MTM. Yes, it’s possible to do this in 2012 version. :)
Now Let us go over the steps which you should follow to execute the tests locally.
tcm run /create /title:"Nightly Run" /planid:1 /suiteid:5 /configid:13 /settingsname:"<Name of your automated test settings>" /collection:<CollectionURL> /teamproject:<Team Project name>
Run created with ID: <xxx>
tcm run /execute /id:id /collection:<CollectionURL> /teamproject:<Team project name>
On completion, you will get the results as shown below.
Super useful; thanks!
Could you describe what is setting name in the command ( /settingsname:"<Name of your automated test settings>" )
Mehender, You can find the name of your test settings from MTM (MTM -> Lab Center -> Test Settings ->Name Column). Please try this out and do let me know in case you have any further question.
We followed the same steps, but we are getting the error(
A potentially dangerous Request.Path value was detected from th client).
Is there any other option to see the result in Test manager?
This error generally occurs if there are invalid characters in some specified http url.
Can you please specify the exact command line arguments that you are passing in the below format
You can mail the details to email@example.com
There doesn't seem to be any way to specify an order for test case execution with this - one 'possible' workaround was to group dependent test cases into suites, but ... there doesn't seem to be any way to wait for the suite to complete before kicking off the next suite either.
Any ideas on how we could control the order of test cases being run with this?
Roy, you should use an ordered test to control the order of execution of tests.
i tried to run tests locally with out specifying the test envirionment name but test caes got failed . in resluts im getting error message like this: "If you specify a test environment name, you must also specify the name of the test controller for that test environment.
Parameter name: testEnvironmentName".
i have created new testsettings and tried too. but getting same error message. Is there any other way or workaround to execute tests locally using tcm.exe commands?
I missed your comment earlier and today I was referring to this post for another customer and then I saw your comment. Apologies for this.
>> i tried to run tests locally with out specifying the test envirionment name but test caes got failed .
Can you please share with what error message the tests failed for you?
Not sure if anyone is still following this thread, but, when I try this, all tests instantly fail.
tcm run /execute /id:6764 /collection:%collection% /teamproject:webportal3
Executing run: steve test