Rikard Edgren’s test design e-book has been online since 2012, free for download and consumption, but I only knew about the book recently. It is a must read for beginner software testers. The book is short, only 32 pages long including the bibliography. Here are a few takeaways:
- Learn a lot, because it is more likely that testers (more often) will know the important stuff when they do.
- Testers who devise their own methods for testing learn far more than those who blindly follow scripted test cases written by somebody else.
- Complete testing is a myth. Even if a software tester is able to execute all possible application functions and unit tests, some things will remain unknown to her and will never be replicated like user needs and feelings and data. This means that testing is a sampling problem, and test design means finding out test ideas that covers the most important test samples when executed.
- Always ask what problem testing is trying to solve. Challenge the requirements.
- A test that is testworthy is a test that we think is likely to deliver information of some value about the app in test, even if the approach is risky, even if the requirement is not explicitly defined, or even if the process is time-consuming.