Find the answer you are looking for

Best practices for testing technical integrations

To test technical integrations effectively, it is recommended to follow these steps:

1. Please note that you are testing in a DEV/STAGE environment, which is unstable compared to the productive environment, so we suggest that you open the chat in an incognito window to avoid cache problems and also that you do not run all tests from the same session, or delete cookies between each test flow.

undefined


2. Open the chat window and type each intent that activates or triggers the flow to be tested. The message "Powered by Froala Editor" is only visible in the test environment and will not appear in the production integration.

3. Uses the test data provided in the analysis instance, to ensure that validations are consistent with the shared casuistry. 

4. Keep in mind that this demo version only contains information related to the integrations, the content uploaded there is not your entire knowledge base, but the necessary circuitry to achieve effective testing and ensure that the integration works correctly before implementation, so if you use data from the production environment you may generate inconsistent answers.

5. Verify that each flow behaves as indicated in the documentation and diagrams. Also make sure to validate the messages and texts in each case.

6. After performing all the verifications, we suggest that you share a consolidated document with the observations you have on the tests performed, to your OB/CSM. Include screenshots, GIFs or videos of what you need to report and the corresponding flow, to speed up the adjustment stage and avoid loss of information. In case of requesting any text modification, please detail which one you wish to make the change for.

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.