Table of Contents

minLevel	1
maxLevel	6
outline	false
style	default
type	list
printable	true

Admin App

Test Case	Admin user should block an fraudulent account successfully
Application	Admin App

Code Block

language	none

Feature: Fraudulent User Block
  Background: Admin Home Page
    Given I have accessed the Admin Page as admin user
  
  Scenario: Admin user should block an fraudulent account successfully
    Given I have access the fraudulent user profile page
    When I block the fraudulent user profile
    Then user status should be tagged as "blocked"

Test Case	Admin user should unblock an fraudulent account successfully
Application	Admin App

Code Block

language	none

Feature: Fraudulent User Block
  Background: Admin Home Page
    Given I have accessed the Admin Page as admin user
  
  Scenario: Admin user should unblock an fraudulent account successfully
    Given I have access the fraudulent user profile page
    And the user is already blocked
    When I unblock the fraudulent user profile
    Then user status should be tagged as "unblocked"

Whitelabel App

Test Case	Blocked user should not be able to update his profile
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
    And I have successfully signed in
  
  Scenario: Blocked user should not be able to update his profile 
    Given I have accessed the Settings page
    And I attempt to update my user profile 
    Then I should be logged off from Whitelabel

Test Case	Blocked user should not be able to place new orders
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
    And I have successfully signed in
  
  Scenario: Blocked user should not be able to place new orders
    Given I have a order ready to be placed
    When I access the checkout page
    And I try so place a new order
    Then I should be logged off from Whitelabel

Test Case	Blocked user should be disconnected after 01 hour
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
  
  Scenario: Blocked user should be disconnected after 01 hour
    Given I signed in on Whitelabel
    When my profile is blocked on Admin
    But I don't do any critical operation
    And my user profile has been logged in for one hour
    Then I should be logged off from Whitelabel

Test Case	Blocked user should not be able to generate QR Code
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
  
  Scenario: Blocked user should not be able to generate QR Code
    Given I signed in on Whitelabel
    When my profile is blocked on Admin
    And I attempt to generate a QR Code to place on order on Kiosk
    Then I should be logged off from Whitelabel

Test Case	Blocked user should not be able to sign in
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
  
  Scenario: Blocked user should not be able to sign in
    Given I have valid credentials
    When I attempt to Sign In on Whitelabel
    But my profile is blocked
    Then I should see the message "CUENTA BLOQUEADA TEMPORALMENTE"

Test Case	Blocked user should not be able to sign in using Social Login
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
  
  Scenario: Blocked user should not be able to sign in using Social Login
    Given I have valid credentials
    When I attempt to Sign In on Whitelabel using Social Login 
    But my profile is blocked
    Then I should see the message "CUENTA BLOQUEADA TEMPORALMENTE"

Test Case	Formerly blocked user should be able to sign in again after being unblocked
Application	Whitelabel

Code Block

language	none

Feature: Fraudulent User Block
  Background: Whitelabel
    Given I have accessed the Whitelelabel home page
  
  Scenario: Formerly blocked user should be able to sign in again after being unblocked
    Given I have valid credentials
    When I attempt to Sign In on Whitelabel using Social Login 
    But my profile is blocked
    Then I should see the message "CUENTA BLOQUEADA TEMPORALMENTE"

Service Notification

Test Case	Service should send email to user once block event is triggered
Application	Service Notification

Code Block

language	none

Feature: Fraudulent User Block  
  Scenario: Service should send email to user once block event is triggered
    Given a fraudulent user has been blocked on Admin App
    Then I should send a Notification Message to the user email

Test Case	Service should send email to user once unblock event is triggered
Application	Service Notification

Code Block

language	none

Feature: Fraudulent User Block  
  Scenario: Service should send email to user once unblock event is triggered
    Given a user has been unblock on Admin App
    Then I should send a Notification Message to the user email

Braze

Test Case	User communication preferences should be updated when user is blocked
Application	Braze

Code Block

language	none

