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

← Older edit

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

Revision as of 02:12, 16 November 2012

811 bytes removed , 16 November 2012

→‎Test Cases

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
 == Edge Cases ==
-* Multiple payments chained together
+* First vs. second page of trusted context
-* Different payment providers (i.e. JWT typ), valid vs. invalid
+* Multiple JWT requests - same vs. different payment providers
-* Payment Provider Server Downtime or Failure
+* Web activities firing during trusted UI flow (e.g. phone call)
-* Invalid JWT requests
+* No network connection
-* Switching app contexts post the call of mozPay
+* Temporary vs. permanent exit of trusted UI context
-* Interception and altering of content to be rendered within trustworthy UI chrome
+* Returning to an existing trusted UI context from lockscreen, task switcher, etc
-* Valid vs. invalid application keys
+* Trusted UI context in the task manager
-* Expired vs. Non-Expired Payment Requests and Refunds
+* Canceling purchases
-* Different country codes
+* Multiple trusted UI contexts running
-* Different locale text with JWT request
+* Exit to task switcher, lockscreen, etc
-* Optional vs. required parameters for JWT request
+* Background pages & payments
-* Default pricing vs. locale-specific pricing
+* Invalid JWT values for client-side validation
-* Different country currencies
+* Keyboard use during trusted UI context
-* Completed vs. Canceled Purchases
-* Marketplace Server Downtime or Failure
-* Registered application for in-app payments vs. non-registered
-* Valid vs. invalid postback and chargeback URLs on successful payments and refunds
-* Default price vs. no default price
-* Valid vs. invalid amounts
-* Application server response vs. no response on transaction response confirmation
-* Successful vs. unsuccessful authentication
-* Valid vs. invalid transaction IDs for a refund
 == Signoff Criteria ==
@@ Line 63: / Line 53: @@
 == Test Case Management ==
+* Test cases shall be tracked in MozTrap tagged with "gaia" and "payments"
 == Infrastructure ==
+* A mock payment provider shall be used for testing the payment API and trustworthy UI - [https://github.com/ferjm/mockpayprovider Mock Payment Provider]
+* A payments test case repository shall be used for tracking test cases - [https://github.com/ferjm/Payment-tests Payment Tests]
 == Automation ==
-== Smoke Tests ==
+'''Tracking bug:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=777023 bug 777023]
+* Zac Campbell is looking into this - primarily aiming to target front-end automation in Marionette in python
-== Basic Functional Tests ==
+== Test Cases ==
-== Exploratory Tests ==
+Test cases for this feature can be found [https://moztrap.mozilla.org/manage/cases/?filter-suite=183 here].
-== Open Questions ==
+== References ==
-* Does the trustworthy UI provide any context of where the HTML 5 content served inside the UI is from? In other words, how do I know the content I've received is safe or not? Is the URL of the content shown in the trustworthy UI to mitigate this?
+* [https://docs.google.com/spreadsheet/ccc?key=0AiZoGR-iOAlUdDZFdjREckFkb3dkSWl0Y0lIRmp2d0E#gid=0 Initial Test Pass on 11/9 & 11/12]
-* How come postback and chargeback URLs are specified in the JWT request and Mozilla Marketplace? What's the difference? Is the one on marketplace the default callback URLs if a callback URL isn't specified?
-* How exactly does the identity pieces affect the in-app payments flow? I've noticed it's stated it's the responsibility of the "payment provider" - from the context of mozPay, is that a black box then?
-* What's the purpose of productdata? How does it affect the in-app purchase?
-* How exactly does the application server send the 200 OK with the order ID back to the payment provider?