Confirmed users
2,959
edits
B2G/QA/WebAPI Test Plan/WebPayment: Difference between revisions
B2G/QA/WebAPI Test Plan/WebPayment (view source)
Revision as of 23:37, 4 November 2012
, 4 November 2012no edit summary
No edit summary |
|||
| Line 30: | Line 30: | ||
* API and JWT testing to ensure the JS API handles general valid and invalid input cases with the right success/error callbacks | * API and JWT testing to ensure the JS API handles general valid and invalid input cases with the right success/error callbacks | ||
* End-to-End functional testing with mozPay and trustworthy UI isolating marketplace bits out - Ensure trustworthy UI use cases work as expected | * End-to-End functional testing with mozPay and trustworthy UI isolating marketplace bits out - Ensure trustworthy UI use cases work as expected | ||
== Edge Cases == | |||
* First vs. second page of trusted context | |||
* Multiple JWT requests - same vs. different payment providers | |||
* Web activities firing during trusted UI flow (e.g. phone call) | |||
* No network connection | |||
* Temporary vs. permanent exit of trusted UI context | |||
* Returning to an existing trusted UI context from lockscreen, task switcher, etc | |||
* Trusted UI context in the task manager | |||
* Canceling purchases | |||
* Multiple trusted UI contexts running | |||
* Exit to task switcher, lockscreen, etc | |||
* Background pages & payments | |||
* Invalid JWT values | |||
* UTF-8 characters in JWT parameters | |||
* Keyboard use during trusted UI context | |||
== Signoff Criteria == | == Signoff Criteria == | ||