Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Introduction

This document details how the Allow Payment methods by DOP 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.

DOP

A platform that allows the restaurant manager to edit the restaurant information such as the payment methods and cash limitation feature.

Sanity

CMS

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 the 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

localhost

https://dev-plk-web.es.rbi.tools/

https://staging-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)

Build and run the local environment and set the mocks

DOP user

User responsible for enabling the payment methods.

  • No labels