Add test cases for all mutators #685
Merged
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
maks-rafalko
reviewed
May 1, 2019
BackEndTea
force-pushed
the
enhancement/mutator-test
branch
from
7783311
to
ff62bc9
Compare
maks-rafalko
approved these changes
May 2, 2019
|
Thank you @BackEndTea |
|
Thank you @borNfreee |
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.
This PR:
All mutators will now be used to parse files in the 'CodeSample' folder. Wheter or not they mutate
this code doesn't matter, the test here is to make sure that this code does not crash the mutator.
One issue found by this test has been fixed, namely the
DecrementIntegermutator could crash when 0 was compared to a function with a variable name.This means we can remove all the 'It does not break on ...' test cases that we now have for every mutator that in some way deals with functions/methods.