We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Still something we're interested in looking into
Sorry, something went wrong.
No change from above.
Still interested in this.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: