-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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
smarter stop method 'constant' #121
Comments
Actually, no mutant should be created for this method. so this is indeed a bug. |
Really? (I activated the 'constant' mutation) |
With |
well this is what I though when I read to documentation but this actually activate the mutants: The doc says: <features>
<feature>
<!-- This will allow descartes to mutate deprecated methods -->
+STOP_METHODS(except[deprecated])
</feature>
</features>
and indeed I activated several mutation operators this way. |
Yes, sure, you activate the mutants by disabling the stop methods. Sorry I might not have been clear enough. |
ok! I think you can add this sentence in the readme file. |
Characteristics
Description
The stop method 'constant' sometimes creates a mutant that returns the exact same value of the returned constant. I face this limitation in abstract classes that have some methods with default behavior (eg https://github.com/interacto/interacto-java-api/blob/master/src/main/java/io/github/interacto/binding/WidgetBindingImpl.java#L243). The method returns false and Descartes creates a mutant that returns
true
while it should just create a mutant that returnsfalse
.Do you think that is possible to improve that?
Steps to reproduce
Create a method that returns true.
Enable
except[constant]
The text was updated successfully, but these errors were encountered: