We are running the Unit test cases via MSTest runner Plugin on Bamboo and the test files are generated on build agent machine.
We are trying to get the coverage report for result files using opencover via script task but getting error
Below is the script task
set mse="D:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7"
cd "D:\Program Files\OpenCover.4.6.519\tools\"
.\OpenCover.Console.exe -target:$mse\IDE\mstest.exe" -targetargs:"/noisolation /testcontainer:\"D:\bamboo-agent-home\xml-data\build-dir\TCWA-Q2TCWAD-JOB1\Q2.TCWA\UnitTests\API.Tests\bin\Release\API.Tests.dll\"" /resultsfile:"D:\bamboo-agent-home\xml-data\build-dir\TCWA-Q2TCWAD-JOB1\APItest.trx" -reports:"D:\bamboo-agent-home\xml-data\build-dir\TCWA-Q2TCWAD-JOB1\TestResults\openCover" -targetdir: "D:\bamboo-agent-home\xml-data\build-dir\TCWA-Q2TCWAD-JOB1\TestResults\openCover\html" -filter:"+" -mergebyhash -output:"$out"\TCWA-Q2TCWAD-JOB1.CodeCoverage.xml"
The argument '/testcontainer:\D:\bamboo-agent-home\xml-data\build-dir\TCWA-Q2TCWAD-JOB1\Q2.TCWA\UnitTests\API.Tests\bin\Release\API.Tests.dll"' is not recognised
I am new to bamboo. Please help me with it
As you can see in the improvement request below, Bamboo does not support OpenCover "out of the box" :
After a quick search, I found the following blog post that, at first glance, seems to be a pretty good way to workaround this limitation. This method uses an intermediary step with NCover. You can try it out and see if it works in your case.
We’re preparing for Bamboo 8.0, which will be our first Data Center release. To make sure our app vendors and customers with written in-house apps are prepared, we’re launching Bamboo 8.0 Early Acces...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events