Validating a Test Case

After you create a Test Case, the Test Case must be validated to ensure it runs successfully under normal conditions. If the results are unsatisfactory, make modifications to the test script until a satisfactory result is obtained. You must validate Test Cases before applying them to a Campaign.

The Cyara Test Case Validation process places an actual call into the IVR in real time as per the details specified in the Test Case and allows you to listen to the recorded result upon completion. This process ensures that the test is behaving as designed and that the Test Case itself is not at fault (for example, it may have incorrect Step sequence/s, incorrect responses or expected delays, and so on).

To validate the Test Case, click Save & Run at the bottom of the Create Test Case screen.
This triggers the validation process. Step-by-Step validation progress is displayed on the test result screen. The current Step being validated is highlighted and after the validation is complete, the indicator moves to the next Step. The Step-by-Step validation result is displayed for all completed Steps and for the test result details above the Steps.

The Step-by-Step validation complete screen is as shown:
Click the Back button in your browser or the Test Case Name to return to the Edit Test Case screen to make any required changes to the test case.

Note: You can abort the validation while it is running. The validation is aborted after the current Step validation is complete.
Click the Last Validated date and time link in the Edit Test Case screen to view the historical validations of the Test Case. Historical validation reports are available for all past validations. The validation history shows the status of a validation run as well as the validation date and duration.Click a specific date to view detailed results.
You can also view the historical validation reports for a test from the Test Cases & Blocks screen. Navigate to the test case and click to view the list of validations for that test case.
To re-run a validation, select Action > Validate Test Case.

Analyzing Speech Recognition Results

You can listen to call recordings to analyze the speech recognition results and identify issues, if any. The audio inspector has two separate channels. The upper channel for the Expect to Hear audio and the lower channel for the Reply With audio. This makes it easier to identify specific noises while performing analysis.

The audio tracks have step markers to indicate the beginning and end of a step. MultiStep prompt with contiguous steps of PSST = 0 is shown as a single step in the audio inspector. In the following illustration, steps 2 and 3 are combined together as step 2 and 3 have PSST of 0 and step 3 has an Expect to Hear prompt. Similarly, steps 5 and 6 are combined together.

For more information about MultiStep prompt, see Multi-Step Prompt.

Note: Call recordings recorded in Platform release versions earlier than 21.5 are presented only in single channel mode as before. Step markers are not displayed on the audio tracks.

To listen to the entire test recording, click the Play button on the embedded applet at the top of the Test Case Validation screen. You can also use the controls to go to the beginning or the end of the recording.
Click and drag the handle along the audio track to zoom and listen to a specific part of the call. Click Zoom Selection and set the zoom percentage. Click Reset Zoom to zoom out of the selection.
Hold the pointer over a step marker to view the results of that particular step in a pop-up.
Click to download the full recording WAV file.
Click in the Detailed Result column of a step to play the step recording directly in your web browser. This allows you to hear the recording of a Step directly rather than hearing the recording of the entire Test Case. You can also download a WAV file of the step recording.

Note: Audio inspector for step recordings are available only in single channel mode and contains the Expect to Hear audio.
Click to analyze the speech recognition result of a particular prompt in detail using the Prompt Analyzer .