Open theunrepentantgeek opened 10 months ago
Describe the current behavior
We currently have reasonable code coverage over key parts of ASO (though there's room to improve).
However, code coverage by itself doesn't tell us very much - all we know is that the code is used by at least one test.
Mutation testing is a way to validate that our coverage is useful - and Gremlins seems to be a good option in this space.
Describe the improvement
We should try out Gremlins to see what it finds, and to judge whether it should be a regular part of our CI process.
Still something we're interested in looking into
No change from above.
Still interested in this.
Describe the current behavior
We currently have reasonable code coverage over key parts of ASO (though there's room to improve).
However, code coverage by itself doesn't tell us very much - all we know is that the code is used by at least one test.
Mutation testing is a way to validate that our coverage is useful - and Gremlins seems to be a good option in this space.
Describe the improvement
We should try out Gremlins to see what it finds, and to judge whether it should be a regular part of our CI process.