Mutation Testing
Mutation Testing is a fault-injection technique developed by DeMillo, Lipton, and Sayward in 1978 that evaluates test suite effectiveness by introducing small, deliberate bugs (mutations) into source code and checking if tests catch them. A test suite that kills (detects) all mutants is stronger than one that achieves high code coverage without killing mutants.
Source record
Citations copied verbatim from the method’s source record. No claim-level verification is inferred from them.
- DeMillo, R. A., Lipton, R. J., & Sayward, F. G. (1978). Hints on test data selection: Help for the practicing programmer. IEEE Computer, 11(4), 34–41. · DOI 10.1109/C-M.1978.218136
- Just, R., Jalali, D., Inozemtseva, L., Ernst, M. D., & Holmes, R. (2014). Are mutants killed by tests? How test suite composition affects the effectiveness of mutation testing. Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering. · URL
- Jia, Y., & Harman, M. (2010). An analysis and survey of the development of mutation testing. IEEE Transactions on Software Engineering, 37(5), 649–678. · DOI 10.1109/TSE.2010.62
Curated claims
Claims persisted in the evidence ledger, each with its own assessment.
This view does not invent a claim assessment when the ledger has none.
Related methods
Generated from the method graph and shown as machine-suggested relations — no evidence claim is inferred.
The generated relation graph has no outgoing relation for this method.