-
Notifications
You must be signed in to change notification settings - Fork 30
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
CI code coverage wrong #288
Comments
Check if is some TestFixture that is using a class on a parameter. With xunit that happens and doesn't run the test at all. |
I'll flag this for follow-up. Right now, I'm working in Terminal.Gui stuff that is going to have enough impact over here that I'd rather not fix something that ends up duplicating or obviating any work. Now that the big blocker of the reformat push tig wanted to do is mostly done, I should be able to start making much quicker progress. However, this is probably relevant to v1, yeah? Just want to be sure I can triage appropriately on my end. |
Good thinking. But, nunit doesn't have that issue. It's quite good with parameterized tests, and falls back to object if it can't figure it out, so they at least run, even if things get boxed or upcast. Usually, it's related to either an attribute that causes it to be excluded without explicit mention in a filter for the test runner or something that makes the source generator skip the method, such as incorrect access modifiers or other syntactic stuff, or else a misbehaving or improperly referenced ValueSource or TestCaseSource, when those are in use. |
@tznind does a git blame on any particular commit result in better behavior? Also, it's possible that the runner may just need to be tweaked, if this is only happening in CI runs. I seem to remember wanting to re-work that, in some work I was doing before I switched focus to TG v2 stuff. 🤔 |
This is only on v2 branch. Code coverage stat comes from a gist and theres only one so its 'last in first out' (not ideal but I can live with it).
Unfortunately the CI is only running on the merge commits so cannot narrow it down further. It works locally though so its like the CI test runner is exiting early - but not returning an errror exit code. It shows the right number of tests found:
But then it only reports running 396 I need to run the test on my linux machine to see if it is somehow OS related.
|
It looks like CI is not running all the tests
The text was updated successfully, but these errors were encountered: