Testing is an essential part of Connector building. Let’s have a quick introduction to how you should approach it in Cyclr.
Initial Testing
The API calls you make whilst building and testing your Connector within Cyclr will count towards your usage. This is why it’s good practice to test your methods and endpoints before you begin accessing the API via Cyclr.
When making a Connector, always check the following:
- Does the documentation give accurate information?
- Does the documentation give enough information?
- Can we verify that the user credentials work?
- Are there any issues we should be aware of before moving into the Cyclr environment?
If you are unable to make your method requests, ask yourself these questions:
- Do I have all the info needed?
- Can I make a successful API call?
If the answer to either question is no, you will need to consider what is missing and how to obtain it.
Testing in Cyclr
Once you have imported your methods into your Connector in Cyclr, you need to test them in the Cyclr environment.
There are two ways to test your methods in Cyclr, and doing both when building connectors is advised. One way is testing the methods in the Connector settings, and the second way is building a simple cycle with your Connector methods to ensure they work together as intended.
We will go into the ways of testing methods further in the Methods section of this tutorial.
Top Tip! Set up an Account for Testing
You will need to set up an Account to be able to test your Connector effectively. It’s advised to use a non-customer-facing account for this, as you may need to install and uninstall your Connector several times while it is in the testing phase.
If you have not set up an account yet, please refer to the Account Management section of our “Introduction to the Cyclr Console” Tutorial.