Test Case templates
T
Tara Ford
In the projects we test we have several steps that are used across several types of tests.
Additionally many of these steps change as software gets updated, or we find more efficient ways to test things.
My current solution is to have a list of templates for each platform we test in our repository. These templates are constructed entirely from shared steps. When a new test is needed we simply clone the template and move it to the correct place. When a step changes, we just update the shared step.
What would be more efficient is to flag certain test cases as templates and then have the option to create a test case from a template.
Maksim Bletsko
we need it
Perry Goy
I would also find this useful if prerequisites could be shared in the templates as well!
Esteban Aragon
Agreed; I run into the same issue.
In the software I test, there are many (MANY) UI components that rely on the exact same GUI layout. They need basically the exact same test steps, with only the names and values of things changing from one to another. But, it is too impractical to use shared steps, because there are so many variables.
Whenever a new UI component is added, I clone a template suite to test it, and replace manually in every child case the green elements (see pic attached).
This should be made automatic with a corresponding wizard:
- Wizard lets you create a suite with sub-cases and sub-suites (a template)
- They are stored under a name in a separate Templates view
- You can mark some keywords in the Templates wizard to be filled in later
- When cloning a template into the real repo, the wizard asks you how to replace the keywords
We could also have some parts where you can fill in with a combo-box of choices (exemple: choose between "enabled" or "disabled").
It'd also be great to have markdown work with the filled-in words.
Currently, I mark my keywords in between brackets, in all caps: [KEYWORD]
And mark choices (combo-boxes) with slashes: [CHOICE 1 / CHOICE 2].