Voice interaction application test method and device and related equipment

By retrieving and deserializing voice type events from preset files, the voice interaction application is driven to execute these events, solving the problem of automated testing for applications without an operating interface, ensuring the normal operation of voice interaction applications in the vehicle system and detecting anomalies.

CN121051003APending Publication Date: 2025-12-02BEIJING CO WHEELS TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410674875.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-05-28
Publication Date
2025-12-02

AI Technical Summary

Technical Problem

Existing technologies cannot perform automated simulation testing of voice interaction applications without a user interface, resulting in the inability of voice interaction applications in vehicle systems to function properly.

Method used

By obtaining the target file stream from a preset file, deserializing it to generate various voice event types, and distributing them to the voice interaction application, the application is driven to execute these events to obtain test results, thus avoiding contact with the user interface.

Benefits of technology

It enables automated testing of voice interaction applications that cannot be touched, ensuring that voice interaction applications in the vehicle system can operate normally, saving testing manpower and discovering potential anomalies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121051003A_ABST
    Figure CN121051003A_ABST
Patent Text Reader

Abstract

The invention discloses a voice interaction application testing method and device and related equipment. The method comprises the steps of obtaining a target file stream from a preset file, wherein the preset file comprises a file stream generated after a normal voice interaction event stream of a voice interaction application is serialized; deserializing the target file stream to generate various voice type events; distributing the various voice type events to a voice interaction application; and driving the voice interaction application to execute the various voice type events to obtain a test result of the voice interaction application. According to the embodiment of the invention, the method does not involve the contact of an operation interface, is suitable for the test of a non-touchable voice interaction application, and guarantees the normal operation of the voice interaction application in the vehicle-mounted terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of vehicle technology, and in particular relates to a testing method, apparatus and related equipment for voice interaction applications. Background Technology

[0002] With the continuous development of science and technology, vehicles have brought great convenience to people's lives and travel. In particular, voice interaction applications in in-vehicle systems can control various vehicle functions in response to voice commands from drivers and passengers. To ensure the proper functioning of voice interaction applications in in-vehicle systems, testing is necessary. However, current testing methods for voice interaction applications are mostly based on touch-screen applications with user interfaces, and are not suitable for non-touchscreen voice interaction applications, making automated simulation testing of such non-interactive applications impossible. Summary of the Invention

[0003] This application provides a testing method, apparatus, and related equipment for voice interaction applications, which can test non-touchable voice interaction applications without involving contact with the user interface, thereby ensuring that voice interaction applications in vehicle systems can operate normally.

[0004] In a first aspect, embodiments of this application provide a testing method for a voice interaction application, the method comprising:

[0005] Obtain the target file stream from a preset file, which includes a file stream generated after serializing the normal voice interaction event stream of the voice interaction application;

[0006] The target file stream is deserialized to generate various voice event types;

[0007] Distribute the various voice type events to voice interaction applications;

[0008] The voice interaction application is driven to execute the various voice type events, and the test results of the voice interaction application are obtained.

[0009] Secondly, embodiments of this application provide a testing device for a voice interaction application, the device comprising:

[0010] The first acquisition module is used to acquire a target file stream from a preset file, wherein the preset file includes a file stream generated after serialization of a normal voice interaction event stream of a voice interaction application;

[0011] The generation module is used to deserialize the target file stream and generate various voice event types;

[0012] The distribution module is used to distribute the various voice type events to voice interaction applications;

[0013] The driver module is used to drive the voice interaction application to execute the various voice type events and obtain the test results of the voice interaction application.

[0014] Thirdly, embodiments of this application provide an electronic device, the electronic device comprising: a processor and a memory storing computer program instructions; the processor executing the computer program instructions implements a test method for the voice interaction application described above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the test method for the voice interaction application described above.

[0016] Fifthly, embodiments of this application provide a computer program product, wherein instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform a test method for a voice interaction application as described in any of the above claims.

[0017] In a sixth aspect, embodiments of this application provide a vehicle comprising at least one of the following: a testing apparatus for a voice interaction application as described above; an electronic device as described above; a computer-readable storage medium as described above; and a computer program product as described above.

[0018] The testing method, apparatus, and related equipment for voice interaction applications in this application embodiment can obtain a target file stream from a preset file, which includes a file stream generated after serializing the normal voice interaction event stream of the voice interaction application; deserialize the target file stream to generate multiple voice type events; distribute the multiple voice type events to the voice interaction application; drive the voice interaction application to execute the multiple voice type events, and obtain the test results of the voice interaction application. Thus, in this application embodiment, multiple voice type events can be distributed to the voice interaction application, i.e., simulating the automatic distribution of multiple voice type events to drive the voice interaction application to execute each voice type event, thereby obtaining the test results of the voice interaction application. This does not involve contact with the user interface and is applicable to the testing of touchless voice interaction applications, thereby ensuring that the voice interaction application in the vehicle system can operate normally. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1This is a flowchart illustrating the testing method for a voice interaction application provided in an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of the structure of the test device for the voice interaction application provided in the embodiments of this application;

[0022] Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0023] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0024] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0025] With the continuous development of science and technology, vehicles have brought great convenience to people's lives and travel. In particular, voice interaction applications in in-vehicle systems can control various vehicle functions in response to voice commands from drivers and passengers. To ensure the proper functioning of voice interaction applications in in-vehicle systems, testing is necessary. However, most voice interaction applications currently on the market are touch-based with user interfaces, which are not suitable for non-touch-based voice interaction applications, making automated simulation testing of such applications impossible.

[0026] To address the problems of the prior art, embodiments of this application provide a testing method, apparatus, and related equipment for voice interaction applications. The testing method for voice interaction applications provided in this application embodiment will be described first below.

[0027] Figure 1 A flowchart illustrating a testing method for a voice interaction application provided in one embodiment of this application is shown. Figure 1 As shown, a testing method for a voice interaction application may include the following steps S101 to S104:

[0028] S101. Obtain the target file stream from the preset file, which includes the file stream generated after serializing the normal voice interaction event stream of the voice interaction application;

[0029] S102. Deserialize the target file stream to generate various voice event types;

[0030] S103. Distribute various voice event types to voice interaction applications;

[0031] S104. Drive the voice interaction application to execute various voice type events and obtain the test results of the voice interaction application.

[0032] The testing method for voice interaction applications in this application embodiment can obtain a target file stream from a preset file, which includes a file stream generated after serializing the normal voice interaction event stream of the voice interaction application; deserialize the target file stream to generate multiple voice type events; distribute the multiple voice type events to the voice interaction application; drive the voice interaction application to execute the multiple voice type events, and obtain the test results of the voice interaction application. Thus, in this application embodiment, multiple voice type events can be distributed to the voice interaction application, that is, the automatic distribution of multiple voice type events can be simulated to drive the voice interaction application to execute each voice type event, thereby obtaining the test results of the voice interaction application. This does not involve contact with the user interface and is applicable to the testing of touchless voice interaction applications, thereby ensuring that the voice interaction application in the vehicle system can operate normally.

[0033] The specific implementation methods for each of the above steps are described below.

[0034] The testing methods for the aforementioned voice interaction applications are primarily applied to event controllers in terminal devices with data processing capabilities. An event controller is a component in the software architecture used to manage events; it is responsible for processing and coordinating the event flow within the system.

[0035] The aforementioned voice interaction application is installed in the aforementioned terminal device and enables voice interaction between the user and the terminal device. The voice interaction application can activate its function by speaking a preset wake-up word, recognize and understand the user's voice commands, including natural language and specific commands, and then respond to the user's voice commands to perform events such as making phone calls, sending text messages, playing music, adjusting volume, setting navigation, and controlling the in-vehicle climate.

[0036] In step S101, the aforementioned preset file is generated by acquiring the normal voice interaction event stream of a voice interaction application, serializing the normal voice interaction event stream according to a preset sequence to obtain a file stream, and finally writing the file stream to the disk for storage. The preset file may include the file stream generated after serializing the normal voice interaction event stream of the voice interaction application.

[0037] The serialization process described above is the process of converting the state information of an object into a form that can be stored or transmitted.

[0038] The file streams mentioned above, typically associated with file operations, refer to the data stream generated during file read and write operations. In programming, a file stream is an abstract concept that allows a program to process data in a file in a continuous manner, as if it were a data stream. The concept of file streams is implemented in various programming languages, including but not limited to C / C++, Java, and Python.

[0039] The aforementioned event stream typically refers to a collection of events occurring within a certain time sequence. In this embodiment, the event stream can be generated through a voice engine during normal voice interaction.

[0040] The above-mentioned method of obtaining the target file stream from a preset file can, for example, be reading the target file stream from a preset file stored on a disk.

[0041] In S102, the above deserialization is the reverse process of serialization, which involves converting a sequence of bytes back into the original data structure or object.

[0042] The aforementioned various voice event types may include useless voice events, wake-up voice events, and command voice events. In this embodiment, the various voice event types are not limited to these and may also include other voice event types, which are not specifically limited here.

[0043] The above-mentioned process of deserializing the target file stream to generate multiple voice event types can be exemplified by deserializing the target file stream to obtain at least one voice event; classifying the at least one voice event to construct multiple voice event types, which include useless voice event types, wake-up voice event types, and command voice event types.

[0044] In S103, the above-mentioned distribution of multiple voice type events to the voice interaction application can, for example, be distributed to the voice interaction application according to the distribution order indicated by a preset distribution strategy. Different distribution strategies indicate different distribution orders for the multiple voice type events, such as sequential distribution or random distribution.

[0045] In S104, the above test results can be used to characterize whether the voice interaction application operates normally under the drive of various voice type events.

[0046] The above-mentioned method of driving the voice interaction application to execute multiple voice type events and obtain test results for the voice interaction application can, for example, be driving the voice interaction application to execute multiple voice type events in a preset order or in a random order to obtain test results for the voice interaction application.

[0047] In some embodiments, the above-described S102 may specifically include:

[0048] The target file stream is deserialized to obtain at least one voice event;

[0049] At least one voice event is classified to construct multiple voice event types, which include at least one of useless voice events, wake-up voice events, and command voice events.

[0050] The voice events of at least one of the above are events in the normal voice interaction event stream.

[0051] The aforementioned useless voice type events refer to events in a voice recognition system that are incorrectly identified as valid voice input when they are actually meaningless or unintentional. This may be due to background noise, false triggers, or other non-voice sounds. For example, in a noisy in-vehicle environment, the voice recognition system may incorrectly identify the user's conversation or noise as a voice command.

[0052] The aforementioned wake-up voice event refers to a user uttering a specific wake-up word or phrase to activate the vehicle's voice interaction application. Once the system is woken up, it will be ready to receive and process the user's voice commands.

[0053] The aforementioned command-based voice events refer to specific commands or requests issued by the user after the voice recognition system is activated. These commands can be instructions to perform specific operations, such as turning on car lights / windows, playing music, setting an alarm, or checking the weather.

[0054] In this embodiment, at least one voice event is obtained by deserializing the target file stream and classifying the at least one voice event to construct multiple voice event types. The multiple voice event types include at least one of useless voice event types, wake-up voice event types, and command voice event types. This makes it easy to retrieve and test each voice event type when driving voice interaction applications.

[0055] As one implementation of this application, in order to obtain the file stream in the preset file, before S101 above, the method may further include:

[0056] Obtain the normal voice interaction event stream of the voice interaction application;

[0057] The normal voice interaction event stream is serialized according to a preset sequence to obtain a file stream.

[0058] The above-mentioned acquisition of normal voice interaction event streams of voice interaction applications, for example, can be achieved by using a voice engine to form normal voice interaction event streams from the voice signals of normal voice interaction.

[0059] The aforementioned preset sequences, i.e., predefined serialization formats, can, for example, include text serialization, binary serialization, and custom serialization (serialization based on timestamp order). Text serialization converts data into text formats such as JSON and XML, which are easy to read and edit and are commonly used for data exchange. Binary serialization converts data into binary format, which is generally more compact and has higher transmission efficiency than text serialization. Custom serialization allows for the creation of custom serialization rules based on the needs of specific applications to optimize performance or meet specific data structure requirements.

[0060] In this embodiment, the normal voice interaction event stream of the voice interaction application is obtained and serialized according to a preset sequence to obtain a file stream. In this way, the preset file can be used for testing the voice interaction applications of multiple vehicle systems, and the preset file can also be changed according to different user testing needs to meet different user testing needs for the voice interaction application.

[0061] In some embodiments, the above-described S103 may specifically include:

[0062] According to the preset distribution strategy, various voice event types are distributed to the voice interaction application in the order indicated by the distribution.

[0063] The above distribution strategy is used to indicate the distribution order of various voice event types, such as sequential distribution, reverse distribution, or random distribution. In this embodiment, it is not limited to this and can be set according to the actual needs of the user. No specific limitation is made here.

[0064] In this embodiment, since users can distribute various voice type events to the voice interaction application in any order in a real-world scenario, distributing multiple voice type events to the voice interaction application according to the distribution order indicated by the preset distribution strategy can realistically simulate the scenario of users sending events to the voice interaction application, thereby detecting anomalies in the voice interaction application.

[0065] As another implementation of this application, in order to fully expose anomalies existing in the testing of the voice interaction application, before distributing multiple voice type events to the voice interaction application according to the distribution order indicated by the preset distribution strategy, the above method may further include:

[0066] The system receives drive signals from the event driver. These drive signals include target policy parameters. Different policy parameters correspond to different distribution policies, and the distribution policies indicate the distribution order of various voice event types.

[0067] Among the multiple preset distribution strategies, the distribution strategy corresponding to the target strategy parameter is determined as the target distribution strategy;

[0068] The above-mentioned distribution of various voice type events to voice interaction applications according to the distribution order indicated by the preset distribution strategy may specifically include:

[0069] Distribute various voice type events to voice interaction applications according to the distribution order indicated by the target distribution strategy.

[0070] The aforementioned driving signals can be used to trigger the event controller to distribute various voice-type events to the voice interaction application in the order indicated by the target distribution strategy. For example, the driving signal can be any form of signal or data indicating that a specific behavior or state change has occurred.

[0071] The aforementioned event driver typically refers to the source of the triggering drive signal, which can be a hardware device, operating system signal, network request, timer, sensor reading, user interface operation, etc.

[0072] The aforementioned strategy parameters, for example, can be strings of letters, numbers, and combinations thereof, used to uniquely identify the distribution strategy. Different strategy parameters correspond to different distribution strategies, and different distribution strategies indicate different distribution orders for various voice type events. The aforementioned target strategy parameters can be parameters set by the user according to actual testing needs.

[0073] In this embodiment, the target distribution strategy is determined by the target strategy parameter in the driving signal, and various voice type events are distributed to the voice interaction application according to the distribution order indicated by the target distribution strategy. This enables the voice interaction application to be tested in different distribution orders, which helps to fully expose the anomalies that exist in the testing of the voice interaction application.

[0074] In some embodiments, the above-described S104 may specifically include:

[0075] The system drives a voice interaction application to execute various voice-type events in a preset or random order, and obtains the test results of the voice interaction application.

[0076] In some embodiments, the order in which the voice interaction application executes multiple voice type events can be the same as the order in which multiple voice type events are distributed to the voice interaction application.

[0077] The test results of the above-mentioned voice interaction application can be obtained by evaluating multiple execution results after executing multiple voice type events. The test results can be used to characterize whether all multiple execution results are normal, or to indicate the corresponding voice type event when at least one execution result is abnormal.

[0078] In this embodiment, by driving the voice interaction application to execute various voice event types in a preset or random order, the test results of the voice interaction application can be obtained, ensuring that the application can correctly handle various types of voice events and achieving a comprehensive evaluation of the quality and performance of the voice interaction application.

[0079] To facilitate understanding of the testing method for the voice interaction application in the embodiments of this application, the application process of the testing method for the voice interaction application is described below:

[0080] In this embodiment, the main approach is to record event streams generated by normal user behavior, and then drive the application to run by randomly replaying or re-randomizing these event streams, thereby conducting functional tests and identifying problems.

[0081] (1) Normal voice interaction forms an event stream through the voice engine (i.e., the normal voice interaction event stream mentioned above). The event stream is serialized into a file stream (equivalent to the target file stream mentioned above) according to a fixed sequence. The file stream is written to the disk and stored to form a file (i.e., the preset file mentioned above). (Serialization is the process of converting the state information of an object into a form that can be stored or transmitted.)

[0082] (2) Read the file; deserialize the read file stream to form a voice event, which is the event recorded in step (1); the various voice event types formed are handed over to the event controller for management and control, and the events are managed and scheduled by the controller in the form of a queue (deserialization is the reverse process of serialization, which involves converting the byte sequence back to the original data structure or object).

[0083] (3) Enable the event driver to trigger the event controller to dispatch events.

[0084] (4) When the event controller receives the drive signal, it selects events from the event stream and distributes them according to the parameters carried in the drive signal (i.e. the target strategy parameters mentioned above). It can execute voice events in the controller sequentially or execute voice events in the controller randomly.

[0085] (5) Distribute the event-driven application (i.e. the above-mentioned voice interaction application) to run. After the application is simulated by the exhaustive simulation of events in the Hong paradigm, the problems of the application are fully exposed (the application here is a voice interaction type application. The application runs by event flow. Countless time streams can fully simulate the user's voice interaction behavior, and then discover the problems in the process of running the application).

[0086] This application embodiment is based on automatically recording events in normal usage scenarios. By replaying the recorded events, the application is triggered to perform testing, automatically discovering any abnormal issues and significantly saving testing manpower.

[0087] Based on the testing method for voice interaction applications provided in the above embodiments, this application also provides specific implementations of a testing device for voice interaction applications. Please refer to the following embodiments.

[0088] like Figure 2 As shown in the embodiment of this application, a test device 200 for a voice interaction application may include the following modules: a first acquisition module 201, a generation module 202, a distribution module 203, and a driver module 204.

[0089] The first acquisition module 201 is used to acquire a target file stream from a preset file, the preset file including a file stream generated after serialization of the normal voice interaction event stream of the voice interaction application;

[0090] The generation module 202 is used to deserialize the target file stream and generate various voice event types;

[0091] Distribution module 203 is used to distribute various voice event types to voice interaction applications;

[0092] Driver module 204 is used to drive the voice interaction application to execute various voice type events and obtain the test results of the voice interaction application.

[0093] The testing device for voice interaction applications in this application embodiment can obtain a target file stream from a preset file, which includes a file stream generated after serializing the normal voice interaction event stream of the voice interaction application; deserialize the target file stream to generate multiple voice type events; distribute the multiple voice type events to the voice interaction application; drive the voice interaction application to execute the multiple voice type events, and obtain the test results of the voice interaction application. Thus, in this application embodiment, multiple voice type events can be distributed to the voice interaction application, i.e., simulating the automatic distribution of multiple voice type events to drive the voice interaction application to execute each voice type event, thereby obtaining the test results of the voice interaction application. This does not involve contact with the user interface and is suitable for testing voice interaction applications that require no physical interaction, thereby ensuring that the voice interaction application in the vehicle system can operate normally.

[0094] In some embodiments, the generation module 202 described above may specifically include:

[0095] A deserialization unit is used to deserialize the target file stream to obtain at least one voice event;

[0096] A construction unit is used to classify at least one voice event and construct multiple voice type events, including at least one of useless voice type events, wake-up voice type events, and command voice type events.

[0097] As one implementation of this application, in order to obtain the preset file, the above-mentioned device 200 may further include:

[0098] The second acquisition module is used to acquire the normal voice interaction event stream of the voice interaction application;

[0099] The serialization module is used to serialize the normal voice interaction event stream according to a preset sequence to obtain a file stream.

[0100] In some embodiments, the distribution module 203 may specifically include:

[0101] The distribution unit is used to distribute various voice type events to voice interaction applications in accordance with the distribution order indicated by the preset distribution strategy.

[0102] As another implementation of this application, in order to fully expose anomalies in the testing of voice interaction applications, the aforementioned distribution module 203 may further include:

[0103] The receiving unit is used to receive the driving signal sent by the event driver. The driving signal includes the target strategy parameter. Different strategy parameters correspond to different distribution strategies. The distribution strategy indicates the distribution order of various voice type events.

[0104] The determining unit is used to determine the distribution strategy corresponding to the target strategy parameter as the target distribution strategy among a plurality of preset distribution strategies;

[0105] The aforementioned distribution unit is also used to distribute various voice type events to voice interaction applications in accordance with the distribution order indicated by the target distribution strategy.

[0106] In some embodiments, the driving module 204 described above can be used to drive a voice interaction application to execute multiple voice type events in a preset order or in a random order to obtain the test results of the voice interaction application.

[0107] Based on the testing method for voice interaction applications provided in the above embodiments, this application also provides specific implementation methods for electronic devices. Please refer to the following embodiments.

[0108] Figure 3 A schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application is shown.

[0109] An electronic device may include a processor 301 and a memory 302 storing computer program instructions.

[0110] Specifically, the processor 301 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0111] Memory 302 may include mass storage for data or instructions. For example, and not limitingly, memory 302 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 302 may include removable or non-removable (or fixed) media. Where appropriate, memory 302 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 302 is non-volatile solid-state memory.

[0112] In certain embodiments, memory 302 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0113] The processor 301 reads and executes computer program instructions stored in the memory 302 to implement any of the voice interaction application testing methods in the above embodiments.

[0114] In one example, the electronic device may also include a communication interface 303 and a bus 310. For example, Figure 3 As shown, the processor 301, memory 302, and communication interface 303 are connected through bus 310 and complete communication with each other.

[0115] The communication interface 303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0116] Bus 310 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 310 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0117] The electronic device can execute the testing method for the voice interaction application in the embodiments of this application, thereby achieving a combination Figure 1 and Figure 2 The test methods and apparatus for the described voice interaction application.

[0118] Furthermore, in conjunction with the testing methods for voice interaction applications in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the testing methods for voice interaction applications in the above embodiments.

[0119] Based on the testing methods for voice interaction applications described in the above embodiments, this application provides a computer program product. When the instructions in this computer program product are executed by the processor of an electronic device, the electronic device performs the testing methods for voice interaction applications as described above.

[0120] Based on the testing method for voice interaction applications in the above embodiments, this application embodiment can provide a vehicle to implement this method. The vehicle includes at least one of the following: a testing device for voice interaction applications as described above; an electronic device as described above; a computer-readable storage medium as described above; or a computer program product as described above.

[0121] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0122] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0123] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0124] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0125] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

[0126] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the term "comprising" or any other variations thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A testing method for a voice interaction application, characterized in that, include: Obtain the target file stream from a preset file, which includes a file stream generated after serializing the normal voice interaction event stream of the voice interaction application; The target file stream is deserialized to generate various voice event types; Distribute the various voice type events to voice interaction applications; The voice interaction application is driven to execute the various voice type events, and the test results of the voice interaction application are obtained.

2. The method as described in claim 1, characterized in that, The process involves deserializing the target file stream to generate various voice event types, including: The target file stream is deserialized to obtain at least one voice event; The voice events of the at least one are classified to construct the multiple voice event types, which include at least one of useless voice events, wake-up voice events, and command voice events.

3. The method as described in claim 2, characterized in that, Before obtaining the target file stream from the preset file, the method further includes: Obtain the normal voice interaction event stream of the voice interaction application; The normal voice interaction event stream is serialized according to a preset sequence to obtain a file stream.

4. The method as described in claim 1, characterized in that, The distribution of the various voice type events to the voice interaction application includes: The various voice type events are distributed to the voice interaction application according to the distribution order indicated by the preset distribution strategy.

5. The method as described in claim 4, characterized in that, Before distributing the various voice type events to the voice interaction application according to the distribution order indicated by the preset distribution strategy, the method further includes: The system receives a drive signal from an event driver, the drive signal including a target strategy parameter, different strategy parameters corresponding to different distribution strategies, and the distribution strategy indicating the distribution order of the various voice type events; Among the preset multiple distribution strategies, the distribution strategy corresponding to the target strategy parameter is determined as the target distribution strategy; The step of distributing the various voice type events to the voice interaction application according to the distribution order indicated by the preset distribution strategy includes: The various voice type events are distributed to the voice interaction application according to the distribution order indicated by the target distribution strategy.

6. The method according to any one of claims 1-5, wherein driving the voice interaction application to execute the multiple voice type events and obtaining the test results of the voice interaction application includes: The voice interaction application is driven to execute the various voice type events in a preset order or in a random order to obtain the test results of the voice interaction application.

7. A testing device for a voice interaction application, characterized in that, include: The first acquisition module is used to acquire a target file stream from a preset file, wherein the preset file includes a file stream generated after serialization of a normal voice interaction event stream of a voice interaction application; The generation module is used to deserialize the target file stream and generate various voice event types; The distribution module is used to distribute the various voice type events to voice interaction applications; The driver module is used to drive the voice interaction application to execute the various voice type events and obtain the test results of the voice interaction application.

8. An electronic device, characterized in that, The electronic device includes: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the test method for the voice interaction application as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the test method for the voice interaction application as described in any one of claims 1-6.

10. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the test method for the voice interaction application as described in any one of claims 1-6.

11. A vehicle, characterized in that, Includes at least one of the following: The testing apparatus for voice interaction applications as described in claim 7; The electronic device as claimed in claim 8; The computer-readable storage medium as described in claim 9; The computer program product as described in claim 10.