How To: Give alternate path for picking test dlls?

Microsoft Test Manager always uses the associated build information to find and load test dlls for running automation.  However, one user came up with the scenario where their test code is not build with the application (dev) code.  They are associating MTM properly with the application (dev) build because that is the build they are testing but this also means that the MTM is not able to find the test dlls because it is not there in the associated build.

The alternative here is to tcm.exe command line to run. Below is how you can achieve this -

tcm run /create /title:<run title> /planid:<plan’s ID> /collection:<collection name> /teamproject:<project name> /configid:<config’s ID> /suiteid:<suite’s id> /testenvironment:<environment name> /builddir:<path from where test dll is to be picked>

The tcm.exe has lot of other functionalities.  To know more about it, check the MSDN doc of tcm.exe.

This post is courtesy "Nivedita Bawa" in my team.

Comments (4)

  1. How can we associate a build with Test running by TCM command says:

    Hi Gautam,

    Thanks for your post. We want to assoicate a test running with a build instead of builddir so it will show correct build number in test result. Use TCM run /create with build definiation and build paramemters but it returns "Invalid combination of pations for run command". So is there any other way we could associate a build with test runnin?

  2. Can you give the exact commandline you are using and the exact error?


  3. Vincent says:

    Hi Gautm,

    Thanks for your reponse. We configure the TFS url and project name in TCM.exe.config file and our command is:

    tcm.exe run /create /title:RunTitle /planid:2 /suiteid:66 /build:fakebuild3 /builddefinition:fakeDefinition2 /flavor:Debug /platform:x86

  4. What is the error?  Using the "Email Blog Author" link (at top right side), send me a mail on with following information –

     1. Your scenario – what you are trying to do?

     2. The commandline used

     3. The exact error.


Skip to main content