Hi Chris,
I would use it to generate a number of common templates for different projects with some static headers and project dependent information according to our internal Test Case writing standarts. That would eleminate copy\past of this info from one test case to another. Here is an example of the fields I'd put in:
h2. Description:
h3. In scope:
h3. Out of scope:
h3. Pre-Conditions:
h3. Environment: [Project dependent]
- *Browsers:* IE7-10, FF, Chrome, Safari 6
- *OS:* Windows XP, 7, 8
- *Other*: does not apply
h3. Additional info:
h3. Links:
Thank you,
Vlad
Hi Vlad,
What would a personal issue template do for a test issue type? Please let us know the use-case and we'll be happy to help.
Kind Regards,
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.