-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Ensure tests run on ci #305
Conversation
LCM Tests 8 files 8 suites 1m 34s ⏱️ Results for commit 513fdda. ♻️ This comment has been updated with latest results. |
…download Test results artifacts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 5 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @hahn-kev)
* The mismatch brought in a newer version of assemblies after the non-test assemblies were built causing test failures
…as 0. Added a test for this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 3 files at r3, all commit messages.
Reviewable status: 6 of 7 files reviewed, all discussions resolved
currently no tests are being found and run on CI, however there's no errors. I suspect this has been happening since bc9c0da as that's when the test adapter version changed.
I've also included test reporting in CI so we will better catch when tests aren't running. It turns out the flag
RunConfiguration.FailWhenNoTestsFound=true
only works for the vstest adapter, which we're not using.This change is