OpenMAVN / PM

OpenMAVN project management
MIT License
0 stars 3 forks source link

[Mobile] Fail cases of voucher buying aren't having correct Error message in Application #127

Closed Mamyako closed 4 years ago

Mamyako commented 4 years ago

Environment: iOS software version 13.4.1/ Android software version 10

Note: related to #29 ticket Cases:

  1. SmartVouchers component can't reserve a voucher for required campaign.
  2. Payrexx is unavailable

Note for case 1: When last remaining voucher is available for some campaign, then reservation flow should be started from 2 customer accounts

Steps for case 1:

  1. Log in to mobile application as a customer using credentials
  2. Tap offers tab at the bottom menu of the application
  3. Tap to any available voucher with only one voucher left
  4. Tap Redeem offer button from two accounts

Actual result: User that tapped later see error message "Oops! It look like something went wrong. If the issue continues, contact our friendly customer service" Expected result: User that tapped later see error message "Smart voucher campaign does not have available vouchers"

Precondition for case 1: Payrexx is unavailable

Steps for case 2:

  1. Log in to mobile application as a customer using credentials
  2. Tap offers tab at the bottom menu of the application
  3. Tap any available voucher
  4. Tap Redeem offer button

Actual result: User that tapped later see error message "Oops! It look like something went wrong. If the issue continues, contact our friendly customer service" Expected result: User that tapped later see error message "There's a problem with payment provider" 19.jpg

Mamyako commented 4 years ago

@ElenaBelyavskaya please, review the description

pddimitrova commented 4 years ago

@Mamyako Where (in which story) are these message requirements described?

Mamyako commented 4 years ago

@pddimitrova Messages should be different but their text isn't confirmed for now, that's why need some review from @ElenaBelyavskaya

pddimitrova commented 4 years ago

@Mamyako Then this is not a bug rather than a regular story for adding messages that had not previously existed.

Mamyako commented 4 years ago

Sure, I'll change label

pddimitrova commented 4 years ago

@ElenaBelyavskaya @MarlonMaercz In order that we move this to Ready for development, we will need copies for such cases

ElenaBelyavskaya commented 4 years ago

@pddimitrova for now added the texts to https://docs.google.com/spreadsheets/d/1e38PERmWzvvK777QtuBPEFm1jAa_lVZZ/edit#gid=382811706, rows 599 and 600

pddimitrova commented 4 years ago

@ElenaBelyavskaya These are the errors we need messages for: SmartVoucherCampaignNotFound SmartVoucherCampaignNotActive NoAvailableVouchers PaymentProviderError SmartVoucherNotFound CustomerHaveAnotherReservedVoucher

I can create a mobile subtask as soon as we have the copies.

ElenaBelyavskaya commented 4 years ago

@pddimitrova 2 of these errors are mentioned in the story already (NoAvailableVouchers, PaymentProviderError)

pddimitrova commented 4 years ago

The errors with provided error message are handled. CustomerHaveAnotherReservedVoucher will be handled in #165. Closing this.