Source: dzone.com
Mutation Testing Systems: Improving the Quality of TestsCategory: Security, github
Professionally, I label myself as a developer, although I don’t like labels very much, and I prefer to say that the reason for my work is: to create quality software.
I like to define it as follows: Quality software is that which meets the user's needs efficiently and without errors.
"This deliverable must have a battery of tests that ensure a minimum of 70% code coverage", as a synonym of error-free code and proven quality in at least 70% of the code.
Let's see an example of tests that we submitted at the time: We configured JaCoCo to get the test coverage report and the result is as follows.
Taking into account that it is based on code mutations and that it applies not only to unit tests, but also to integration tests, as the code grows and the number of tests increases, it will take longer to execute them.
I like to define it as follows: Quality software is that which meets the user's needs efficiently and without errors.
"This deliverable must have a battery of tests that ensure a minimum of 70% code coverage", as a synonym of error-free code and proven quality in at least 70% of the code.
Let's see an example of tests that we submitted at the time: We configured JaCoCo to get the test coverage report and the result is as follows.
Taking into account that it is based on code mutations and that it applies not only to unit tests, but also to integration tests, as the code grows and the number of tests increases, it will take longer to execute them.
Related Articles
Community Partners
DevOps Careers