|April 23, 2018|
Test Case Repository
A Test Case repository is where QA keeps test cases use for various test situations. You should be able to find tests for Weekly Regression, Performance Testing, Security Testing and Acceptance Testing.
Seven Things I Learned About Using A Test Case Repository
- Always Update! Systems Change, Browsers change. If a test case hasn’t been updated in 3 months something is clearly wrong with it. (If it’s a manual test case, then it might be a good candidate for automation.)
- Negative Tests are Good! QA can learn a lot about negative test cases in a separate part of the project. Helps come up with ideas on
- Focus on the 80/20 rule. Don’t clutter the Test Case Repository with useless tests that people would not execute because they were relevant during the development stage of a project.
- Prioritize Tests. There should be more High Priority / Critical Tests in the Test Case Repository than low-level ones. Chances are the low-level ones won’t get executed very often, try combining the tests so QA isn’t overwhelmed by the number of tests to run.
- Product Managers Should be in the Know. Share access to the Test Case Repository to Product Managers so they are aware of what tests are run on a weekly bases. They may offer feedback on an additional test that should be run - or change the priority on existing test cases.
- Write Good Practical Test Cases. Test Cases should be easily understood and executed. There should never be a need to contact the original author. It’s a good place for new QA Engineers on a project to start. In addition, QA Managers should point out well-written test cases to inspire everyone to write well.
- Audit Often. Take a good look at the Test Case Repository often. During downtime, check to see if the test cases are relevant. If it’s not be executed, find out why and decide if it’s a relevant test.
It’s not the quanity of the test cases that matter it’s the quality of the tests.
Add your Comments
Feel free to leave a comment about this post.