I'm new to PartCover.
I have some problem with results I get.
The report contains 0% when executing tests, even if they all pass.
I’m using 184.108.40.206424 release with MSTest.
When executing sample tests (with litle number of source dlls), the report is right.
But when executing on real tests (the difference is: more source dlls), the report shoes 0% coverage even if all tests pass.
What can be the problem?
The only difference I see is number of dlls. But it does not make sence for me. In log I get "Cannot update code for class", "In module X instrumented 12318808 items. Skip it" and "Cannot instrument module" messages.
Can you reference me to explanation of this messages, please?
Thank for any advice, Svetlana.
Just a guess:
Are the DLLs signed?
Can you post the all parameters you set before executing partcover (incl. include/exclude lists)?
The DLLs are not signed.
I'm executing from cmd the following script:
set target=C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\MSTest.exe
PartCover --target "%target%" --target-work-dir "%working%" --target-args "%args%" --log 2 --output out.xml
(I tried with include/exclude and now without as you see, the same result -> nothing).
In the log file I see that MyTestedSource.dll is loaded,
but after the line "Module NNNNNNN loaded (MyTestedSource.dll)"
I get line "In module NNNNNNN instrumented 12312112 items. Skip it".
And for all classes there is message :
"Cannot update code for class (no module)".
could you please try /noisolation option for mstest?
With /noisolation option all tests Fail.
I've tried some simple source.dll (with dependecies only on System*.dlls),
I see in log "was instrumented and stored" for methods of my tested class, but the report shows 0% when I do have test for at least one method.
When the rules are --include [*]*,
MSTest has 52% coverage, when my tested source is on 0% and the test itself also 0%.
If I click on method in tested source class, I see the code with red color.
"il body updated" appears near Microsoft.VisualStudio.TestTools.RunnerCommandline.Runner's methods.
when no such message is near the tested source methods nor the test methods.
There is only "was instrumented and stored" lines for each method in source.dll.
The error is: Could not load file or assembly <the referenced assembly>.
When without /noisolation all tests pass.
Log in to post a comment.