Arlo Belshee: What makes a good test suite? – Summary
So having read through all answers quoted by Arlo I think this summarizes it best… also trying to give some priority derived from how often these criteria got mentioned. All of them refer to automated testing. Only Markus Gärtner gave a detailed description what a good manual test suite is about.
So to quote the question:
What are the characteristics of a good test suite?
- Fast: If I did not miss anything this is what actually all answered. Some defined the limit in minutes others even in seconds.
- Easy to read: Focused on the body of a test method it must be easy to understand the purpose of the test.
- Robust: Obviously many have made bad experiences with flaky test results which actually will lead to distrust the test.
- To the point: A good test suite obviously is not the result of capture & replay of a complete workflow. It’s tests rather focus on one point and thus should only contain one single assertion.
- Safety net: It encourages developers doing refactorings thus keeping agile – as they know there is a safety net.