Development Environment
This topic lists a number of test cases that will help you jump-start your testing efforts in a development environment.
Testing your Integration with a Mock Provider
Before proceeding, make sure you have your development environment setup for testing with a mock provider. Also make sure you understand how to use the mock provider for simulating response statuses and error messages. If you imported our Postman Collection for Testing Purposes, you can use it to jump-start your testing efforts.
Test Case | Completed |
---|---|
Verify succesful card tokenization using your method of choice for collecting a user's card information. | |
Handle synchronous payment flows and operations. To test, simulate a provider response status. | |
Handle asynchronous payment flows and operations. To test,
simulate a provider response status. Note: Only execute this test case if the provider handles flows asynchronously. |
|
Handle response errors in synchronous payment flows and operations. Pass in test amounts to simulate error responses. | |
Handle response errors in asynchronous payment flows and operations. Pass in test amounts to
simulate error responses. Note: Only execute this test case if the provider handles flows asynchronously. |
Testing your Integration with Real-life Providers
The next step after testing your integration using a mock provider, is to test your integration using actual providers. Before proceeding, make sure you updated your setup to use actual providers in the development environment.
Test Case | Completed |
---|---|
Verify succesful card tokenization using your method of choice for collecting a user's card information. | |
Handle synchronous payment flows and operations. | |
Handle asynchronous payment flows and operations. Note: Only execute this test case if the processor handles flows asynchronously. |
Last modified January 4, 2022