-
Notifications
You must be signed in to change notification settings - Fork 101
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
mutmut and @property #259
Comments
If it's a syntaxerror it should have failed the test run, and that should have caused the mutation to be marked as killed. |
Hi Anders, Unfortunately, it doesn't :( One mutant survives (3), diff below:
If I apply the mutation and re-run the test suite manually:
Happy to provide further information later on if required. |
Just had a quick look at the code... I might have a clue about the issue. Because the test fails due to an uncaught exception, in this particular case the return code will be 2 (On Unixoide at least. TBD on Windows). |
Unfortunately, I couldn't enter pdb by adding breakpoint() before the above line. So, I switched back to a simple print statement. Hypothesis confirmed:
|
Hi there,
During my last Python class, one participant discovered an interesting case with
@property
, which I reproduced and simplified below.mutmut is reporting one survivor:
@property
decorationNow I am wondering. Applying the mutation causes a Syntax Error, whence the test suite does not run at all.
Does that count as survived? Or are we supposed in this case to suppress the mutation with a
#pragma
?Thanks in advance,
Loic.
The text was updated successfully, but these errors were encountered: