Skip to main content

Managing Test Cases

A test case is one scripted conversation that an Application Test plays against your voice application. Each test case has a name, an optional description, and an ordered list of steps that alternate between what the application should say (match) and what the caller should do in response. Test cases live on the Test cases tab of an Application Test.

Accessing Test Cases​

  1. Navigate to the Monitoring module.

  2. Open the Application Tests page and click the test you want to work with.

  3. Select the Test cases tab.

    Test cases tab on an Application Test

The table lists every test case on the test, with its Name and Description. Use the row actions to edit, copy, export, or delete a test case.

Creating a Test Case​

  1. Click the New test case dropdown in the top-right of the tab and pick one of:

    • Configure manually — build the test case step by step in the editor.
    • Configure via live call — place a real call to your application. Cloverhound Cloud records what the application says and what you press or say, then pre-fills the editor from that call.

    New test case dropdown

  2. Fill out the test case details at the top of the editor:

    • Name — required. Shown in the test cases table and in run results.
    • Description — optional free-text note about what this case covers.

  3. Define the steps (see Editing Steps below).

  4. Click Create Application test case to save.

Copying, Exporting, and Deleting​

The row actions on the test cases table let you reuse and clean up cases.

Test case row actions

  1. Click Edit to open the test case in the editor and change its name, description, or steps.
  2. Click Copy to duplicate the test case. The new case opens in the editor pre-filled with the original's steps and a name like <original> (Copy). Save to add it to the test.
  3. Click Export to download the test case as a JSON file named Test_case_<name>.json. Use this to back up a case or move it to another Application Test.
  4. Click Delete to remove the test case.
warning

Deleting a test case is immediate and cannot be undone. Past run results for the case remain in the test's history, but the case no longer runs on future executions.

Editing Steps​

Each step represents one turn in the conversation. Steps run in the order shown.

Test case step editor

For each step, set:

  • Match — what the application is expected to say or play.

    • Match type:
      • Transcript — the step matches when the application's audio transcribes to the text you enter. The text area is required.
      • Any — the step matches anything the application says. Useful for ignoring a prompt you don't care about. The last step cannot be Any, and two consecutive steps cannot both be Any.
    • Language — the language used to transcribe the application's audio for this step.

  • Response — what the test should send back after the match succeeds. Hidden when Match type is Any.

    • Type:
      • DTMF — the response is a sequence of keypad digits (for example, 1 or 1234#).
      • Voice — the response is spoken text synthesized to audio.
    • Language — shown only when Type is Voice. Sets the voice used to speak the response.

Adding Steps​

  • Click + Add step at the end of the list to append a step.
  • Hover between two steps and click the round + button to insert a step at that position.

Reordering Steps​

Drag a step by the handle on the left of its header to move it up or down. Steps are renumbered automatically.

Drag handle for reordering steps

Deleting a step​

Hover over the step and click Delete next to the step number.

warning

Step validation runs as you type. If a step shows an error (for example, a blank Match on a Transcript step, or Any in an invalid position), fix the error before saving. The form refuses to save a test case with step errors.

With test cases in place, the Application Test runs each one on schedule and reports a pass or fail for every case. To change when the test runs, see the Test schedules tab on the parent Application Test.