MSTest unable to parse results

[chris spencer]

I'm attempting to get Bamboo on-demand to run a test using MSTest. It appears to run the test but then fails parsing it afterwards. What could I be doing wrong?

Copyright (c) Microsoft Corporation. All rights reserved.

Loading C:\build-dir\DAS-TE-JOB1\PortalWebApp\Dashworks.Model.Testing\bin\Debug\Dashworks.Model.Testing.dll...

Starting execution...

Results Top Level Tests

------- ---------------

Passed Dashworks.Model.Testing.JsonModelTests.TestJsonDatePickerProperties

1/1 test(s) Passed

Summary

-------

Test Run Completed.

Passed 1

---------

Total 1

Results file: C:\build-dir\DAS-TE-JOB1\TestResults_Build_3.3.0.24.trx

Test Settings: Default Test Settings

Parsing test results...

Failing task since test cases were expected but none were found.

Finished task 'MsTest'

If I add an MSTest Parser task then that fails also. With the same error.

Starting task 'Parse results' of type 'com.atlassian.bamboo.plugin.dotnet:mstest'

Parsing test results...

Failing task since test cases were expected but none were found.

Finished task 'Parse results'

[chris spencer · Accepted solution]

Bamboo on-demand only allows the generation of .trx files. It validates this in the UI. I could run the MSTest.exe directly and possibly generate an .xml files but I chose not to do this.

I resolved this by changing the 'Results filename' value from:

"${bamboo.build.working.directory}\<filename>.trx" to just "<filename>.trx"

Maybe it was the backslash causing the issue...

[Martin Morin]

This also fixed my issue

[dougknudsen]

This fixed my issue too. Using "**/*.trx" works.

I wonder if it is a relative path so putting "${bamboo.build.working.directory}/...." for the Results filename causes issues. Can't find any logs that show what the full path it is trying to use but I bet that is the problem.

[Ron Chan]

Chris - try generating the test file to an .xml format