Skip to content

Master Test Plan
Document Master Test Plan
Author: Valtteri
Version: Ver 0.1
Date: 18.03.2025

General information

A master test plan (MTP) is a high-level document that describes the overall testing strategy, objectives, and scope for a software project or product. It provides a comprehensive overview of the key decisions, resources, risks, and deliverables involved in the testing process. It also defines the relationship and coordination among different test levels, such as unit testing, integration testing, system testing, and acceptance testing. An MTP helps to ensure that the testing activities are aligned with the project goals and requirements, and that the quality of the software is verified and validated. You can find more information about MTPs from these sources:

Master Test Plan

1. Introduction

This document contains information about the testing plan for features included in the Presta Shop platform. Planned activities include manual testing of features to ensure functional requirements outllined per feature are met.

2. Test Objectives

Tests are to be conducted in such a way that they ensure the functionality of all features in all possible conditions. The test plan per feature should take into account all possible variables that may affect the functionality of features.

3. Test Items

Items to be tested based on features or out of necessity:

Security - Testing implemented security fixes Login - Testing features and functionality around the login process to ensure a smooth and secure login process Payment - Testing of all features and functionality related to the payment process Performance - Testing the performance of the service to ensure a smooth customer experience

4. Features to be Tested

Features to be tested:

FEA132 - Password Recovery FEA178 - Feedback Form FEA192 - Payment Integration

5. Features not to be Tested

Current testing plan includes all features being implemented into the Presta Shop platform.

6. Approach

The testing will be conducted manually. Each test conducted will be verified by another member of the team. Additionally more than one team member may test the same feature if necessary (for example to test different platforms).

Broader testing may be conducted if a feature requires it.

7. Item Pass/Fail Criteria

PASS - All functions of a feature work as described and doesn't cause issues outside the scope of the feature. FAIL - One or more functions of a feature do not work as described or the feature causes issues outside the scope of the feature.

Additionally: Performance test should take into account eccessive impacts in the service's performace caused by the implementation of new features. Previous features should be checked after major changes in the platform to ensure the functionality of all systems.

8. Suspension Criteria and Resumption Requirements

Testing may be suspended due to: Critical issues preventing manual testing a feature completely Major changes in the project plan

Testing may resume when: Critical issues are solved so that manual testing may continue Changes in the project plan are set and new testing requirements are written

9. Test Deliverables

-Testing plan -Report of tested features -Report of important issues found during testing

10. Testing Tasks

-Test planning -Test execution -Issue reporting -Test reporting

11. Environmental Needs

Hardware - Server to be tested, Client device(s) Software - Prestashop instance, other necessary testing tools Network - Functional internet connection, VPN access

12. Responsibilities

Team Leader - Aleksi Overseeing the testing process and checking testing plan stays in the scope of the project.

Tester - Valtteri Test planning Assignment of needed team members for Tests Test reporting

Team memebers - Eemeli, Niklas, Rasmus, Anna-Katharina Other roles include implementation of features, as well as operations and security related tasks.

13. Staffing and Training Needs

Familiarization of prestashop platform, testing documentation as well as testing tools if necessary.

14. Schedule

Testing is to be completed as features come online. Scheduling feature tests will be done per feature depending the completion of said feature and sprint goals.

15. Risks and Contingencies

Identify any potential risks or contingencies that could impact the testing activities.

Unavailability - In case tester is not available to complete tasks, another member is to be named for testing the specified feature. Testing environment unavailability - Investigate the possibility to set up a separate environment to test specified feature. Alternatively re-schedule testing to once the environment is available. Delay in feature deployment - Re-schedule testing to match delayed feature deployement. Issues found in late testing - Schedule additional test to ensure funtionality of all features.

16. Approvals

Testing plan is to be approved first by the team leader and checked by the rest of the team.