How to use /testlist with /testmetadata

[chris spencer]

I'm attempting to use the MSTest Runner as per this page https://confluence.atlassian.com/display/BAMBOO053/MSTest+Runner

I enter the path to the <solutionName>.vsmdi file and this appears to work. However, I need to use the /testlist option in order to filter which tests are run. There does not appear to be an obvious place to enter this extra parameter in the UI. I've tried simply adding it after the path to the metadata file but this doesn't work.

This seems like something that should be simple to do and from the command line it is - worked first time. I would like to get it running via the MSTest Runner however. Is this possible?

[chris spencer · Accepted solution]

I resolved this issue by setting up a 'Command' task for the MsTest executable and calling it directly. I fail to see any benefit with using the MSTest Runner wrapper.

[Jason Monsorno]

The wrapper is just an executable with some of the parameters broken out, it was probably added to directly compete with competitors that have similar plugin/macro/etc.

I would setup an executable to MsTest instead of using a command task; that way you can have different server capabilities, audit which jobs use that executable, and can easily change the source/location of the executable if you upgrade versions. Easier to plan for the future proactively than retroactively.

[chris spencer]

I've setup MsTest.exe as an executable for the build image. Is this what you are suggesting? I then use a task of type command, selecting MSTest from the Executable drop-down

[Jason Monsorno]

Yeah, I saw you say 'Command' but for some reason I had 'Script' in my head.