VOGO Voice shares a uniquely flexible and configurable platform that allows prototyping and publishing both Alexa and Google actions. The testing capability fixed within the interaction builder platform offers the option to test the functionality of a custom interaction model during its development or at any given time. Using this feature also helps to determine the performance of an interaction even in the absence of a voice-assisted device.
This user-centric guide delineates the anatomy of the Testing card that is integrated onto the interaction builder platform. To help you gain a thorough understanding of this feature, the comprehensive guide in a simplified manner focuses on the purpose and relevance of availing the test feature along with how to populate the fields on the Test window prior to testing any session of a specific custom skill.
Prerequisites
- VOGO Voice account: https://www.vogovoice.com/
- Access rights to the Interaction builder platform.
How to access the Test button
Navigate into any interaction within the Interactions section to access the Test button next to the Flow Editor button. Click on the Test button to proceed with the testing of your skill.
In the Tests pop-up window that appears click the + button on its top right-hand corner.
Assign a name for the test in the Name field of the Test Response window that shows up.
In the Conversation section of the Test Response, the intent invoked to execute the respective interaction flow while testing will be auto-generated in the User invokes field as shown above.
On clicking the plus button an additional field titled User Invokes appears wherein you can select a specific intent from the drop-down list that needs to be called to action within this interaction.
šNote: This field will not appear if an additional intent has not been invoked within the interaction during the execution of the flow.
Additional fields will appear with the title With Slots, where the slot names along with the space to assign the respective slot values will be displayed. The testing procedure is carried out based on the input slot values. The With Slots field is enabled only if you had previously assigned slot values while creating the intent to which the interaction is mapped, an example of which is as shown above. Thereās also a provision to add more custom intents along with adding its slot values by clicking the consecutive + button.
In the succeeding, optional field User Settings, dual fields are provided to add variables using the key-value structure to represent the specific data called through the instance of a connector or other components while building the custom interaction model for requirements such as processing, querying or requesting data. Since the request is not a real user you may need to mock up settings keys and values to test different use cases.
In the User Permissions section check the checkmark box of those permissionsĀ that corresponds to the permission requests implemented within the flow through the Request Permissions data component while building the custom interaction model. These permissions represent the ones for which the user has granted consent in regard to the skill that is to be tested. In the event of selecting Geolocation, optional fields will appear to add location data of the device in the form of latitudinal and longitudinal values.Ā
Within the Device Capabilities section, check the checkmark box of all the capability interfaces supported by the device in the event of performing a live test of your custom skill.
Finally, click the Save button to save the input and perform the test for your custom interaction model.
Running a test
- To validate the Test Response, click on the lightning symbol on the left-hand side of the test case.
2. On the resultant Test Response window, the blue chat bubble will cumulatively present the previously input messages within the Response component. Depending on the number of connector instances linked to the interaction flow, a corresponding number of lightning bolt symbols in yellow will appear in the Test Response as shown below.
3. Click on the chat bubble to see the details of the individual responses. To take a detailed look at the data fetching part of connector instances, click on the lightning bolt icon highlighted in yellow that represents the specific connector.
