dotCover skips assemblies
Hi everyone, i'm having a problem where dotCover seems to skip some of the assemblies in my solution. I've tried setting no filters, and explicitly setting +:myAssmblies but both generate the same result. Any ideas?
Thanks, Gonzalo
Please sign in to leave a comment.
I'm seeing something similar on our main executable. According to Reflector, the name of the assembly is "ceo". The name of the build output is "ceo.exe". The default namespace is "Ceoimage.Basecamp.MainMenu". I added the following my filters but it never shows coverage results in this assembly:
+:ceo
+:ceo*
+:ceo.exe
No idea what is going on.
Wait, capitalization was the key. That mystery is solved for me. There are still other assemblies being tested that dotCoverage does not hit. I will check the filter on those, but is there anyway for us to see what assemblies are being skipped? Any log file somewhere?
Hi
What build runner are you using, are tests actually executed for these assemblies?
Can you post a screenshot of a build step and a build log please.
Thanks
Michael
There is no easy way as far as I know, but I'll ask dotCover developers on that.
Thanks
Michael
Hmmm, it seems to be happening again on the same assembly named "ceo" after it had been working fine for a while. This time, I downloaded the coverage.zip file and found a "ceo" directory that should contain results, but all the HTML files show no classes where I know I have classes with test coverage. Strange how it would stop working all of a sudden after I made no configuration changes.
Still perplexed by this one. I just ran NCover on the build server and found this assembly is being covered. TeamCity's test results page show tests covering this assembly are being run and passed. I found the attached dotCover7094734687847167656Report file and it does show the assembly but reports 0% coverage for every class in the assembly.
Are there any attributes of an assembly that could cause dotCover to skip it?
Attachment(s):
dotCover7094734687847167656Report.zip