In this episode, we finish the Game Flow by creating a solution for accumulating the questions and answers and a new method for routing to the result.
We use the mutation testing technique to check if the behavior of the
Flow class is well covered by our tests. We do so by manually mutating the production code and checking if the tests are failing; if they do fail, we're confident with the coverage.
This technique proves its value as it helps us detect a missing test. We add the missing test and discuss how it could have lead to potential bugs in the future.