A test case answers the question, "What am I going to test?" You develop test cases to define the things that you need to validate to ensure that the system is working properly and is built with a high level of quality.
Test Case Section | Description |
---|---|
Summary | Use the theme, category, and function features to organize
your test cases into logical groups that you can sort later. Your team can
define these attributes any way that makes sense. You can also add a weight value to the test case. Weight is a measure of execution effort and can be based on tester hours, units of work, or priority. For example, a test case that requires twice as much time to execute could have double the weight as another test case. Reports that measure your progress take the weight value into account when determining status. |
Test Case Design | Defines the overall design of the test case. This can include any background setup information or topologies. You can include images or a high-level description in a bulleted format. |
Formal Review | Lists the people who must review or approve your test
case and defines the approval process. Use to institute a formal review process
that can help your business processes comply with applicable industry or corporate
standards and regulations. Each team member that is listed receives a work item notification. When team members respond, the test case owner is notified, and a summary of the results is displayed. The team owner then updates the test plan accordingly and repeats the process until all team members approve. |
Requirements | Use to associate requirements with a particular test
case after you add requirements to the test plan. After you establish the association between requirements and test cases, you can create coverage reports to determine the percentage of requirements that test cases cover. By maintaining this tight association between requirements and test cases, you can set up traceability throughout the project life cycle. |
Pre-Conditions | Defines the items that must occur before you can begin executing this test case. For example, another test case might have to complete before you can begin this particular test case. |
Post-Conditions | Defines what needs to occur after the test case has been completed. You can highlight any cleanup items here or uninstall instructions. |
Expected Results | Documents the results that must be achieved before you can consider the test case successful. You can attach a file or image that shows the state of the user interface or the resulting code. |
Test Scripts | Lists the test scripts that are associated with a particular
test case. Several types of test scripts are supported, including manual test
scripts, keyword-enabled test scripts, automated functional test scripts,
and others. Scripts can be reused in other test cases. Each test script contains the instructions for implementing a test case. During execution, manual test scripts are processed statement by statement; automated test scripts run automatically. |
Test Execution Records | Lists the test execution records associated
with the test case. These test execution records contain detailed information for the test case and the high level results from a test case execution. They specify the hardware and software environment for execution. For example, to ensure that your test case passes when it runs on four different operating systems, two different hardware platforms, and three different browsers, you could create an test execution record for each of these combinations. Test execution records also contain the overall result (that is, pass, fail, blocked) associated with the execution of a test case. In order for the test case to pass, all of its test execution records must pass. Test execution records can also include a detailed log of the test run, and thus a detailed history of all execution results. In addition, Rational® Quality Manager includes features for generating these test execution records automatically, thus greatly simplifying the test planning and test execution process. |
Attachments | Use to attach files and documents to the test case. |