Mutation Testing Report #931
AlexDenisov
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, Marcin!
I am working on a tool for mutation testing, it is called Mull.
In a nutshell, it is a technique that helps to assert how good a test suite is.
Here how it works: you have a test that tests a function. If you introduce a semantic change into the function, then the test should fail. If that is not the case, then either test or function is not good enough.
Recently I made an attempt to bring Swift support just to check whether it works or not. Lots of work needs to be done to make it production ready, but, in general, results are great and promising.
I assessed the quality of your test suite, and I can conclude that it is great. However, I found some issues, which I share below.
Each entry has the following format: list of tests and change. The system expects at least one of the group of tests to fail based on the mutation. Also, I grouped similar mutations together (
advanced by 0
,precondition
).I hope this helps to improve your great library!
Tests:
Diff:
Tests:
Diff:
Tests:
Diff:
Tests:
Diff:
Tests:
Diff:
Tests:
Diff:
Tests:
Diff:
Beta Was this translation helpful? Give feedback.
All reactions