docs: 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
|
){kind=icon}
){kind=icon}
tselit
changed the title
There was a problem hiding this comment.
Can we make this image a bit less wide so it's more readable without zooming in?
There was a problem hiding this comment.
Let's move this file to docs/testing/testplan.md
| Any person interested in testing the beta release of the Web Monetization extension. | ||
| There are no requirements for technical competencies. | ||
|
|
||
| We focus on functional test cases, and the goal is to record and report the actual behavior that was observed when it differs from the expected behavior. |
There was a problem hiding this comment.
Can move this line to Introduction, or remove it too.
There was a problem hiding this comment.
I'm not sure if we should say there's no requirements for technical competencies. We mention things like Web Monetization events being triggered and opening GitHub issues.
| ## Strategy | ||
|
|
||
| One of the strategic goals of the Interledger Foundation is to grow Web Monetization awareness and adoption such that there are 1,000 web monetized websites and 100,000 active Web Monetization users (by 31 December 2024). | ||
|
|
||
| One of the long-term goals is to grow Web Monetization adoption by a factor of 10, in the next 5 years (by December 2029) such that Web Monetization functionality is either native to the most widely used Web browsers, or readily available through browser extensions on Web browser stores and marketplaces. |
There was a problem hiding this comment.
I don't know why this is relevant to this document?
There was a problem hiding this comment.
Yeah, I don't think we need to discuss our internal business strategy in a test plan.
| ## Objectives | ||
|
|
||
| 1. Validating that, once installed, users can configure Web Monetization settings on the extension. | ||
| 2. Validating that once the extension is successfully connected to a digital wallet, a user is able to. |
There was a problem hiding this comment.
Additional context: Step 2 is missing the ending :)
|
|
||
| ### Tools and Resources | ||
|
|
||
| The resources and tools that you will need to test Web Monetization depend on your point of view. |
There was a problem hiding this comment.
Instead of "point of view", maybe The resources and tools that you will need to test Web Monetization depend on what you want to test.
| The resources and tools that you will need to test Web Monetization depend on your point of view. | ||
| The Web Monetization personas have different perspectives and needs for testing: | ||
|
|
||
| Persona 2: A website owner that wants to receive WM payments. |
There was a problem hiding this comment.
I think this line is meant to come out.
|
|
||
| Persona 2: A website owner that wants to receive WM payments. | ||
|
|
||
| | People | Hardware | Digital wallet | Environment & software | |
There was a problem hiding this comment.
Suggestions: Column title "Persona".
Then instead of Persona 1/2 in the other cells, maybe:
"Website Visitor: A visitor who wants to pay..."
"Website Owner: A site owner that wants to..."
|
|
||
| ### Reporting Issues | ||
|
|
||
| 1. Use any screen recording application to record the steps and results of your testing. |
There was a problem hiding this comment.
Could we/should we suggest and/or link to one?
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.