Workflow for Testing Integrations
You can test integrations in your development environment or in a higher environment, such as testing or production. When testing, check the integrations for errors and ensure that they run as expected. You should understand the goals and business logic of an integration so that you can identify issues quickly.
If you need to deploy to a higher environment before testing, see Workflow for Deploying Automation Solutions.
Step | Task | More information |
---|---|---|
1 |
Activate the project or the integrations in the project |
You have several options:
Note: When you activate an integration, you choose the level of tracing information to log to the activity stream. Consider the following factors when choosing a tracing level:
|
2 |
Run the integration |
To run an integration, invoke the endpoint URL for
the integration. You have several options for invoking an
endpoint URL:
|
3 |
Check the activity stream for errors |
Verify that the instance of the integration is finished. See Monitor Integrations in a Project. Next, verify that the integration finished running, and check the activity stream for errors. The activity stream depicts the message flow in the integration instance and indicates where errors occurred, if any. The activity stream contains all the information that you need to troubleshoot problems with your integrations. To learn more, see Learn About the Payloads in the Activity Stream. You can open the activity stream from several pages:
|
4 |
If an error occurred when the integration ran, address it and take the appropriate next steps |
When the activity stream contains one or more errors, the integration isn't running as expected.
|
5 |
Verify that the integration works as expected |
For example:
|