Repository navigation
ci(stryker): use coverage-analysis all in mutation run - #448
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #448 +/- ##
=======================================
Coverage 93.15% 93.15%
=======================================
Files 15 15
Lines 336 336
Branches 99 99
=======================================
Hits 313 313
Misses 12 12
Partials 11 11 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
With
coverage-analysis: perTest, Stryker 5.0.0 (solution mode, MTP runner) captures per-test coverage over the pool-wide set of discovered test assemblies for every mutated project.Change
stryker-config.json:"coverage-analysis": "perTest"->"all"(one initial test run per project, covered mutants run against all tests of the project). Same change as dailydevops/extensions.test#1542.Before / After
Both runs are single workflow_dispatch runs of
mutation.yml(before:main, after: this branch), so timing noise of several seconds applies.Risk
allis not safe: in pulse and healthchecks the run finished testing and then failed with OutOfMemoryException while serializing the JSON report; frameshift was cancelled. This repo is small, so it is not affected so far.perTestwrongly reported as NoCoverage are now tested; it is not necessarily a stronger test suite.