Key Integration Tests

Integration tests are designed to help minimize the possibility of issues when integrating with the other system. They are especially invaluable when you run them integrated with the other system (stub set to false). However, you will often need to do work in order to do this to verify that the data being sent is valid and also the the tests are cleaning up after themselves. So most of the time integration tests are run in stub mode.

Some of the Key Integration Tests include:

• Connect Test: This will check if the connect method is successful with no healthcheck and with healthcheck on startup.
• HealthcheckTest: This will check if the healthcheck method is successful. This also includes checking authentication to the other system when running integrated.
• Specific Tests: These tests are created for every method in the adapter. Running these tests integrated with the other system is a good way to make sure all the calls are working. However, you should never run integration tests to the other system in a production environment!

Example: Integration Test

describe('#connect', () => {
  it('should get connected - no healthcheck', (done) => {
  it('should get connected - startup healthcheck', (done) => {

describe('#healthCheck', () => {
  it('should be healthy', (done) => {

There are many more integration tests, some are generic for all adapters and others have been added to check that specific calls that were built for the adapter are returning properly.