Now that you’ve set up some Events and Actions, the next step is to test your connector’s capabilities. Our connector development platform allows you to perform multiple layers of testing as you develop.
In general, testing while developing your connector happens in two ways:
The first way, testing a singular method, allows you to test the flow of data through your method, in a low-stakes, very transparent way. You control the data that is input into your connector’s method explicitly, and can therefore benefit from having total control over the cases your connector is tested against. This style of testing all occurs within our connector building environment itself, and is designed to be used frequently along your development cycle. For more information, see “Testing Your Methods”.
The second way, testing your entire connector, happens while building a FLO, and allows you to thoroughly test all of the functionality and visual elements of your connector in one place. Here, you can also test your connector’s interactivity with other connectors- allowing you to see how “usable” your Connector would feel to a user. This style of testing is meant to be robust, but should be used during the “polishing” stage of your testing workflow after many rounds of testing while developing, as this method requires that you must deploy to the FLO building environment with each update.