Description
Systematically drive a live voice system through every dialog state, universal command and error condition to verify it matches the dialog specification.
In voice design a dialog is one state in the conversational flow, usually a question and the user's reply, with all its transitions, error prompts and help prompts. Dialog traversal testing runs a script against the live system (over the phone for IVRs) that visits every state and checks that the correct action is taken and the correct prompt played. Within each state every universal command (help, repeat, go back, goodbye) and every error condition is exercised: out-of-grammar speech to trigger a reject, silence to trigger the no-speech timeout, and several successive errors to check escalation. Testers annotate a printed flow diagram as they go. Coverage is adapted to the system: every state for deep fixed trees, every function reachable from the top-level prompt for wide assistants, and best paths plus common error paths when full traversal is too costly.
Attributes
- Discipline
- Usability & Evaluation
- Loss type
- Siloed
- Stage
- Evaluation
- Data
- Analytical / expert
- Effort
- Days
Steps
- Take the dialog specification and flow diagram as the oracle.
- Write a test script that visits every dialog state.
- At each state, check the action taken and the prompt played against the specification.
- Exercise every universal command (help, repeat, back, goodbye) in each state.
- Trigger each error condition: out-of-grammar input, silence, and successive errors to test escalation prompts.
- Mark results on the printed flow diagram and log every divergence.
- For broad assistants confirm every function is reachable from the top level; for very large systems prioritise best paths and common error paths.
Sources
- Designing Voice User Interfaces (Pearl, 2017)
Also known as
- DTT
- Dialog traversal test
- Dialogue traversal testing
Categories
- User Research
- Usability & Evaluation