Skip to content

Master Test Plan
Document Master Test Plan
Author: Juha Sirnio - Tester, Teemu Vitikainen - Tester
Version: v0.1
Date: 18.06.2025

1. Introduction

This document presents the testing strategy, objectives, and coverage plan for the PrestaShop e-commerce platform. Its primary goal is to validate that all implemented features meet both functional and non-functional requirements, while upholding the overall quality of the system.

The system under test is a containerized PrestaShop instance deployed on CSC Pouta, integrated with MySQL, and managed via Docker Compose. The platform supports secure functionalities, automated GitLab CI/CD pipelines, real-time logging, and robust user and developer-facing features.

2. Test Objectives

  • Test user workflows (login, order, register)
  • Verify automation of CI/CD pipeline and Docker builds
  • Validate secure access (HTTPS, non-root containers)
  • Confirm real-time logging and alerting

3. Test Items

  • Dockerized PrestaShop + MySQL container setup
  • GitLab CI/CD pipeline for automated deployment
  • User workflows (PrestaShop UI)
  • HTTPS/SSL setup
  • Log monitoring system

4. Features to be Tested

  • FEA023 User workflows
  • FEA008 Secure Service Access
  • FEA005 Automate build, test, and deployment processes
  • FEA017 Implement security contexts (e.g., run as non-root user) to enhance container security
  • FEA007 Dockerized Service Production
  • FEA010 Provide real-time log monitoring and analysis capabilities
  • FEA006 Provide managed hosting for PrestaShop instances

5. Features not to be Tested

Deep testing of internal PrestaShop modules

6. Approach

Testing types
Integration Testing Validate service interactions PrestaShop - MySQL
System Testing Full platform tests with real-world flows
Security Testing SSL, container vulnerabilities, login mechanisms
Regression Testing Re-run tests after bug fixes or updates
Manual Testing
Tools
Robot Framework Regression testing & UI automation
GitLab CI/CD Automated pipeline validation
Performance testing

7. Item Pass/Fail Criteria

Test Item Pass Criteria
Functional Test Meets acceptance criteria and expected behavior
CI/CD Pipeline Successful build/test/deploy without errors
Log Monitoring Real-time logging + alerting work as expected
Security No critical vulnerabilities in containers

8. Suspension Criteria and Resumption Requirements

Testing will be suspended if critical infrastructure (Docker, MySQL, CSC Pouta) is unavailable or blocking defects prevent further testing. Testing resumes when blocking issues are resolved and the environment is restored.

9. Test Deliverables

  • Master Test Plan (this document)
  • Test cases
  • Test execution reports
  • Defect/bug reports
  • Summary report at project end
  • Installation and user documentation (if required)

10. Testing Tasks

  • Prepare and review the test plan
  • Design and document test cases
  • Set up the test environment (CSC Pouta, Docker, PrestaShop, MySQL)
  • Execute test cases
  • Report and track defects
  • Retest after bug fixes
  • Prepare test summary and closure reports
  • Communicate with developers and project supervisor

11. Environmental Needs

  • CSC Pouta virtual machine with Rocky Linux (or Ubuntu?)
  • Docker and Docker Compose installed
  • MySQL database (development and staging environment)
  • PrestaShop (development and staging versions)
  • GitLab for version control and issue tracking
  • Browsers for UI testing (Chrome, Firefox, etc.)
  • Test data (users, products, orders)

12. Responsibilities

  • Tester: Juha Sirniö – executes tests, reports defects
  • Tester: Teemu Vitikainen – executes tests, reports defects
  • Developers: fix defects, support test environment setup
  • Project Supervisor: reviews progress, approves deliverables
  • DevOps/Environment: (if separate) – maintains test environment

13. Staffing and Training Needs

  • Two testers (both beginners)
  • Training on PrestaShop basics, Robot Framework, Docker usage, and GitLab workflows
  • Guidance from supervisor or experienced team members as needed

14. Schedule

  • Sprint 02 start: 16.06.2025 - 28.06.2025
  • Test planning: 16.06.2025 -
  • Test case design: [date range]
  • Test execution: [date range]
  • Bug fixing and retesting: [date range]
  • Acceptance testing: [date range]
  • Project end: 29.08.2024

15. Risks and Contingencies

  • Limited testing experience (mitigation: training, supervisor support)
  • Environment setup delays (mitigation: early setup, backup plans)
  • Unforeseen technical issues with Docker, PrestaShop, or CSC Pouta (mitigation: document issues, seek help early)
  • Incomplete requirements or scope changes (mitigation: clarify with supervisor, document changes)

16. Approvals

  • Testers: Teemu Vitikainen, Juha Sirniö
  • Project Supervisor: Okko Tuuri
  • Developers: Tugba Ilhan