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
Actually, my point is also that if we change the number of mutations the test will break.
Take my example of 33 mutations, and let's suppose we chose 20% rounded up, running 7 mutations (6 or 7 here is annecdotic).
Then the assertion
analysis generalResult numberOfEvaluatedMutants / numberOfMutations * 100
Will be equals to 7/33*100 == 21.21 which is not your expected 20 :)
7/33*100 == 21.21
Equally, if we choose to run 6 instead of 7, we would have 6/33*100 == 18.18.
6/33*100 == 18.18
At the end the question is: do we stop before exceeding the budget or after? So we need a test for this ^^
Originally posted by @guillep in #34 (comment)
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Take my example of 33 mutations, and let's suppose we chose 20% rounded up, running 7 mutations (6 or 7 here is annecdotic).
Then the assertion
analysis generalResult numberOfEvaluatedMutants / numberOfMutations * 100
Will be equals to
7/33*100 == 21.21
which is not your expected 20 :)Equally, if we choose to run 6 instead of 7, we would have
6/33*100 == 18.18
.At the end the question is: do we stop before exceeding the budget or after?
So we need a test for this ^^
Originally posted by @guillep in #34 (comment)
The text was updated successfully, but these errors were encountered: