Method and system for VoiceXML quality assurance.

• US 20110145641A1
• Filed: 12/11/2009
• Published: 06/16/2011
• Est. Priority Date: 12/11/2009
• Status: Abandoned Application

• Current Assignee: Daniel D. Evans
• Original Assignee: Daniel D. Evans
• Inventors: Evans, Daniel D
• Application Number:
  US12/635,963
• Publication Number:
  US 20110145641A1
• Time in Patent Office: Days
• US Class Current: 714/27
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A software quality assurance tool (“IVRT”) for VoiceXML applications is described. IVRT makes speech and telephony irrelevant to the testing of VoiceXML logic. IVRT follows a machine-readable “Test Plan” to execute the logic of an application. The Plan provides the results of telephony interactions. Testing is done without live callers, and runs at computer speed. A Plan contains any number of calls, to guide the application execution through all logic paths. The tool executes the application in a live environment with respect to all non-telephony functions, particularly web interactions, to test the application'"'"'s web logic. IVRT executes multiple threads, acting as simultaneous callers, to provide controlled load web logic testing. The tool summarizes Plan “coverage”. For regression testing, IVRT tests an updated application with its original Test Plan and compares the log to previous logged output. Differences indicate potential regression failures.

Claims

1. A method for quality assurance testing of one or more simultaneous instances of a VoiceXML application in super-real-time by obtaining the telephony interactions expected by the application from a test plan, eliminating the need for speech input or output during execution, and providing a speed improvement over normal real-time testing.

2. A method of claim 1 whereby the execution of the VoiceXML application is controlled by a Test Plan, a series of directives which provide information for simulated telephony interactions and speech responses, encompassing any number of simulated telephone calls, allowing each call to provide differing interactions and thus test different aspects of the application.

3. A method of claim 2 wherein in Test Plan directives provide for grammar triggers, interpretations, and multiple results, eliminating the need for speech to test VoiceXML application logic.

4. A method of claim 2 wherein Test Plan directives can also provide assertions about the expected behavior of the application, checks that specific logical conditions are true at specific points in a test.

5. A method of claim 2 wherein Test Plan directives can also provide metadata applicable to all calls.

6. A method of claim 2 whereby the Test Plan syntax reflects the syntax used within VoiceXML (ECMAScript) and is therefore familiar to VoiceXML developers.

7. A method of claim 1 wherein all actions of the VoiceXML application during the execution are logged to become input to subsequent regression testing.

8. A method of claim 1 wherein all executed logic paths of the application during the execution are recorded to provide a Quality Assurance measure known as “

Coverage”

, the effectiveness of a test as measured by the percentage of logic paths executed.

9. A method for comparing the logged output of separate Test Plan executions so that the irrelevant differences, such as time stamps, are ignored, and the relevant aspects of the logging are compared to provide support for Quality Assurance regression testing. Log differences and their points of occurrence are highlighted.