Add maestro E2E test for purchase through paywall #1636
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| # config.yaml | ||
|
|
||
| executionOrder: | ||
| continueOnFailure: false | ||
|
|
||
| flows: | ||
| - e2e_tests/* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # This flow tests the purchase through paywall flow. | ||
| # It navigates to the purchase screen, verifies initial entitlements, | ||
| # presents the paywall, makes a purchase, and verifies entitlements update. | ||
|
|
||
| appId: com.revenuecat.automatedsdktests | ||
| name: Purchase through paywall | ||
|
|
||
| --- | ||
| - clearState | ||
| - pressKey: home | ||
| - launchApp | ||
| - assertVisible: "Test Cases" | ||
| - tapOn: | ||
| text: "Purchase through paywall" | ||
| - assertVisible: "Entitlements: none" | ||
| - assertVisible: "Present Paywall" | ||
| - tapOn: | ||
| text: "Present Paywall" | ||
| - assertVisible: "Paywall V2" | ||
| - tapOn: | ||
| text: "Yearly" | ||
| - tapOn: | ||
| text: "Continue" | ||
| - runFlow: | ||
| file: ../utils/confirm_purchase.yaml | ||
| - assertVisible: "Entitlements: pro" | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # This flow handles the Test Store purchase confirmation. | ||
|
|
||
| appId: com.revenuecat.automatedsdktests | ||
| name: Confirm purchase - Test Store Purchase Alert | ||
|
|
||
| --- | ||
| - assertVisible: "Test.*Purchase" | ||
| - tapOn: | ||
| text: "(?i)test valid purchase" | ||
|
Contributor
There was a problem hiding this comment. Looking at this issue, maybe we could do something like this instead: This way we tap on the exact string. But not a blocker I would say. I think what you have also works!
Member
Author
There was a problem hiding this comment. Nice suggestion! My idea was to keep it case insensitive with the purpose of changing the texts in the natives to have them match. So I've created RevenueCat/purchases-android#3314 which makes the texts the same (which I think is desirable regardless 😄). And also #1724 for the same alert in this repo |
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be worth to add snapshots of this paywall + The screen after a purchase is completed and perform some verification on those snapshots, so we're aware of unintended changes? Of course, this can come in follow-up PRs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. Will take a note to add it to a follow-up PR. Thanks for the suggestion!