A test charter is a tool to run exploratory tests. With the test charter the stakeholders define the scope and goal of such a test. By writing down this information, the charter remembers the team to concentrate on a particular type of risk while exploring the software. A good charter provides inspiration on how to run the test without determining on how to conduct it and without prescribing the test results.
This template - and this is true for all templates - is just a tool to help the stakeholders to write the important things down. You may add the three main aspects - mission, tools, information - of the charter in their own sections or write the information in just one sentence as the short description. Use what ever makes you feel more comfortable. If you want to alter the template to better suite your requirements, feel free to fork the project containing the blueprints!
| Tip Box |
|---|
| | Quote External |
|---|
| source-uri | http://www.satisfice.com/articles/et-article.pdf |
|---|
| author | James Bach |
|---|
| source | Exploratory Testing Explained |
|---|
| source-date | 16.4.2003 |
|---|
| Exploratory testing is simultaneous learning, test design, and test execution. |
Explore It! by Elisabeth Hendrickson provides lots of information on how to explore software. Besides presenting many interesting aspects of exploratory testing and practical tips it gives an introduction on how to create good test charters. If you need to know more about exploratory tests her book is a recommended way to start! There is also plenty of information on the internet. See Resources for some starting points. |
| 
