Introduction
This document details how the Fraudulent User Block feature should be tested
Test Scope
In Scope
Application | Description |
|---|---|
Whitelabel | Whitelabel is used by fraudulent users to generate new faker orders and it’s the main entry point for such type of orders |
Admin Tool | Admin Tool will be used to block fraudulent accounts |
Email Service (notification_service) | The Notification Service is responsible for sending emails warning users that their account is blocked |
Braze | Once user is blocked / unblocked on Admin, it’s Braze’s profile should be updated to enable or disable Marketing communications |
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 |
|---|---|
Whitelabel | |
Admin Tool | ToDo: Collect admin dev env URL |
Whitelabel Endpoint | ToDo: Collect whitelabel endpoint |
Test Deliverables
Test Cases
Test Plan (this document)
Bug Tasks
Test Management
Test Actors
User Role | Description |
|---|---|
User | User will be placing successfull orders on Whitelabel |
Fraudulent User | Fraudulent user will be placing faker orders on Whitelabel |
Admin User | Will be used to block fraudulent users |
Add Comment