-
Notifications
You must be signed in to change notification settings - Fork 27
Applied mutation testing to improve the quality of the tests and the code for Java implementation. #2
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
Conversation
Applied [mutation testing](http://confreaks.tv/videos/mwrc2014-re-thinking-regression-testing) with Ortask Mutator 1.9. Improved the quality of the tests (and the code) by 13% (from a score of 84.6% to 95.3%). - Explicitly made public fields 'public'. - Corrected the comparison of the error value by introducing bounds for it (added a new error precision field). -- Best programming practice: floats/doubles should never be compared like ints. - Made the new error precision part of the public API.
Applied [mutation testing](http://confreaks.tv/videos/mwrc2014-re-thinking-regression-testing) with Ortask Mutator 1.9. Improved the quality of the tests (and the code) by 13% (from a score of 84.6% to 95.3%). - Added needed tests to document behavior with bad and edge-case parameters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these are public, might as well make them final
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bergundy they were package private before this PR. If the test is running in the same package, I suggest we keep them package-private, and final is just a nice addition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's go with protected
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and final
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@omgm please change the attributes to final protected
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry guys, didn't know you were waiting on me. Changes have been done.
For mutation analysis, I create a new test to leave the original one intact. I forgot to clean up the new tests when I committed. This has been fixed.
Made client-accessible fields 'protected final' as agreed.
Applied mutation testing to improve the quality of the tests and the code for Java implementation.
|
@omgm merged, thanks! |
Applied mutation testing with Ortask Mutator 1.9. Improved the quality of the tests (and the code) by 13% (from a score of 84.6% to 95.3%).
-- Best programming practice: floats/doubles should never be compared like ints.