[Test Plan] Block user from closing window
- Almeida, Gabriel
- 1 Introduction
- 1.1 Test Scope
- 1.1.1 In Scope
- 1.1.2 Out of Scope
- 1.2 Quality Objective
- 1.3 Test Methodology
- 1.4 Testing Tools
- 1.4.1 Testing Tools
- 1.4.2 Test Deliverables
- 1.5 Test Management
- 1.6 Test Actors
- 1.7 Traceability Matrix / Test Status
- 1.1 Test Scope
Introduction
This document details how the Block User From Closing Window feature should be tested
Test Scope
In Scope
Application | Description |
|---|---|
Whitelabel | Whitelabel’s is were guests finishes placing their orders, either it’s on mobile or web. |
Out of Scope
Application | Description |
|---|---|
POS |
Won’t be tested as this application won’t be changed by this feature's development |
Kiosk | |
Call Center |
Quality Objective
Ensure that all Acceptance Criteria has been met
Ensure that all Test Cases has been executed and have passed
Ensure that all bugs found has been fixed and retested before release
Test Methodology
Exploratory Testing
Functional Testing
Testing Tools
Testing Tools
Platform | Version | Description |
|---|---|---|
macOS | 15.0 |
|
Google Chrome | 126.0 |
|
Android Device | 14.0 |
|
iOS Device | 18.0 |
|
Insomnia | 9.3.0 | For backend tests |
Testing Subjects
Subject | Description |
|---|
Subject | Description |
|---|---|
Whitelabel | https://dev-plk-web.es.rbi.tools/ |
Test Deliverables
Test Cases
Test Plan (this document)
Bug Tasks
Test Management
Test Actors
User Role | Description |
|---|---|
User | User will be placing successful orders on Whitelabel |
Traceability Matrix / Test Status
Test Case | Test Execution Date | Test Status |
|---|---|---|
| Backlog | |
User should be redirected to order cart if payment popup is closed |
| Backlog |
| Backlog |