-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(testing/plan): add functional test plan #596
Conversation
add test plan
Add 7 sections.
Add risks and test case diagram
add assets for testing
add a mindmap of the test cases
this folder was meant to be in the test/testplan folder
a folder for the test plan assets
add 3 basic test cases
Added the following test cases: - Pay one-time when extension funds are insufficient. - Disable continuous payments.
Added the following 4 test cases: - Pay one-time when extension funds are insufficient - Disable continuous payments - Change rate of pay and View available balance - Disconnect wallet
- update test case for a partial one-time payment success due to insufficient extension funds - add test case to pay until the extension runs out of funds
Extension builds preview
|
docs/testing/testplan.md
Outdated
**Steps**: | ||
|
||
1. Visit a monetized website that has multiple receiving wallet addresses or payment pointers: | ||
a. You can visit [roamancing.com/naturallyours](http://roamancing.com/naturallyours/). |
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.
we should say how many wallet addresses are in this page and whether they're real or test. This way, under expected results, the user will know how to math the remaining balance.
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.
Cool, cool.
docs/testing/testplan.md
Outdated
b. Alternatively, you can use the [Test Playground](#Test-Playground) to add payment pointers or wallet addresses from different wallet providers. | ||
As an example, you can add all of the following wallet addresses to the playground: | ||
|
||
- https://ilp.rafiki.money/wm-dev |
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.
Does this address need to change?
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.
I removed the test playground alternative from the functional test cases.
I think the test case text is less cluttered, and reads a little easier.
docs/testing/testplan.md
Outdated
- [storytogo.ca](https://storytogo.ca) | ||
- [roamancing.com](https://roamancing.com) | ||
|
||
2. Visit the Web Monetization Playground, and add any Fynbos Canada wallet addresses. Here are a few payment pointers that you can use: |
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.
I think the Fynbos Canada reference here is supposed to be Gatehub.
**Expected results**: | ||
|
||
1. The wallet owner receives an interaction prompt from their wallet to authorize the connection and access to the amount. | ||
2. On accepting, you get shown the message "Your wallet is now successfully connected to the extension." |
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.
Not a huge thing, but step 1 references the wallet owner and step 2 references "you". These references refer to the same person.
docs/testing/testplan.md
Outdated
|
||
| Web monetized websites | Non monetized websites | | ||
| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :------------------------------------------------------------------------------ | | ||
| Extension icon: active (full color), with a green tick | Extension icon: active (full color), but with a red X | |
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.
Test ID 3 below shows an image for non web monetized websites. None of the other tables contain any other assets. Was this intentional?
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.
I've added a final round of comments/questions. In general, I think you're just about there so I'm approving this.
… auto key addition to wallet
…'s new setup & settings pages
…netization-extension into mt/docs/test/testplan
* chore(deps): update dependency tsx to ^4.19.2 (#715) * chore(deps): update dependency @testing-library/jest-dom to ^6.6.3 (#717) * fix(deps): update dependency react-router-dom to ^6.28.0 (#718) * chore(deps): update dependency tailwind-merge to ^2.5.4 (#716) --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Context
Document a test plan for the Web Monetization extension, detailing the functional test cases.
Closes #290.
Changes proposed in this pull request
The test plan in markdown format, alongside an image asset that visualises how the test cases relate to each other.