Components of an IEEE 829 Test Plan:
1. 1. Test Plan Identifier:
A unique name or code to identify the test plan.
Example: "Test Plan for Online Banking Application - Version 1.2".
2. 2. Introduction:
Provides an overview of the testing effort, including the purpose, scope, and
objectives.
Example: "This test plan outlines the testing activities for the new user registration
module in the online banking application. The objective is to ensure all
functionalities work as expected and are free of defects before release.".
3. 3. Test Items:
Specifies the software or system components to be tested.
Example: "The test items include the user registration form, the email verification
process, and the database integration for user data.".
4. 4. Features to be Tested:
Lists the specific features or functionalities that will be tested.
Example: "Features to be tested include: user registration with valid and invalid
data, password reset functionality, and account activation/deactivation.".
5. 5. Features not to be Tested:
Lists any features or functionalities that are excluded from the testing scope.
Example: "Features not to be tested in this phase include the mobile app interface
and the integration with third-party payment gateways.".
6. 6. Test Approach:
Describes the overall testing strategy, including the types of testing (e.g.,
functional, performance, security), techniques (e.g., black box, white box), and
tools to be used.
Example: "This test plan will utilize a combination of black-box testing techniques
and automated testing with Selenium for functional testing. Performance testing will
be conducted using JMeter.".
7. 7. Item Pass/Fail Criteria:
Defines the criteria for determining whether a test item has passed or failed.
Example: "A test case is considered passed if the actual results match the
expected results, and no major or critical defects are reported.".
8. 8. Suspension Criteria and Resumption Requirements:
Specifies when testing should be temporarily suspended and under what conditions
it can be resumed.
Example: "Testing will be suspended if the test environment becomes unstable.
Testing can be resumed once the environment is stabilized and all previously
executed test cases are rerun.".
9. 9. Test Deliverables:
Lists the documents, reports, and other artifacts that will be produced as a result of
testing.
Example: "Test deliverables include test cases, test logs, test summary reports,
and defect reports.".
10. 10. Remaining Test Tasks:
Lists any tasks that need to be completed after the initial testing phase.
Example: "Remaining tasks include retesting of resolved defects and performance
testing of the updated system.".
11. 11. Environmental Needs:
Describes the hardware, software, and network configurations required for testing.
Example: "The test environment requires a server with sufficient memory and
processing power, the latest version of the web browser, and a stable internet
connection.".
12. 12. Staffing and Training Needs:
Specifies the personnel required for testing and any necessary training.
Example: "This project requires two testers with experience in automated testing.
Training will be provided on the new testing tools and techniques.".
13. 13. Responsibilities:
Assigns roles and responsibilities for different testing activities.
Example: "The test lead is responsible for creating the test plan, while the testers
are responsible for executing test cases and reporting defects.".
