Handle tests marked as inconclusive
PR Summary
- Adds properties to CSharp classes to enable
InconclusiveandInconclusiveCountproperties on thePester.Runobject. - Adds logic to group and count tests marked as inconclusive.
- Pester Report output updated to support Inconclusive counts etc.
- Adds deprecation notice shown when
Set-ItResult -Pendingis used in tests. - NUnit reports updated to handle inconclusive tests (needs thorough review).
- Minor changes to help text
Fix #2400
PR Checklist
- [x] PR has meaningful title
- [x] Summary describes changes
- [x] PR is ready to be merged
- If not, use the arrow next to
Create Pull Requestto mark it as a draft. PR can be markedReady for reviewwhen it's ready.
- If not, use the arrow next to
- [ ] Tests are added/update (if required)
- [ ] Documentation is updated/added (if required)
Notes
I think the logic to handle inconclusive tests is sound, but I am looking for feedback on these points
- Are implemented changes to NUnit reports sufficient, or did I miss anything?
- Does this PR call for new tests or changes to existing ones?
- Are documentation updates needed (if so, where)?
- Deprecation notice wording and placement
Happy new year! 🎆 Thanks for looking into this. It looks great!
Thank you @fflaten and late happy new year to you too (sorry about the response time).
I have tried to address your comments and requested changes, but would appreciate some advise on this one though:
We need some tests to make sure this works and doesn't break in the future. Suggestions:
- Add test for behavior and error here
Can I trouble you for an example of what you have in mind that is not already there?
@fflaten when you have a moment, please let me know if there is anything else I should do or address to complete this PR.
Thanks
@fflaten when you have a moment, please let me know if there is anything else I should do or address to complete this PR.
Apologies for the delay. Been occupied with work for a while. We're also waiting on @nohwnd for final review + merge & release.
We need some tests to make sure this works and doesn't break in the future. Suggestions:
- Add test for behavior and error here
Can I trouble you for an example of what you have in mind that is not already there?
Can't remember tbh. so just ignore it. I probably missed the existing inconclusive test 🙂
& release. <- Not so easy :D My certificate expired because I asked for renew and then went on vacation. I am waiting for a new one.
Looking good. I've added cheaper way of checking that the deprecation should be shown so we don't have to inspect every single test on every run.
Merged, thank you! :)
Thank you for accepting the PR @nohwnd. And thank you @fflaten for you patience with me through the code reviews.
No thank you for your work, and sorry for being slow! Same huge thanks for Frode 👏
Thank you for accepting the PR @nohwnd. And thank you @fflaten for you patience with me through the code reviews.
Thank you for your patience and great work 👏