Feature: Fraudulent User Block  
  Scenario: User communication preferences should be updated when user is blocked
    Given a user has been blocked on Admin App
    Then the following fields should be updated
      | preference      | value        |  
      | email_subscribe | unsubscribed |
      | marketingEmail  | false        |
      | rewardsEmail    | false        |
      | push_subscribe  | unsubscribed |
      | marketingPush   | false        |
      | rewardsPush     | false        |
      | sms_subscribe   | false        |
      | Email Opt In    | false        |

Test Case	User communication preferences should be updated when user is unblocked
Application	Braze

...

language	none

...

Scenario Title	Pre-conditions	Steps	Expected Result
Ensure the offer dropdown is editable.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Attempt to type an offer name into the dropdown.	The dropdown field should allow the user to type an offer name.
Verify that search results appear quickly when typing an offer name.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Start typing an offer name.	Search results should be displayed within a few seconds of typing.
Ensure offers can be searched with at least three characters.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Type a string with less than three characters.	No offers should be displayed in the dropdown.
Verify that the search returns offers containing the typed characters in any part of the offer title (beginning, middle, or ending).	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Type a string that matches the beginning of an offer title (e.g., "Off"). Type a string that matches the middle of an offer title (e.g., "ferN"). Type a string that matches the ending of an offer title (e.g., "Name").	When typing a string that matches the beginning of an offer title, the relevant offers should be displayed. When typing a string that matches the middle of an offer title, the relevant offers should be displayed. When typing a string that matches the ending of an offer title, the relevant offers should be displayed.
Verify that the search is case-insensitive.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Type an offer name using mixed case (e.g., "OfferName").	The dropdown should display the correct offer regardless of the case used in the search.
Ensure the dropdown displays existing offers in alphabetical order.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Type an offer name with at least three characters.	The dropdown should display all existing offers containing the search string, sorted in increasing alphabetical order.
Warn the user when the offer does not appear in the list.	Admin Tools access Sanity Access	Access the Admin Support tool. Click on the Offers button to open the form. Click on the "Assign offer dropdown" field. Type a non-existing offer name (less than three characters or invalid).	A warning message should display stating that the offer does not appear in the list.
Verify the feature toggle for the new dropdown functionality.	Admin Tools access Sanity Access Launch Darkly	Access the Admin Support tool. Toggle the feature on and off in the test environment. Click on the Offers button to open the form while the feature is toggled off. Check the "Assign offer dropdown" field.	When toggled off, the dropdown should revert to the previous non-editable state. When toggled on, the new editable dropdown functionality should be available.

Versions Compared

Old Version 1

New Version 2

Key

Admin App

Admin user should block an fraudulent account successfully

Admin user should unblock an fraudulent account successfully

Whitelabel App

Blocked user should not be able to update his profile

Blocked user should not be able to place new orders

Blocked user should be disconnected after 01 hour

Blocked user should not be able to generate QR Code

Blocked user should not be able to sign in

Blocked user should not be able to sign in using Social Login

Formerly blocked user should be able to sign in again after being unblocked

Service Notification

Service should send email to user once block event is triggered

Service should send email to user once unblock event is triggered

Braze

User communication preferences should be updated when user is blocked

User communication preferences should be updated when user is unblocked

Page Comparison

Versions Compared

Old Version 1

New Version 2

Key

Admin App

Admin user should block an fraudulent account successfully

Admin user should unblock an fraudulent account successfully

Whitelabel App

Blocked user should not be able to update his profile

Blocked user should not be able to place new orders

Blocked user should be disconnected after 01 hour

Blocked user should not be able to generate QR Code

Blocked user should not be able to sign in

Blocked user should not be able to sign in using Social Login

Formerly blocked user should be able to sign in again after being unblocked

Service Notification

Service should send email to user once block event is triggered

Service should send email to user once unblock event is triggered

Braze

User communication preferences should be updated when user is blocked

User communication preferences should be updated when user is unblocked