Now that you have some experience with this technique, let’s reflect on when to use it, what it’s good for, and how to coordinate it with other techniques.
Here is a summary overview of our thinking:
1. Use domain testing when you’re just learning the program: Working through the program with the goal of finding every variable and testing it with basic domain tests is a good way to find bugs while discovering what the program does.
2. Simple domain testing has limits and will run out of steam: Input-focused domain testing will check for many bugs that might never exist in software at your company. As to the ones domain testing does find, the programmers will fix them and your tests will ...