Testing Overview

Once you have built one or more parts of your integration, you will want to test them. 

We recommend building a series of tests that can be used to test out your integrations initially, as well as on an ongoing basis as you make changes to your integration. We recommend three types of tests:

• Unit Tests: Unit Tests are small, localized tests aimed at testing one specific part of your integration. Examples of unit tests include testing a connection to an individual endpoint on your backend system (e.g. testing the Access Point and File System Endpoint connected to your ERP), testing a connection to a trading partner, or testing a single map.
• Functional Tests: Functional tests string together multiple unit tests to test out as much of your integration as is possible without impacting trading partners or other external systems that would require coordination. Thus, functional tests are end-to-end integrations, but they simulate the connection to the partner so that it can be tested before reaching out to your partner. The goal is to ensure your integration is working well before bothering your trading partner and, when you do test with your trading partner, if something goes wrong, you can be pretty confident it's due to the connection with your trading partner and not some other part of your integration
• End-to-End Tests (with Partners): Once you have well functioning Functional Tests, you are ready to do the final step of testing the end-to-end integration with your Trading Partner. So, in this step, we replace the simulated partner endpoint with the real partner endpoint.

We will continue to build out tests in this section to assist you in your testing efforts. Expect more to come.