Introduction
This document details how the Integrating Loyalty Data into BookingAll Order Flows feature should be tested
Test Scope
In Scope
Application | Description |
|---|---|
Partners-Api | Whitelabel’s is where guests finish placing their orders, either it’s on mobile or the web. |
Out of Scope
Application | Description |
|---|---|
Whitelabel | Won’t be tested as this application won’t be changed by this feature's development |
Rbi backend services |
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 | 14.1 |
|
Google Chrome | 131.0 |
|
Testing Subjects
Subject | Description |
|---|---|
Partners-api documentation | https://euw3-dev-plk-partners-api.rbictg.com/docs/market/#tag/OrderAPI/operation/getOrder |
Subject | Description |
|---|---|
Partners-api |
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 |
Partner user | User that will be consuming the new data added |
Traceability Matrix / Test Status
Scenario | Brand | Country | Test scenario | Test Execution Date | Test Status |
1 | BK | ES | Check if the Loyalty Id is returned on getOrder endpoint for drive-thru orders |
|
|
2 | BK | ES | Check if the Loyalty Id is returned on getOrder endpoint for delivery orders |
|
|
3 | BK | ES | Check if getOrder works if the Loyalty Id is not saved in database |
|
|
4 | BK | ES | Check if getOrder works if the Loyalty Id is saved as an empty string |
|
|
5 | BK | ES | Check if documetation reflects the changes |
|
|
6 | BK | ES | Check if the Loyalty Id returned on getOrder endpoint match with the correct user Loyalty Id |
| |
| |||||
| |||||
| |||||
|
Add Comment