/
[Test Cases] Allow Payment methods V2 - DOP

[Test Cases] Allow Payment methods V2 - DOP

Test

Market

Reference

Test scenario

Pre-condition

How to execute(step-by-step)

Expect Result

Comments

Test

Market

Reference

Test scenario

Pre-condition

How to execute(step-by-step)

Expect Result

Comments

1

PLK ES

DOP

Check the new enable-schedule-payment-method-control FF on LD

  1. FF enable-payment-methods-control enabled.

  1. Access DOP and edit a restaurant.

  2. Check if the new elements are available only when the new FF is enabled on LD:

  • Quick fill toggle

  • dropboxes

  1. The new elements must be available only when the new FF is enabled on LD.

  • default value

  • user can edit the field

2

PLK ES

DOP

[Allow payment null] Check dropbox when the page is loaded

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Check if the dropbox is not display.

  1. The dropbox must not be displayed.

 

3

PLK ES

DOP

[Allow payment null] Check the dropbox display: Click on deactivate

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Check if:

  • the dropbox is displayed only to the payment method that was deactivate.

  • the dropbox must be collapse by default.

  • the dropbox must display: Tomorrow date "Reactivate [DD/MM/YYYY] 11:00".

  1. Deactivate other payment methods and check the dropboxes.

  1. The dropbox is displayed only to the payment method that was deactivate.

  2. The dropbox must be collapse by default.

  3. The dropbox must display: Tomorrow date "Reactivate [DD/MM/YYYY] 11:00".

 

4

PLK ES

DOP

[Allow payment null] Check the dropbox elements: Click on deactivate

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Expand the dropbox and check:

  • if the dropbox adapt the layout as Figma's design.

  • "Deactivation Settings" title.

  • "Set how long..." description.

  • "Custom Deactivation Period" radion button.

  • "From" and "To" text fields.

  • "Permanent Deactivation" radion button.

  1. The dropbox must adapt the layout as Figma's design.

  2. The elements must be displayed as design.

 

5

PLK ES

DOP

[Allow payment null] Check the dropbox date/time fields default pre-filled - Allow payment null

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Expand the dropbox and check:

  • if the "From" field is pre-filled by default with today date and the current time.

  • if the "To" field is pre-filled by default with tomorrow date at 11am.

  1. The "From" field must be pre-filled by default with today date and the current time.

  2. The "To" field must be pre-filled by default with tomorrow date at 11am.

 

6

PLK ES

DOP

[Allow payment null] Check the dropbox date picker

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Expand the dropbox.

  4. Check the Date picker component.

  5. Pick other dates and check if the fields are update.

  1. the user must be able to pick another date/time by date picker.

  • If the user tries to insert manually and after delete using the backspace, the web page will be back to a blank page.

7

PLK ES

DOP

[Allow payment null] Check the dropbox validation date and time

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Expand the dropbox.

  4. Check if a validation message is displayed when the start date is greater than or equal to the end date:


"Start date cannot be less than or equal to the end date".

  1. Check if a validation message is displayed when the end date cannot be less than or equal to the start date:


"End date cannot be less than or equal to the start date".

  1. The validation messages must be displayed:

  • "Start date cannot be greater than or equal to the end date".

  • "End date cannot be less than or equal to the start date".

 

8

PLK ES

DOP

[Allow payment null] Check if the payment method toggle is enable when the initial date is a future date

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the deactivate button of a payment method.

  3. Set a period that the initial date is a future date.

  4. Check if the payment method toggle becomes activated automatically.

  5. Check if the dropbox is not hidden.

  1. The payment method toggle must be activated.

  2. The dropbox must not be hidden.

 

9

PLK ES

DOP

[Allow payment null] Check if the dropbox is not displayed when a payment method is activated

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on the activate button of a payment method.

  3. Check if the dropbox is not displayed.

  1. The dropbox must not be displayed.

 

10

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if a deactivation per period is saved properly - use default pre-filled values

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Click on deactivate button of a payment method.

  3. Using the default pre-filled values, click on Save button and confirm.

  4. Check if the deactivation was saved properly.

  5. Perform this test case scenario deactivating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

11

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if a deactivation per period is saved properly

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Set a period to deactivation for one payment method.

  3. Click on Save button and confirm.

  4. Check if the deactivation was saved properly.

  5. Perform this test case scenario deactivating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

12

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if a deactivation per period is saved properly - use a future date on the initial date

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Set a period to deactivation for one payment method future date on the initial date.

  3. Click on Save button and confirm.

  4. Check if the deactivation was saved properly.

  5. Perform this test case scenario deactivating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

13

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if a deactivation per permanent period is saved properly

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Select the Permanent Deactivation option.

  3. Click on Save button and confirm.

  4. Check if the deactivation was saved properly.

  5. Perform this test case scenario deactivating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

