|
Test Plan
Description: Testing strategy and approach to testing
QA will use to validate the quality of the product prior to release.
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
Milestone criteria.
Lists of required reviewers who must provide approval of the test plan.
Samples...
Test Case Checklist (Matrices)
Description: An outline or matrices of test cases that test a feature, or set of features.
Samples...
Test Case
Description: A specific set of steps and data along with expected results for a particular test objective. A testcase
should only test one limited subset of a feature or functionality. 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.
Samples...
Weekly Status Report
Description: Use to inform management regarding latest issues that arise during the software development lifecycle
on weekly basis.
Samples...
Test Document
Type of test file. It is a sample document that contains the feature being tested.
 Share your thoughts on Documentation and Strategy in SQAtester Group.
 E-mail to a Friend.
|
