background image
<< Risks and Resources | Project Scheduling >>
Rational TestFactory
<< Risks and Resources | Project Scheduling >>
88
Chapter 6 - Test Planning
s
Might test (low)
This test might be useful to run, but is not essential to the
project. Run this test if you cannot make further progress on other, more
important, tests.
s
Won't test (low)
This test is not part of the testing project. A test with this
priority defines the boundaries of the test plan and helps focus attention on what
will be tested.
Types of Tests to Perform
There are many types of tests to consider as you create a test plan, including, but not
limited to:
s
Reliability tests
Can the application function without errors? Use Rational
TestFactory, Purify, Quantify, and PureCoverage for reliability testing.
s
Functional tests
Does the application meet its functional requirements? Use
Rational Robot for functional testing.
s
Performance tests
Is the system's performance acceptable under varying
workloads? Use Robot to record performance tests. Use TestManager to run these
test scripts with different workloads, and to analyze the results of a test.
Stages of Testing
There are several stages of testing to consider as you create a test plan. These stages
progress from testing small components to testing completed systems and usually
apply to different stages of the system's development cycle:
s
Unit testing
Verifies individual components, the smallest testable elements of
the software.
s
Integration testing
Ensures that the components in the implementation model
operate correctly when combined to run a test for a use case.
s
System testing
Ensures that the software is functioning as a whole.
s
Acceptance testing
Verifies that the software is ready for delivery and that it
meets its requirements.
Unit testing is typically performed by software developers. As a tester, your focus is
primarily on integration, system, and acceptance testing.