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

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

414 bytes removed , 29 October 2012

Confirmed users

2,959

edits

@@ Line 70: / Line 70: @@
 == Infrastructure ==
-* A generic test application is going to be needed that allows for various different JWT requests for payments and refunds
+* A mock payment provider shall be used for testing the payment API and trustworthy UI - [https://github.com/ferjm/mockpayprovider]
-* A mock payment provider will be needed to be able to write automation against for this payment API. Additionally, it will be needed probably to help diagnose problems that are in the API vs. BlueVia's side
+* A payments test case repository shall be used for tracking test cases - [https://github.com/ferjm/Payment-tests]
-* Control over the payment provider test server will be needed to be able understand what's going on server side and be able to affect it as needed (e.g. invoke downtime or incorrect values)
-* Marketplace dev server will be needed to be used to register apps for testing to produce the public and private keys for in-app payments
 == Automation ==