Master Test Plan
| Document | Master Test Plan |
| Author: | Jiahui Pan |
| Version: | Ver 0.1 |
| Date: | 6.3.2024 |
Master Test Plan
1. Introduction
This document will detail our testing approach, strategies and objectives for Skill Collector. Master test plan will include details about the testing schedule, resources required, test criteria and objectives. This document will give clear goals and a schedule for the product owner and stakeholders.
2. Test Objectives
The primary objectives of the testing activities are to:
- Verify the functionality of all software features.
- Validate the software against specified requirements.
- Identify and address any defects or issues.
- Ensure the software meets performance, security, and usability standards.
3. Test Items
The following software items will be tested:
[List of software items will be tested]
4. Features to be Tested
All features of the software will be tested, including but not limited to:
| Feature Number | Feature Name | Priority |
| FEA106 | Improve dark mode colors | P1 |
| FEA102 | Securely authenticate user accounts | P1 |
| FEA204 | Count average traffic in chosen area | P1 |
| FEA302 | Traffic situation in Sweden | P3 |
| FEA303 | Traffic situation in Norway | P3 |
| FEA304 | Localization for Swedish | P3 |
| FEA407 | Control access to the server | P2 |
| FEA403 | Regularly scan for known security vulnerabilities | P1 |
| FEA506 | Implement automated build and deployment pipeline | P2 |
| FEA503 | Implement logging and error tracking mechanisms | P3 |
| FEA515 | Automate tests for frontend and backend code | P1 |
5. Features not to be Tested
Certain features will not be tested, including: | | | | |:-:|:-:|:-:| | FEA201 | Export data to csv from the database | P2 | | FEA505 | Configure scalable and resilient infrastructure using containerization | P1 | | FEA517 | Maintainable Documentation | P1 | | FEA516 | Manual Testing | P1 |
6. Approach
The overall approach to testing will include the following:
- Types of testing: Module/Component Testing, System Integration Testing, System Testing, and Acceptance Testing.
- Testing tools: [List of testing tools]
7. Item Pass/Fail Criteria
The criteria for determining the pass or fail status of each software item will be based on:
- Compliance with specified requirements.
- Absence of critical defects or issues.
- Meeting performance and usability standards.
8. Suspension Criteria and Resumption Requirements
Testing activities may be suspended if:
- Critical defects are identified.
- Environmental issues arise.
- Resource constraints impact testing.
- Resumption requirements include:
- Resolution of critical defects.
- Environmental stability.
- Availability of resources.
9. Test Deliverables
The following deliverables will be provided as part of the testing process: * Test cases * Test reports
10. Testing Tasks
Testing tasks will include:
- Test planning and preparation
- Test case development
- Test execution
- Defect tracking and management
11. Environmental Needs
Testing will be conducted on the docker running in a cPouta virtual machine and by group members on their own machines. The previously mentioned environments will have different configurations and settings to ensure that the product can be tested in as many ways as possible to ensure high quality.
12. Responsibilities
The responsibilities of each team member involved in testing are outlined in the documentation Team Introduction.
13. Staffing and Training Needs
Staffing needs and training requirements will be assessed and addressed as necessary throughout the testing process.
14. Schedule
The testing activities will be scheduled according to the project timeline, with milestones and deadlines outlined in the Project Plan.
15. Risks and Contingencies
Potential risks to the testing activities include:
- Resource constraints
- Technical challenges
- Schedule delays
Contingencies will be developed and implemented to mitigate these risks as they arise.
16. Approvals
This Master Test Plan must be approved by Group leader Aaro Kolu before testing can begin.