|
Test Plan
A test plan provides the following information:
General description of the project, its objectives, and the QA test schedule.
Resource requirements including hardware, software and staff responsibilities.
Features to be tested, as well as features not to be tested.
Details for the test approach.
Lists of test deliverables such as test cases and test scripts.
References to related test plans (which focus on specific topics) and project documentation.
Dependencies and/or risks.
Descriptions of how bugs will be tracked (Engineering Issues Form on bugfix).
Milestone criteria.
Lists of required reviewers who must provide approval of the test plan.
Example...
Test Case Checklist (Matrices)
A checklist of tests for a specific area of application
or tool functionality with rigorous, detailed I/O expectations.
Examples...
Test Case
A specific set of steps and data along with expected
results for a particular test objective. A test case does the following:
details test setup.
details test procedure (steps).
describes testing environment.
specifies the pass/fail criteria.
references results of test.
Test Case Specification From...
Test Case Log Form...
Examples...
Test Document
Type of test file. It is a sample document that contains
the feature being tested
Test Script
Type of test file. It is a set of instructions run automatically
by a software of hardware test toll.
Suite
A collection of test cases or scripts.
Black - Box Testing
In using this strategy, the tester views the program
as a black - box, tester do not see the cod of the program: Equivalence partitioning, Boundary - value analysis,
Error guessing.
White - Box Testing
In using this strategy, the tester examine the internal
structure of the program: Statement coverage, Decision coverage, condition coverage, Decision/Condition coverage,
Multiple - condition coverage.
|
