B2G/QA/WebAPI Test Plan/WebPayment: Difference between revisions

B2G/QA/WebAPI Test Plan/WebPayment (view source)

Revision as of 23:21, 29 October 2012

423 bytes removed , 29 October 2012

→‎Strategy

Jsmith

Confirmed users

2,959

edits

@@ Line 24: / Line 24: @@
   |}
-== Strategy ==
+== Overview ==
-* API testing to ensure the JS API handles general valid and invalid input cases with the right success/error callbacks
+This document will cover testing the web payment API that tests the API itself and the trustworthy UI used on device. Other portions of payment testing such as identity integration, marketplace integration, etc shall be covered in different docs. Therefore, the testing is broken into two areas here:
-* JWT generation testing to analyze the different values allowed to be used in calling nav.mozPay and its resulting effects
-* 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
+* API and JWT testing to ensure the JS API handles general valid and invalid input cases with the right success/error callbacks
-* 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
+* End-to-End functional testing with mozPay and trustworthy UI isolating marketplace bits out - Ensure trustworthy UI use cases work as expected
-* 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 ==