Skip to content

Master Test Plan
Document Master Test Plan
Author: Minna Tapojärvi
Version: Ver 1.1
Date: 04.03.2024

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 overview into the testing plans for this project. Target of the test will be the added features to Tukko - Traffic Visualizer, that our team will implement during this project. The scope of the testing is to find most critical bugs and also make sure the features match up with the expected outcome.

2. Test Objectives

The goal of the testing is to verify that the features match up with the related user story and criteria from the product owner.

3. Test Items

Test items contain frontend and backend features.

4. Features to be Tested

  • FEA102 Securely authenticate user accounts
  • FEA106 Improve dark mode colors
  • FEA110 Enhance color contrast for color blindness
  • FEA201 Export data to csv from from the database
  • FEA304 Localization for Swedish
  • FEA404 Enforce secure coding practices
  • FEA406 Harden all the containers

5. Features not to be Tested

  • FEA515 Automate tests for frontend and backend code
  • FEA516 Manual testing

Both features do not require additional testing since they are the actual tools to be used for testing other features.

6. Approach

For testing we are going to several approaches. When developing, the developer of the feature will conduct unit testing while developing. After that, if the feature is new, the tester will start with explorative testing. If the feature is existing one, the tester will try to implement automation for testing.

Testing tools:

  • WAVE and Venngage tools for accessibility testing
  • Robot Framework for test automation

7. Item Pass/Fail Criteria

Criteria for passing is that there are no crashes and feature works as requested in the related user story.

8. Suspension Criteria and Resumption Requirements

Suspension criteria: - Tukko is not running - Tukko is crashing before testing - Other feature takes priority - Unclear what should be tested

Resumption criteria: - Tukko is online - Feature is prioritized - Testing criteria is clear

9. Test Deliverables

Testing results will be documented.

10. Testing Tasks

For the features that are to be tested, there should be test cases written, and clear passing criteria.

Also the enviroment for the testing should be up and running.

11. Environmental Needs

Testing requires internet access and access to Tukko instance.

12. Responsibilities

Main tester of the project is Minna Tapojärvi, but testing tasks can also be delegated if necessary.

13. Staffing and Training Needs

Testers should be familiarize themselves with the material available in the Future Factory site.

14. Schedule

Testing is running alongside with the development for the length of the project. As soon as something is ready to be tested, it should get tested as soon as possible.

15. Risks and Contingencies

Risks:

  • Only one main tester
  • Unfamiliar code language

16. Approvals

Plan should be approved by the team before testing.