This section describes first steps, planning considerations,
and best practices when you begin the test effort.
Identifying and creating requirements
Requirements are an essential input to test planning. When
planning the test effort, you often begin by identifying the project
requirements that were used in the development effort.
Organizing artifacts by using categories
A category is an attribute of a test artifact. You can
use categories as a tagging or grouping mechanism to organize a test
project into logical hierarchies. If you migrate test artifacts from
other products that typically use a hierarchical organization, you
can use categories to represent that organization.
Creating custom attributes
Like categories, custom attributes can be used to help
group, sort, and filter your test artifacts. With categories, the
field values are restricted to text format; however, with custom attributes
you 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.
Managing risk
Risk-based testing allows you to prioritize what needs
to be tested based on the risk that is associated with various test
plans and test cases. With risk-based testing you can focus your resources
on those test artifacts that have the highest likelihood of failure or
the greatest impact if failure occurs. Ultimately, risk-based testing
helps your team mitigate risk.
Planning test environments
Planning your test environment includes defining your platform
coverage, setting up test plan environment types, generating new test
environments, and adding existing test environments to a test plan.
Estimating the size of the test effort
As part of the planning process, you can create high-level
estimates of the size of the test planning and test execution efforts.
You can also provide detailed estimates of the time or effort required
to run each individual test case. Later on, you can use the test plan,
the list views, and test execution records to measure your progress
and provides input to several reports.
Setting up a review process
You can set up a formal review process in which several
team members can collaborate in the development of a variety of test
artifacts, including test plans, test cases, and test suites.
Setting quality objectives and entry and exit criteria
You can use quality objectives to define the overall quality
goals for a release, as well as to define the required entry and exit
criteria for testing. You can use these goals to determine the level
of quality that must be achieved before your product is considered
ready to be released.
Have a problem or a question? Post it in the Jazz.net forum.