Comprehensive Test Planning

Comprehensive test planning

A test plan that user define in Rational Quality Manager drives activity for distributed teams through all phases of the project lifecycle. The test plan defines the objectives and scope for the test effort and contains criteria to help teams determine the answer to this question: Are we ready to release?

The test plan can be configured to meet the needs of your organization. User can use the test plan to do any and all of the following tasks:

• Define business and test objectives

• Establish a review and approval process for the test plan and for individual test cases

• Manage project requirements and test cases and establish the interdependencies between the two

• Estimate the size of the test effort

• Define

The test plan can be configured to meet the needs of your team. Typically, a test plan identifies requirements, risks, test cases, the test environments to be tested, business and quality objectives, test schedules, and other items. Related test plans can be grouped together in a nested master-child relationship.

Test plan sections

A test plan includes several predefined sections.

Each section includes its own editor. Some sections, such as the Business Objectives and Test Objections 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 plan sections, such as the Requirements and Tests Cases sections, provide links to these additional test artifacts.

Still other sections include tables that establish and measure against criteria such as Exit Criteria, Entry Criteria, Quality Objectives, and Test Schedules.

User can add your own sections and remove sections that you do not need using the Manage Sections feature.

Test plan

With categories, the field values are restricted to text format. However, with custom attributes user can also use integer and date formats. Custom attribute values are free-form and not restricted to a predefined set, allowing any data to be entered and used when working with test artifacts. When user view a list all of test plans he is part of, he can filter the list by using the custom attributes.

Test plans and their relationship with other test artifacts

From a test plan you can manage other test artifacts, such as test cases and requirements. The topic on test artifact relationships describes the relationships between tests plans and other test artifacts, such as test cases, requirements, test scripts, keywords, test data, and so on.

Test execution status

From the test plan overview you can track the test execution status of test cases and test suites. User can view the relationship between test estimates and actual time spent, test execution progress in relation to the assigned weight (or point) values, and test execution status in relation to the number of tests attempted.

Test plan tasks

Here are some of the tasks that user can perform with test plans:

• Set up a formal review process that is visible at all times to all members of the larger project