| || |
Test Case Naming Method
I need a decent method of naming test cases. All books and articles I read will refer to using a unique ID for the test case name. What I need is a method to generate a name that not only identifies the content of the test case and what it actually addresses but to also implement an unique ID number that is automatically generated. This way anyone can 'name' a test case and not create duplicate names. I suspect this needs to be database driven. Anyone have such a method implemented?
Re: Test Case Naming Method
How about defining each test case in a DB table as:
id_nbr (serial integer, primary key)
test_case (text or char)
Use the func_area field to define what "test" this case belongs to - you could have a few simple categories (GUI, DB, busRules), or one for each screen to be tested - whatever works for you.
Then you could report the func_area concatenated with the id_nbr to be your test case ID in the test procedures or other reports.
In a past job for the govt. where we had a good set of requirments doc.'s, the test cases where named as reqtNbr-testCaseNbr, with testCaseNbr starting from 001 for each requirment.
Hope this helps.
Software Testing (n): 1. The art of trying to increase your confidence in a piece of software by finding everything that is wrong with it.