14

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if the activation is saved properly

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Select the active option for any payment method.

  3. Click on Save button and confirm.

  4. Check if the activation was saved properly.

  5. Perform this test case scenario activating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The activation must be saved to the correct restaurant and paymet methods.

 

15

PLK ES

DOP

[Allow payment deactivated per period] [Single restaurant] Check dropbox when the page is loaded

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that is deactivate by period.

  2. Check if the toggle of the payment method is disabled.

  3. Check if the dropbox is collapsed.

  4. Check if the dropbox content is filled:


"Reactivate [DD/MM/YYYY] HH:MM".

1.The toggle of the payment method must be deactivated.

  1. The dropbox mut be collapsed.

  2. The dropbox content must filled:


"Reactivate [DD/MM/YYYY] HH:MM" as the user had set as expiration period.

 

16

PLK ES

DOP

[Allow payment deactivated per period with a future date] [Single restaurant] Check dropbox when the page is loaded

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that is deactivate by period with a future date.

  2. Check if the toggle of the payment method is enabled.

  3. Check if the dropbox is collapsed.

  4. Check if the dropbox content is filled:


"Deactivate [DD/MM/YYYY] HH:MM".
"Reactivate [DD/MM/YYYY] HH:MM".

1.The toggle of the payment method must be activated.

  1. The dropbox mut be collapsed.

  2. The dropbox content must filled as the user had set as expiration period:


"Deactivate [DD/MM/YYYY] HH:MM"
"Reactivate [DD/MM/YYYY] HH:MM"

 

17

PLK ES

DOP

[Allow payment deactivated per period with expiration date finished] [Single restaurant] Check dropbox when the page is loaded

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that was deactivate by period but that the expiration date finished.

  2. Check if the toggle of the payment method is enabled.

  3. Check if the dropbox is not displayed anymore.

  1. The toggle of the payment method must be activated.

  2. The dropbox must not be displayed anymore.

 

18

PLK ES

DOP

[Allow payment activated] [Single restaurant] Check dropbox when the page is loaded

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that is activated.

  2. Check if the toggle of the payment method is enabled.

  3. Check if the dropbox is not displayed.

  1. The toggle of the payment method must be activated.

  2. The dropbox must not be displayed.

 

19

PLK ES

DOP

[Allow payment activated] [Single restaurant] Change from activated to inactivated

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that is activated.

  2. Click on to deactivate the payment method.

  3. Check if the dropbox is displayed.

  4. Set a period date.

  5. Click on Save button and confirm.

  6. Check if the activation was saved properly.

  7. Perform this test case scenario deactivating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

20

PLK ES

DOP

[Allow payment inactivated] [Single restaurant] Change from inactivated to activated

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that is deactivate.

  2. Click on to activated the payment method.

  3. Check if the dropbox is hidden.

  4. Click on Save button and confirm.

  5. Check if the activation was saved properly.

  6. Perform this test case scenario activating more than one payment method for a same restaurant.

  1. The values must be saved on Sanity.

  2. The activation must be saved to the correct restaurant and paymet methods.

 

21

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check if a deactivation is not saved when the user cancel the action

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Set a period to deactivation for one payment method.

  3. Click on Cancel button.

  4. Check if the deactivation was NOT saved/changed properly.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet method.

 

22

PLK ES

DOP

[Allow payment null] [Single restaurant] Check new Quick fill toggle

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Check if the new "Quick fill" toggle is displayed above payment methods.

  3. Enable the toggle and check if the new item is displayed of the list.

  4. Disable the toggle and check if the new item is removed of the list.

  1. A new item called "Quick fill" must be displayed above the payment mothod list.

 

23

PLK ES

DOP

[Allow payment null] [Single restaurant] Check Quick fill item - Deactive state

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Enable the "Quick fill" toggle.

  3. On "Quick fill" item click to deactivate.

  4. Check if:

  • all payment methods are deactivate too.

  • the dropbox is displayed for all the payment methods.

  • the dropbox is expanded only to "Quick fill" item.

  • the dropboxes must be pre-filled by default with today date and the current time and with tomorrow date at 11am.

  • all payment methods are deactivate too.

  • the dropbox is displayed for all the payment methods.

  • the dropbox is expanded only to "Quick fill" item.

  • the dropboxes must be pre-filled by default with today date and the current time and with tomorrow date at 11am.

 

24

PLK ES

DOP

[Allow payment null] [Single restaurant] Check replication configs from Quick fill item to payment methods

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Enable the "Quick fill" toggle.

  3. Change the configs from Quick fill item, such as deactive, set a period or select the permanent deactivation.

  4. Check if the same configs are replicated to all the payment methods.

  1. All changes applied on the Quick fill item must be replicated automatically to the payment methods.

 

