testing projects.
§ Exercise: Use the all-pairs technique to reduce the number of tests required to cover
feature interactions for a particular program.
a. Functional Analysis
b. Requirements Analysis
c. Partitioning
d. Domain Analysis
4
e. User Scenarios
f. All-pairs
g. Using Combinations of These Techniques
7. System Testing
The high-level approaches that testers need to apply when conducting system testing, plus some
examples of how they might be applied.
a. Load Testing
b. Performance Testing
c. Stress & Hot Spot Testing
d. Spike & Bounce Testing
e. Reliability Testing
f. Configuration Testing
g. Acceptance Testing
h. Sample System Test Strategies
8. Test Documentation
How to develop an arsenal of repeatable tests so you don’t have to redo the test design process
every time you re-test the software. How to carefully calibrate the level of detail in the test
documentation so that there is a good return on the investment for the time it takes and the later
maintenance that will be required.
a. Rude Awakening – IEEE 829
b. What Will Your Test Documents Be Used For?
c. The Quality Plan
d. Test Project Planning
e. Test Case Documentation
i. Manual Tests
ii. Automated Tests
