Introduction
This document details how the Loyalty Balance Information feature should be tested
Test Scope
In Scope
Application | Description |
|---|---|
Whitelabel | Whitelabel is used by guests to make new orders and collect loyalty points |
Admin Tool | Admin Tool will be used by admin agents which can read guests loyalty points, balance, history, etc.. |
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 |
|---|---|
Whitelabel | |
Admin Tool |
Test Management
Test Actors
User Role | Description |
|---|---|
Guest | User will be placing successfull orders on Whitelabel, gather and spend loaylty points |
Admin User | Will have access to guests loyalty balance |
Traceability Matrix / Test Report
Test Case | Test Execution Date | Test Status |
|---|---|---|
[Admin Tool] Agent should be able to check total Loyalty Points balance information | BACKLOG | |
[Admin Tool] Agent should be able to validade points history per order | BACKLOG | |
[Admin Tool] Successful order using Loyalty Points credit should debit points from current balance information | BACKLOG | |
[Admin Tool] Successful order should credit new points to current balance information | BACKLOG | |
[Admin Tool] Cancelled order should not update current Loyalty Balance information | BACKLOG |
0 Comments