-
Notifications
You must be signed in to change notification settings - Fork 389
/p:CollectCoverage=true causes all test discovery to fail when class derives from XUnitVerifier #544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@sharwell owns the |
Hi @AArnott, yep the issue is the instrumentation of
BTW next release should solve without any action we'll skip non instrumentable dll(embedded or external pdb with no local source), I did a test with master(tomorrow you can use nightly, I just fixed an issue we're back by a week).
To hide the warning we expect that a user will add excludes, or we could move from warning to verbose. |
I moved from warning to verbose because xunit will warning every time. #548 |
Applies prescribed workaround for coverlet-coverage/coverlet#544
Thanks! The exclude workaround worked for me and I'll go with that for now. |
@MarcoRossignoli Why is it saying there is an embedded PDB without source files? The source files are part of the embedded PDB. |
Maybe the message is not so clear...I mean "embedded pdb without local source files," local is about local hard drive...if sources are not on pc running test we skip. |
Repro
Unzip: mytestlib.zip
Within the unzipped directory, run:
Notice how the one test method runs successfully the first time. But when code coverage is enabled, no tests are discovered at all.
I suspect an exception is being thrown during the code coverage instrumentation. Perhaps the
XunitVerifier
class I'm using as a base class (which is required to repro the failure) uses a pattern that coverlet.msbuild can't deal with.The text was updated successfully, but these errors were encountered: