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 01:11, 2 September 2012
, 2 September 2012→Strategy
| Line 31: | Line 31: | ||
* 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 | * 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 | ||
* User scenarios and test cases that involve Marketplace's use of nav.mozPay is out of scope in this test plan - see Krupa Raj for more information on the testing approach there | |||
== Edge Cases == | == Edge Cases == | ||