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 05:54, 31 August 2012
, 31 August 2012→Strategy
| Line 30: | Line 30: | ||
* End-to-End functional testing with mozPay and trustworthy UI - Ensure that end to end flows integrating across BlueVia, Marketplace, and Firefox OS fit together as a whole | * End-to-End functional testing with mozPay and trustworthy UI - Ensure that end to end flows integrating across BlueVia, Marketplace, and Firefox OS fit together as a whole | ||
* Availability and Resilience end-to-end testing - Many distributed components are involved in the web payments in mozPay, so we should be able downtime of a component or problems that a component in the process generates gracefully | * Availability and Resilience end-to-end testing - Many distributed components are involved in the web payments in mozPay, so we should be able downtime of a component or problems that a component in the process generates gracefully | ||
* Penetration Testing - There's trust on identification, receipt expiration, etc involved here, so we'll need to test for risks that could occur in any of those factors | |||
== Edge Cases == | == Edge Cases == | ||