[Test Plan] Fraudulent user block (Admin App x Whitelabel)

Owned by Almeida, Gabriel
Last updated: Aug 01, 2024
2 min read

Introduction

This document details how the Fraudulent User Block feature should be tested

Test Scope

In Scope

Application

Description

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

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

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/

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

Traceability Matrix / Test Report

Test Case

Test Execution Date

Test Status

Test Case

Test Execution Date

Test Status

[Admin] Admin user should block an fraudulent account successfully

Aug 1, 2024

done

[Admin] Admin user should unblock an user successfully

Aug 1, 2024

done

[Whitelabel][Logged In] Blocked user should not be able to update his profile

Aug 1, 2024

in progess

Awaiting PR merge to validate blocking messages

[Whitelabel][Logged In] Blocked user should not be able to place new orders

Aug 1, 2024

in progress

Awaiting PR merge to validate blocking messages

[Whitelabel][Logged In] Blocked user should be disconnected after 01 hour

Aug 1, 2024

blocked

 

Awaiting PR merge to validate disconnection timeout

[Whitelabel][Logged In] Blocked user should not be able to generate QR Code

Aug 1, 2024

done

[Whitelabel][Logged Off] Blocked user should not be able to sign in

Aug 1, 2024

done

[Whitelabel][Logged Off] Blocked user should not be able to sign in using Social Login

Aug 1, 2024

done

[Whitelabel][Logged Off] Formerly blocked user should be able to sign in again after being unblocked

Aug 1, 2024

done

[Email Service] Service should send email to user once block event is triggered

Aug 1, 2024

in progress

[Email Service] Service should send email to user once unblock event is triggered

Aug 1, 2024

in progress

[Braze] User communication preferences should be updated when user is blocked

 

blocked

 

Requested Braze access in order to proceed with Test

[Braze] User communication preferences should be updated when user is unblocked

 

blocked

Requested Braze access in order to proceed with Test