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 21:25, 12 September 2012
, 12 September 2012→Infrastructure
| Line 77: | Line 77: | ||
* 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 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 | ||
* 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) | * 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 == | == Automation == | ||