[Test Plan] Visual info of accepted cards
- Hellen Rodrigues Magalhaes
- 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 Visual info of accepted cards feature should be tested
Test Scope
In Scope
Application | Description |
|---|---|
Whitelabel | Whitelabel’s is where guests finish placing their orders, either it’s on mobile or the web. |
Launch Darkly | Feature management platform that allows development teams to control and manage feature flags to release software updates safely and continuously. |
Lokalise | Translation management platform that helps teams streamline the localization process for their software and content. |
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 Plan (this document)
Test Cases
Bug Tasks
Test Management
Test Actors
User Role | Description |
|---|---|
User | User will be placing successful orders on Whitelabel |
Developer user | User responsible for enabling the FF on the Launch Darkly (LD) and setting which cards are accepted for each brand and country |
Traceability Matrix / Test Status