Test case owner – W ho wrote it? Who is responsible for updating it?
Item to be tested – Describe
Item pass/fail criteria – Must have pass/fail criteria for test case
Automation – Can it be automated? Is it automated? Point to file.
Testing tasks – one-page procedure
Environmental needs – Lab setup
Special procedural requirements
Test case priority – changes constantly, depends on many factors
Track which software version this test case is valid for
Schedule – Time to perform the test case – keep track of it
Bugs found by this test case – update every time a new bug is found
Software Testing Process: Test Cases Start writing test cases as the product requirements are being defined. Show your test cases to the developer who is doing the coding. Get him/her thinking about how the feature will be tested. Help prevent the bugs from ever getting into the code. Test cases should give enough information to perform the test, but not so much detail that everyone will perform the test in the same way. You want to allow some variation and randomness in the test case.