Quality improvements to homog and its test suite #23
Conversation
This file contains 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
Mutation analysis on vector-test.js was done with Mutator (http://ortask.com/mutator/). I improved the suite's mutation score from 0.64 to 0.85. I'll get it to 1.0 soon.
Mutation analysis was performed on homog-test.js with Mutator (http://ortask.com/mutator/). These are some fixes that were made for small issues in the source file.
Mutation analysis was performed on homog-test.js with Mutator (http://ortask.com/mutator/). I improved the test suite's mutation score from 0.63 to 0.8. In order to get to raise the quality of the test suite to 1.0, the following issue needs to be resolved: rockbot#22
omgm
changed the title
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.
These changes were applied after performing mutation analysis on homog-test.js. New score is 0.8 (from 0.63).
To get the score up to 1.0, the following issue needs to be fixed: #22