IVR Test Case Generator Using Audio and DTMF Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for testing interactive voice response (IVR) systems are inefficient and costly due to reliance on manual testing, which covers less than ten percent of possible scenarios and is prone to errors, and existing automated systems require extensive programming knowledge.

Innovation Solution

A system and method for automatically generating IVR test scenarios using an IVR test case generator that processes audio streams, dual-tone multi-frequency signals, and metadata to create test cases without the need for programming knowledge, employing machine learning algorithms to generate synthetic audio streams and utilize every dual-tone multi-frequency signal combination.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual testing is used, then ease of operation is improved, but productivity deteriorates and only less than ten percent of scenarios are tested

Engineering Contradiction:
Improveease of operationVSAvoidproductivity
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system enables self-service by allowing the IVR system to test itself automatically. The test case generator captures audio streams, DTMF signals, and metadata from actual user interactions with the IVR system, then automatically generates test cases without requiring manual programming or intervention. This eliminates the need for human testers to manually execute each test scenario while maintaining comprehensive coverage of all possible pathways.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual testing process with an automated computational system. Instead of human operators manually dialing numbers, recording responses, and creating test cases, the system uses audio processing algorithms, speech recognition, and automated script generation to perform all testing functions, thereby dramatically increasing productivity and test coverage.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of operation

If manual testing is used, then ease of operation is improved, but loss of time deteriorates and testing is untimely

Engineering Contradiction:
Improveease of operationVSAvoidloss of time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary action by continuously capturing and storing audio streams, DTMF signals, and metadata from actual IVR interactions in advance. These captured data are then used to automatically generate test cases without requiring time-consuming manual analysis, enabling rapid test case creation that is timely and responsive to system changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The automated system replaces time-consuming manual testing operations with computational processes that instantly analyze captured data and generate test cases. This substitution eliminates the time loss associated with manual recording, analysis, and test case creation, allowing for timely testing that keeps pace with rapid IVR system changes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If automated testing systems are used, then productivity is improved, but device complexity deteriorates due to extensive programming knowledge requirements

Engineering Contradiction:
ImproveproductivityVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system eliminates the complexity barrier by making the automated testing system self-configuring and self-executing. It automatically captures interaction data, processes audio and DTMF signals, generates appropriate test cases, and executes them without requiring users to program or configure complex testing scripts. The system serves itself by adapting to different IVR systems without manual intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary layer in the form of an automated data processing and test case generation system. This intermediary captures raw interaction data, translates it into structured test cases through automated algorithms, and prepares execution scripts, thereby shielding users from the underlying complexity while maintaining high productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If manual testing is used, then ease of operation is improved, but reliability deteriorates due to human errors in reporting

Engineering Contradiction:
Improveease of operationVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system replaces human operators with automated computational processes that objectively capture, analyze, and report test results. Audio streams and DTMF signals are processed algorithmically, and test outcomes are recorded without human intervention, eliminating reporting errors and ensuring consistent, reliable test documentation that accurately reflects system behavior.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system implements feedback mechanisms where actual IVR interactions are captured and analyzed to automatically generate and validate test cases. The captured audio and signal data provide feedback that ensures test cases accurately represent real user experiences, improving reliability by grounding tests in actual system behavior rather than manual interpretation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11790886B2System and method for synthesizing automated test cases from natural interactions
Publication Date: 2023.10.17 CYARA SOLUTIONS PTY LTD
  • US11790886B2 patent drawing
  • US11790886B2 patent drawing
  • US11790886B2 patent drawing

AI summary

A system for synthesizing real IVR scenarios, automatically reproducing test scenarios, and providing accurate reports on those scenarios. An IVR tester uses a telephony device (website, mobile app, VOIP, etc.) and an automated IVR test case generator to place test calls to an IVR system. The automated IVR test case generator intercepts and collects the phone call's audio stream, dual-tone multi-frequency signals, and available metadata (e.g., response times, post-speech silence timeout, etc.). Once the call is complete, the automated IVR test case generator pre-populates a webpage or other user-interface technology and a database with the audio stream, dual-tone multi-frequency signals, and available metadata from the test scenario phone call. The IVR tester may then save that test scenario and continue to the next scenario. The saved scenario may now be used automatically by the IVR test case generator for regression testing or duplicated and edited for use in other systems.