-
Notifications
You must be signed in to change notification settings - Fork 662
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
feat: Mutation Testing #3806
feat: Mutation Testing #3806
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3806 +/- ##
============================================
- Coverage 84.62% 58.31% -26.31%
============================================
Files 302 1 -301
Lines 286798 571 -286227
============================================
- Hits 242699 333 -242366
+ Misses 44099 238 -43861 see 301 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@KeewenawSTX Is this something you can own ? Mutation Testing is worth investing in. |
Alin has a new PR , closing this |
Description
This is my first swing at introducing mutation tests to our GitHub Actions workflows.
Mutation testing is a methodology where you mutate your source code and measure how many mutants "survive" your test suites. This provides a useful measurement for the quality of your test suite.
To run these tests locally:
cargo install cargo-mutagen
cargo mutagen
(Currently there's a missing file error, but the test cases are run and evaluated in
target/mutagen/mutations
so I'm assuming it's a coverage file issue.)Additional info (benefits, drawbacks, caveats)
Checklist
docs/rpc/openapi.yaml
andrpc-endpoints.md
for v2 endpoints,event-dispatcher.md
for new events)clarity-benchmarking
repobitcoin-tests.yml