Dart: Manual Mutation Testing
Mutation testing is a technique for measuring the quality of your tests.
Mutation testing (or mutation analysis or program mutation) is used to design new software tests and evaluate the quality of existing software tests
There are many tools for automating this process, such as Stryker Mutator, but Dart doesn't seem to have a tool to automate this right now. So, this post gives you a quick explanation of how you can implement a similar technique manually. This is a good way to help you prevent bugs and improve the quality of your tests. Read about Flutter Testing here.
What is Mutation Testing (Automated)
Mutation testing involves modifying a program in small ways. Each mutated version is called a mutant, and tests detect and reject mutants by causing the behavior of the original version to differ from the mutant. This is called killing the mutant. Test suites are measured by the percentage of mutants that they kill. New tests can be designed to kill additional mutants.
The idea is much simpler than it sounds. A tool like Stryker Mutator will change your code and then run your tests. If the tests don't fail, then there is a mutant. The tool will measure how many mutants there are in your system, and report a score. It highlights places in your code where you need to add extra test permutations, or verify and expect calls.
We do mutation testing to check the quality of our tests. When we fix a bug, we stop it once. However, bugs often come back, and someone who doesn't know the codebase may come along and put the bug back. Good quality tests ensure that the bug cannot come back. Mutation testing helps to ensure this.
Manual Mutation Testing
To test for mutants, you need to use your imagination. Ask yourself: can I add a bug to my existing code without the tests failing? If you can, then you probably have a mutant. Here is an example of what I mean. Take this simple piece of code.
This code version is completely wrong, but our tests don't cover the input permutations and therefore don't stop the bug from happening. So, we need to add more test permutations. We have a mutant.
The second test now fails, which prompts us to fix the bug.
We squashed one mutant. Of course, we should include many more input permutations, but you get the idea. This is a straightforward example, but you can stretch your imagination for Flutter scenarios. For example, would it be OK if a button had a color of pink instead of black? If not, you may have a mutant. Squash it with a verify in a widget test to ensure the button is black. Try to get yourself in the habit of thinking this way when writing tests. It helps you to improve your tests by thinking of what potential bugs may come up and stopping them before they do.
Here is a quick reminder Tweet. A retweet would be much appreciated! Follow me on Twitter for more Flutter and Dart content.