25

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check Quick fill - Deactive and save

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Enable the "Quick fill" toggle.

  3. On "Quick fill" item click to deactivate.

  4. Check if all payment methods are deactivate automatically.

  5. Using the default pre-filled values, click on Save button and confirm.

  6. Check if the deactivation was saved properly for all the payment methods.

  1. The values must be saved on Sanity.

  2. The deactivation must be saved to the correct restaurant and paymet methods.

 

26

PLK ES

DOP x Sanity

[Allow payment null] [Single restaurant] Check Quick fill - Active and save

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Enable the "Quick fill" toggle.

  3. On "Quick fill" item click to activate.

  4. Check if all payment methods are activated automatically.

  5. Click on Save button and confirm.

  6. Check if the activation was saved properly for all the payment methods.

  1. The values must be saved on Sanity.

  2. The activation must be saved to the correct restaurant and paymet methods.

 

27

PLK ES

DOP

[Allow payment null] [Single restaurant] Check if Quick fill toggle is disabled automatically

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit a restaurant that the "Allow payment methods" is null.

  2. Enable the "Quick fill" toggle.

  3. On "Quick fill" item click to deactivate.

  4. Change any config in any payment method, such as, active or change the period.

  5. Check if the "Quick fill" toggle is disabled automatically.

  6. Check if the Quick fill item is hidden.

  1. The "Quick fill" toggle is disabledwhen the user changes any config in any payment method.

 

28

PLK ES

DOP

[Multiple restaurants] Check elements when more than one restaurant is edited

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Check if:

  • "Quick fill" is disabled.

  • Payment methods items are as "null".

  • Dropboxes are not displayed.

  1. "Quick fill" must be disabled.

  2. Payment methods items must be as "null".

  3. Dropboxes must not be displayed.

 

29

PLK ES

DOP x Sanity

[Multiple restaurants] Check deactivation scenarios to multiple-restaurants

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Check if the deactivation feature is working when the user is editing more than one restaurants.

  • dropboxes.

  • pre-filled values.

  • validation messages to invalid periods.

  1. Set different periods and save.

  2. Check if the deactivation was saved properly for the payment methods and only for the restaurants that were selected.

  1. The deactivation behavior must work for one or more restaurants.

  2. The values must be saved on Sanity.

  3. The deactivation must be saved to the correct restaurants and paymet methods.

 

30

PLK ES

DOP x Sanity

[Multiple restaurants] Check activation scenarios to multiple-restaurants

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Check if the activation feature is working when the user is editing more than one restaurants.

  • dropboxes.

  1. Click to activate the payment methods.

  2. Check if the activation was saved properly for the payment methods and only for the restaurants that were selected.

  1. The activation behavior must work for one or more restaurants.

  2. The values must be saved on Sanity.

  3. The activation must be saved to the correct restaurants and paymet methods.

 

31

PLK ES

DOP

[Multiple restaurants] [Regression testing] on the confirmation modal

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Deactivate or activate the payment methods.

  3. Click on save and check if the confirmation modal is displayed properly.

  4. Check if the amount of the restaurants is correct.

  1. The confirmation modal must be displayed properly.

 

32

PLK ES

DOP

[Multiple restaurants] [Regression testing] Do not change the values, but saving

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Don't change anything and click to save.

  3. Check if no restaurants must have the payment methods changed.

  1. No restaurants must have the payment methods changed.

 

33

PLK ES

DOP

[Multiple restaurants] [Regression testing] Cancel bulk update

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Access DOP and edit multiple restaurants that already allow payment methods set.

  2. Deactivate and activate the payment methods.

  3. Click on save.

  4. On confirmation modal click to cancel the update.

  5. Check if no restaurants must have the payment methods changed.

  1. No restaurants must have the payment methods changed.

 

34

PLK ES

DOP

Check if the layout is following the Figma's design

  1. FF enable-payment-methods-control enabled.

  2. FF Enable schedule payment methods control enabled.

  1. Check if the layout is following the Figma's design in all elements:

  • Quick fill toggle.

  • dropbox

  • date fields

  • date-picker

  1. Check if the layout is adaptative when the user expands and collapses the dropbox.

  1. The layout must be following the Figma's design.

 

Related content

Feature Deployments status - Support Tool
Feature Deployments status - Support Tool
Read with this
[Test Cases] Allow Payment methods - V2 - Sanity
[Test Cases] Allow Payment methods - V2 - Sanity
More like this
[Solution] Allow Payment Methods v2
[Solution] Allow Payment Methods v2
Read with this
[Test Execution] Allow Payment methods - V2 - Sanity
[Test Execution] Allow Payment methods - V2 - Sanity
More like this
[Test Execution] Allow Payment methods by DOP
[Test Execution] Allow Payment methods by DOP
More like this
[Test Execution] [Mobile] Allow Payment methods by DOP
[Test Execution] [Mobile] Allow Payment methods by DOP
More like this