How to Set Up a Test Case Library
After working for a small company (only 5 - 8 persons)about three weeks as a testing guy, I found maybe it is necessary to build a test case library/database for them. Because of lacking of the related experience, I state the Motivation and Design Idea here. Hope can get your help.
- One product, the test case life cycle should be more than at least two years.
- Small company, often have students to do the testing work, and obviously they are lack of test design experience. So it is not easy to maintain the testing coverage (no document now).
- New test case comes out frequently, such as the defect reported from customer.
- Currently, all the test cases are designed for manual testing. In the future part of them could be considered to be automated.
- Busy manager, no time to read document. Database could, at least, give him a set of High Priority Test Cases for review.
- Could have fixed test case template.
- Use Access, shortening the development life cycle
- Have general functions: add new test cases, browse the test cases according to options, generate testing report (pre-test and post-test)
- Another function I am considering is report Regression Testing Test Cases. But I think this should have the requirement document available, right?
Re: How to Set Up a Test Case Library
Just my opinion. Hope it helps ...
- Define what information you want to extract from the test case library. This will help define what information you will need to create a test case.
- Define how a user will find test cases. This also helps define what info is required in you test case.
- The rest is determining how to model the data, and implement a GUI.
In my opinion a few things a test case repository / library / database should permit:
-Create a new test case, add a new revision of the test case, deprecate an out dated test case.
-Search and find test cases based on Priority, Functional Area / Component, Product, Project, Test ID, etc.
- Extract information from database - e.g. report on pass/fail/not executed status for a grouping of test cases, etc.