Help Center

Best practices for testing technical integrations

When implementing technical integrations it is a good practice to test them taking the following precautions: 

The DEV/STAGE environment may suffer instabilities, so it is important that you can test desirably from an incognito window to avoid any cache related issues. We also suggest not to do all tests from the same session/window or to delete cookies between flows from here:


Open the chat window and put intent by intent to test each flow. Clarification: the "Powered by Froala Editor" message is part of the test environment, you will not see this information in the integration when it is in production;

Initially use the test data shared in the analysis instance, as this will ensure that the validations are true to the shared case studies. If data from the production environment is used, it may not be properly updated in the test environment and lead to inconsistencies in the information. 

You should check that the behavior of each flow is as expected - as submitted in the diagrams in the documentation - and also remember to validate the messages / texts in each case;

Once all the checks are done, we suggest sharing with your OB/CSM a unified document with all the observations resulting from your tests, in order to make the adjustment step more efficient and agile and to avoid any information being misplaced. It is important to include in this document:

  1. Captures, gif or video of the reported point;
  2. Flow to which it corresponds;
  3. In case you request any text modification, make a "from/to" for correct understanding of the modification to be made.

Important: in this demo version the rest of your bot's content is not loaded, but they will only find what is related to the integrations in question, so you should limit the testing of the flows with the intentions shared by your OB / CSM for the test instance.

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.