Mutation testing - logger tracking missing/timeout/unviable tests #4179
Conversation
- dockerfile and shell script for specific packages - ci.yml for diff on packages on PR
Co-authored-by: jbencin <[email protected]>
- runs for modified files & created files - has to be run before committing the changes ``` cd mutation-testing/scripts sh git-diff.sh ```
ASuciuX
changed the title
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4179 +/- ##
============================================
+ Coverage 62.42% 82.61% +20.18%
============================================
Files 401 401
Lines 286383 288405 +2022
============================================
+ Hits 178775 238256 +59481
+ Misses 107608 50149 -57459 ☔ View full report in Codecov by Sentry. |
|
Feedback from PR meeting - let's move to draft for now. |
|
Related discussion in Nakamoto slack channel. |
| # test | ||
| steps: | ||
| - name: Run logging mutants from actions | ||
| uses: stacks-network/actions/mutation-testing/logger@feat/mutation-testing |
There was a problem hiding this comment.
this workflow doesn't seem to exist on this branch (or in main). is that something that needs to be re-added?
There was a problem hiding this comment.
I'd recommend merging the feat/mutation-testing branch into stacks-network/actions first, so you don't have to make another PR changing/removing the branch name later
There was a problem hiding this comment.
Also, I can't find the logger action either
There was a problem hiding this comment.
Also, I can't find the
loggeraction either
i expect this PR will be changing quite a bit as we've just started testing this. i'm converting this to draft for now
There was a problem hiding this comment.
yes, i will be updating it these days, wanted to have the PR-differences fully finished asap. this one will have to wait till we have all the mutants from the general sync before being merged
Applicable issues
Additional info (benefits, drawbacks, caveats)
Solutions and Recommended Usage
Cargo-mutant does an incremental build for each mutation, that’s why this solution comes with the implementation of tracking the output and only updating it with the differences, to run 10-20 mutants instead of 4000.
CI YML File: Are linked with the actions in the actions' repo stacks-network/actions#3.
Should be executed with every PR, as it tests only the updated or newly added functions in the PR's commits.
Handling Exit Codes (docs)
In the
loggerworkflow they are updating the place they belong to.Checklist
developandnextbranches