February 2013
Intermediate to advanced
160 pages
4h 33m
English
A good charter offers direction without overspecifying test actions. As an example, the following isn’t a charter; it’s a test case.

When charters are too specific, they become just a different (and weird) way of expressing individual tests. We end up spending a lot of time on test documentation with very little benefit.
On the flip side, charters that are too broad run the risk of not providing enough focus. You won’t know how to tell when you’re done exploring if the target is too big.
For example, consider this charter:
It’s so vague that you would never finish the mission. It calls for exploring the entire system with ...
Read now
Unlock full access