MetricsFile

The mutant resulted in a compiler error. This can happen in compiled languages. Don't spend too much attention looking at this mutant. It is not represented in your mutation score.

The total number of mutants that were not even tested because the config of the user asked for them to be ignored.

At least one test failed while this mutant was active. The mutant is killed. This is what you want, good job!

The total percentage of mutants that were killed. Or a {{Double.NaN}} if there are no mutants.

The total percentage of mutants that were killed based on the code coverage results. Or {{Double.NaN}} if there are no mutants.

No tests are executed to test this mutant, because the mutant is located in a part of the code that is not hit by any of your tests. This means the mutant also survived and your missing a test case for it.

The running of the tests resulted in an error (rather than a failed test). This can happen when the mutant fails outside of running a test. For example, when a testrunner fails. Don't spend too much attention looking at this mutant. It is not represented in your mutation score.

All tests passed while this mutant was active. the mutant survived. You're missing a test for it.

The running of tests with this mutant active resulted in a timeout. For example, the mutant resulted in an infinite loop in your code. Don't spend too much attention to this mutant. It is counted as "detected". The logic here is that if this mutant were to be injected in your code, your CI build would detect it, because the tests will never complete.

The number of mutants that your tests produce code coverage for.

The number of mutants detected by your tests.

The number of mutants that are invalid. They couldn't be tested because they produce either a compile error.

All mutants.

The number of mutants that are not detected by your tests.

The number of mutants that are valid. They didn't result in a compile error or runtime error.