Master Test Plan
| Document | Master Test Plan |
| Author: | JJ |
| Version: | Ver 0.1 |
| Date: | 09.03.2025 |
Master Test Plan
1. Introduction
The purpose of this document is to outline the testing process, tactics and strategy to be used in the development of PrestaShop. Testing should verify that the product behaves as expected, and that each feature integrates and functions alongside other features. The system under test is PrestaShop e-commerce platform, though tests will be performed in a testing environment.
2. Test Objectives
The goal of these testing activities is to verify the functionality of the program, make sure that new features are secure and work as expected within the overarching product, and to gauge any potential vulnerabilities or issues within the product.
3. Test Items
The software items to be tested include - The functionality of PrestaShop code - Proper functionality of the database - Functionality of all features
4. Features to be Tested
The features to be added to the software and tested include - FEA002 - Secure access - FEA003 - Docker service - FEA010 - Integration scanning - FEA011 - Access controls - FEA023 - Version control - FEA031 - Managed hosting - FEA032 - API access - FEA081 - Bug reporting - FEA083 - Bug assignment - FEA087 - Error tracking - FEA132 - Password recovery - FEA135 - Secure user login - FEA141 - Automated database backup - FEA149 - Disaster recovery - FEA192 - Payment integration - FEA193 - Seamless checkout - FEA210 - Base image - FEA212 - Essential tools
6. Approach
Functional tests will be performed on all features that affect the functionality of the software. Integration tests will be performed on all features that depend on or change the way the software works. Acceptance tests will be performed on the software as a whole whenever a relevant stakeholder is available to perform the test.
7. Item Pass/Fail Criteria
For an item to pass a test, it must function as outlined in the feature description as well as the test case description of the currently running test. If a software item behaves somewhat differently to how its function is outlined in documentation, an acceptance test is run to determine if the functionality is adequate.
A software item fails its test if it does not function as described in its description or if its functionality causes another software item to stop working correctly.
8. Suspension Criteria and Resumption Requirements
Testing activities will be suspended if there is nothing to test, testing somehow clashes with development, or the test engineer is not available to monitor testing. Testing activities can resume when these issues have been handled.
9. Test Deliverables
The testing process will deliver documentation/information on passed/failed tests so that any issues can be fixed.
10. Testing Tasks
For testing to be performed a test environment must be established.
11. Environmental Needs
Testing requires a testing environment (virtual machine) that is separate from the development environment.
12. Responsibilities
The test engineer and any assigned testers are responsible for testing activities.
13. Staffing and Training Needs
Testing staff will be trained in using the testing software and performing tests in the test environment.
14. Schedule
Feature testing will be conducted alongside development; acceptance testing will be performed in regular intervals.
16. Approvals
Test plan must be approved by the test engineer and the team leader before testing can begin.