A Quality Manager test case includes the following predefined sections:
Each section includes its own editor. Some sections, such as the Test Case Design, Pre-Condition, Post-Condition, and Expected Results sections, consist of a rich-text editor for text input. These editors provide common formatting features such as table support, font support, bullets, and numbered lists.
Other test case sections, such as the Requirements, Test Scripts, and Test Execution Records sections, provide links to these other test artifacts.
You can add your own sections and remove sections that you do not need using the Manage Sections feature.
Test case categories are used in the Summary section of a test case.
You can use test case categories to help organize your test cases into logical groups. Later, when you use the All Test Cases feature to list all of your test cases, you can sort the listing using the categories.
By default, three test case categories are provided: Category, Function, and Theme. You can add your own categories, functions, and themes to the predefined ones and also create your own types of categories.
Test case weight is a measure of execution effort and can be based on tester hours, units of work, or priority.
A Quality Manager test case is based on a test case template. When you create a new test case, you choose a template to base it on. You can start a new test case with one of the default templates, or you can create new ones. You can also designate which templates are the default.
A test case template is a collection of test case sections. You create a template by adding and removing existing sections or creating new sections. If the section names do not match what you are accustomed to, create new sections and add them to a template.
Each test organization can design their own test templates.
Each test case is usually associated with a test script, although it is possible to run a test with no associated test script.
A test script is a manual or automated script that contain the instructions for implementing a test case. You can write manual test scripts to be run by a human tester or you can automate some or all of the instructions in the test script. You can also associate automated functional test scripts, performance test scripts, and security test scripts with a test case.
These provide information for the person executing the test. Use preconditions to communicate information that must be true before the test case can be executed. Use postconditions to communicate information that must be true after the test case is executed.
Test cases are an integral part of the test execution process. To run a test, you can do any of following: