| || |
Naming of the Test Cases and Macros
Hi! I am not sure is this right forum to ask?
We are having problems with naming Test Cases and Macros. We are currently using TestDirector. Td unfortunately does not give any unique identification to test cases what could be used with macro names. Either our automation tool does not give any unique names to macros what could be give to test cases. Macros cannot be saved to TD because running environment of the macros is in different system. I understand that this kind of organising of the testware is not very good but be are forced to use it due to company policy (at least year more). So Td is only used as management tool (planning and archiving)and automation tool is used (surprise) automate these cases.
What could be best way to name test cases in TD and macros if you keep in mind that there is no "link" between these 2 tools. We have thought to use somekind of numbering space but it does not feel very nice way to do it (it is one solution but causes some extra work to maintain this numbering space)
Re: Naming of the Test Cases and Macros
Why not assign names related to the requirement or functionality being tested? If you are testing to a Requirements document that has paragraph numbers, the paragraph numbers could also be used.
Main thing is to have some kind of a cross reference so you know what is being tested with each test case. I know some Test Cases may test more than one requirement, but the Test Case would be associated with some User Operation.