Benefits of using a repository tool:
- Allows you to store testing notes/test cases in one location (more organized)
- You are able to provide detailed steps
- Other testers (or non-testers) can access your test cases
- More time can be spent on testing
- Your ways of testing are not isolated...it is much easier to do exploratory testing
- Jotting down notes takes less time than writing test case
The benefits of each can also be used a con for the other. I have tested using both and my preference is to not use a repository tool. I like the freedom that it provides which allows you to test at your own will. Plus, if you have completed your testing, you can write a testing summary report. This includes a mission statement, environment information, tests performed, bugs found, and a charter status. This can be used to provide testing details to other testers, developers, product owners, etc.
What is your preference?
I am a proponent of not using a test case repository. We test each story in a sprint and attach testing notes. The notes allow others to see what was tested and how it was tested. Also, the testing notes are relevant to the functionality that the story provides.
ReplyDeleteThe test case repository holds all test cases that are written and the history of whether they passed or failed. I am not very fond of the prescriptive nature of test cases. I don't feel that it allows a tester to be creative in their testing. While it may help a tester that is unfamiliar with testing the functionality, it could also restrict them in finding different ways to test.
Great testing notes and documentation is the key. I prefer attaching the notes to the story and posting any test documentation, such as a release test plan or regression testing information, to the wiki.
I see value in both, depending on the circumstances.
ReplyDelete