2014:mutation_testing_-_why_should_you_care
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2014:mutation_testing_-_why_should_you_care [2013/10/29 13:39] – jonjagger | 2014:mutation_testing_-_why_should_you_care [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| Unlike test coverage metrics (which only tell us how much of your application was executed, not whether the tests were any use) mutation testing lets us say something concrete about the quality of your test suite.\\ | Unlike test coverage metrics (which only tell us how much of your application was executed, not whether the tests were any use) mutation testing lets us say something concrete about the quality of your test suite.\\ | ||
| \\ | \\ | ||
| - | Mutation testing has been around for years, but it’s only recently that performant tools (such as PI Test for Java) have become available. We’ll look at the motivation and technology behind mutation testing and see some examples in action.\\ | + | Mutation testing has been around for years, but it's only recently that performant tools (such as PI Test for Java) have become available. We'll look at the motivation and technology behind mutation testing and see some examples in action.\\ |
| \\ | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
2014/mutation_testing_-_why_should_you_care.1383053987.txt.gz · Last modified: 2016/06/11 14:05 (external edit)