Vehicle-mounted assistant random test method, system, equipment and medium
Patent Information
- Application Number
- CN202411409212.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-10
- Publication Date
- 2025-03-11
Smart Images

Figure CN119597635A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of automobile testing, and in particular to a method, system, device and medium for random testing of an in-vehicle assistant. Background Art
[0002] Currently, in-vehicle voice testing is mainly performed using the Monkey command or by playing wake-up audio and corpus. For the Monkey command testing method, since voice applications are resident in the background and are launched differently from other applications, they cannot be launched using the Monkey command. The parameters passed during launch are also different from other applications, so they cannot open pages and simulate user operations like other applications. Playing wake-up audio and corpus cannot allow voice applications to be tested interactively with the system or other applications. It can only test the stability of the voice application. Neither testing method can fully test the application. Summary of the Invention
[0003] In order to improve the comprehensiveness of in-vehicle voice testing, the present application provides a method, system, device and medium for random testing of an in-vehicle assistant.
[0004] In the first aspect, the present application provides a random testing method for an in-car assistant, which adopts the following technical solution:
[0005] A random testing method for an in-vehicle assistant, comprising:
[0006] Responding to the staff's test instructions, obtaining test requirements;
[0007] Determine the target test event and the total duration of the event test based on the test requirements;
[0008] Determine the event weight ratio of the target test event based on the test requirement content and the target test event;
[0009] Obtaining the event type of the target test event;
[0010] Determining a test time interval based on the event type and the total duration of the event test;
[0011] Generate a random test plan based on the target test event, the total test duration of the event, the event weight ratio and the test time interval;
[0012] An in-vehicle voice test is performed on a target vehicle based on the random test scheme.
[0013] By adopting the above technical solution, the target test event and the total duration of the event test are determined according to the test requirements, the test time interval and the event weight ratio are obtained according to the target test event and the total duration of the event test, and a random test plan is further generated. The random test plan includes various types of events and can automatically perform random tests on various types of events, meeting the requirements of random testing. The test events include all required test types, and can automatically perform random tests on multiple events, thereby improving the comprehensiveness of in-vehicle voice testing.
[0014] Optionally, determining the target test event and the total event test duration based on the test requirement content includes:
[0015] Get test support event data;
[0016] Determining test requirement keywords based on the test requirement content;
[0017] Determine a target test event based on the test requirement keyword and the test support event data;
[0018] Obtaining the number of events of the target test event;
[0019] The total duration of the event test is determined based on the target test event, the number of events and a preset duration rule.
[0020] Optionally, determining the event weight ratio of the target test event based on the test requirement content and the target test event includes:
[0021] Get the weight distribution rule;
[0022] Determine a target allocation rule based on the test requirement keyword, the number of events, and the weight allocation rule;
[0023] Obtaining a weight distribution ratio of the target distribution rule;
[0024] The event weight proportion of the target test event is determined based on the weight distribution ratio.
[0025] Optionally, determining the test time interval based on the event type and the total duration of the event test includes:
[0026] Determining execution steps of the target test event based on the event type;
[0027] Get the step execution time;
[0028] Determine a single event execution duration of the target test event based on the step execution duration and the execution step;
[0029] Determining an event execution duration based on the single event execution duration, the number of events, and the weight distribution ratio;
[0030] Determine the test interval duration based on the event execution duration and the total event test duration;
[0031] The test time interval is determined based on the test interval duration, the number of events and the weight distribution ratio.
[0032] Optionally, determining the test time interval based on the test interval duration, the number of events, and the weight distribution ratio includes:
[0033] Get the interval duration;
[0034] determining a number of test intervals based on the number of events;
[0035] Selecting a duration from the interval duration range based on the number of test intervals and the weight distribution ratio, and determining at least one interval duration;
[0036] The interval duration is used as the test time interval.
[0037] Optionally, the performing an in-vehicle voice test on the target vehicle based on the random test scheme includes:
[0038] Obtaining a test start time for the random test scheme;
[0039] Performing test performance data monitoring based on the test start event;
[0040] Recording the performance data in real time to generate performance test data;
[0041] The performance test data is bound to the random test scheme and the test start time to generate a test operation log.
[0042] Optionally, after binding the performance test data with the random test scheme and the test start time to generate a test operation log, the method further includes:
[0043] Analyze the test operation log and generate a test report;
[0044] The test report is sent to the mobile terminal of the staff member.
[0045] In a second aspect, the present application provides a random testing system for an in-car assistant, which adopts the following technical solutions:
[0046] A random testing system for an in-vehicle assistant, comprising:
[0047] A test requirement acquisition module is used to obtain test requirement content in response to the test instructions of the staff;
[0048] A target event determination module is used to determine a target test event and a total event test duration based on the test requirement content;
[0049] An event weight determination module, configured to determine an event weight ratio of the target test event based on the test requirement content and the target test event;
[0050] An event type acquisition module, configured to acquire the event type of the target test event;
[0051] A test interval determination module, configured to determine a test time interval based on the event type and the total duration of the event test;
[0052] A test plan generation module is used to generate a random test plan based on the target test event, the total test duration of the event, the event weight ratio and the test time interval;
[0053] The vehicle voice test module is used to perform an in-vehicle voice test on the target vehicle based on the random test scheme.
[0054] By adopting the above technical solution, the target test event and the total duration of the event test are determined according to the test requirements, the test time interval and the event weight ratio are obtained according to the target test event and the total duration of the event test, and a random test plan is further generated. The random test plan includes various types of events and can automatically perform random tests on various types of events, meeting the requirements of random testing. The test events include all required test types, and can automatically perform random tests on multiple events, thereby improving the comprehensiveness of in-vehicle voice testing.
[0055] In a third aspect, the present application provides an electronic device, which adopts the following technical solution:
[0056] An electronic device comprising a processor coupled to a memory;
[0057] The processor is used to execute the computer program stored in the memory, so that the electronic device executes the computer program of the in-vehicle assistant random testing method described in any one of the first aspects.
[0058] In a fourth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solution:
[0059] A computer-readable storage medium storing a computer program capable of being loaded by a processor and executing the random testing method for an in-vehicle assistant described in any one of the first aspects.
[0060] In summary, this application includes at least one of the following beneficial technical effects:
[0061] The target test event and the total duration of the event test are determined according to the test requirements. The test time interval and the event weight ratio are obtained according to the target test event and the total duration of the event test. A random test plan is further generated. The random test plan includes various types of events and can automatically perform random tests on various types of events, meeting the requirements of random testing. The test events include all required test types, and can automatically perform random tests on multiple events, thereby improving the comprehensiveness of the in-vehicle voice test. BRIEF DESCRIPTION OF THE DRAWINGS
[0062] Figure 1 This is a flowchart of a random testing method for an in-vehicle assistant provided in an embodiment of the present application.
[0063] Figure 2 This is a structural block diagram of a random testing system for an in-vehicle assistant provided in an embodiment of the present application.
[0064] Figure 3 This is a structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0065] The present application is further described in detail below with reference to the accompanying drawings.
[0066] The present application provides a random testing method for an in-car assistant. This method can be performed by an electronic device, which can be a server or a terminal device. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can be, but is not limited to, a smartphone, tablet computer, or desktop computer.
[0067] Figure 1 A flowchart of a random testing method for an in-car assistant provided in an embodiment of the present application.
[0068] like Figure 1 As shown, the main process of the method is described as follows (steps S101 to S107):
[0069] Step S101: Responding to a test instruction from a staff member, obtaining test requirement content.
[0070] In this embodiment, after the staff issues a test instruction, the test content contained in the test instruction is obtained. The test content includes but is not limited to the test start time, expected end time and test requirements. The test requirements are the functions that you want to test, for example, testing the voice wake-up function of the in-car assistant, testing the voice execution function of the in-car assistant, testing the system function of the in-car assistant, etc. The specific test requirement content needs to be set according to the actual test requirements and is not specifically limited here.
[0071] Step S102: determining the target test event and the total duration of the event test based on the test requirement content.
[0072] For step S102, obtain test support event data; determine test requirement keywords based on the test requirement content; determine the target test event based on the test requirement keywords and the test support event data; obtain the event number of the target test event; determine the total event test duration based on the target test event, event number and preset duration rules.
[0073] In this embodiment, the test support event data is the test event type that the test can provide, that is, the supported test event type. The voice test and touch test are converted into code program tests through coding. The supported test event types include voice events, system events, and other application events. Voice events are events that require voice triggering. Voice events include wake-up word triggering events and wake-up-free triggering events. The wake-up word is a specific word or phrase used to activate the voice recognition system in the car assistant. Under normal circumstances, the car assistant will be activated after the user inputs the wake-up word. The wake-up-free function allows the user to wake up the car assistant and interact with the voice recognition system without saying the specific wake-up word. The sample voices contained in the wake-up word and the wake-up-free function are converted into computer-readable text through automatic speech recognition (ASR) technology. When performing the test, after selecting the target test event, when the target test event is a voice event, the target test event is selected from the voice storage module storing the voice event, and the target test event is converted into a computer-readable text version through automatic speech recognition (ASR) technology, so that the text version is used for testing.
[0074] System events are common system operation events, including returning to the home page, navigation bar, returning, clicking the car screen, long pressing the car screen, short pressing the car screen, dragging and sliding the car screen, etc. The corresponding functions are called by setting the key name, description and key value. The key name, description and key value correspond one to one. For example, the key name is KEYCODE_CALL, the description is the dial key, and the key value is 5. When writing a program, you only need to call any one of the key name, description and key value to call the function.
[0075] Other application events are common application operation events, including starting an activity, starting a service, and sending a broadcast. They are implemented through adb commands. For example, to start an activity: adb shell am start-ncom.example.app / .MainActivity; to start a service: adb shell am startservice-ncom.example.app / .MyService; and to send a broadcast: adb shell am broadcast-aandroid.intent.action.MY_CUSTOM_ACTION-e "key" "value".
[0076] According to the supported test event types mentioned above, keywords are set for each branch in each supported test event type to obtain supported keywords. Keywords are also extracted for the functions that want to be tested in the test requirement content. The keywords extracted from the test requirement content are used as test requirement keywords. The test requirement keywords are matched with the support keywords. The test events used for the support keywords that match the test requirement keywords are used as target test events. The number of events of the target test events is determined. The preset duration rule is a table with the number of events and the basic test duration. The number of events is compared in the preset duration rule to determine the basic test duration corresponding to the current number of events. The additional test time is determined according to the specific target test event and the preset time rules. The additional test time is set in a table in the same way as the basic test time. The total additional test time is obtained by comparison. The additional test time is added to the basic test time to obtain the total test time. After obtaining the total test time, the total test time control is also implemented through code. It can be implemented according to the coded logic loop module and time function module coding. The obtained total test time can be sent to the staff's mobile terminal and executed after the staff completes the writing. The staff can also write multiple time control pages, and the system will automatically call the matching time control page according to the obtained total test time. It should be noted that the number mentioned here is not the total number of test events but the number of types.
[0077] Step S103: determining the event weight ratio of the target test event based on the test requirement content and the target test event.
[0078] For step S103, obtain the weight allocation rule; determine the target allocation rule based on the test requirement keyword, the number of events and the weight allocation rule; obtain the weight allocation ratio of the target allocation rule; determine the event weight ratio of the target test event based on the weight allocation ratio.
[0079] In this embodiment, when performing weight distribution, weight distribution is also performed through coding, which can be implemented according to the coding of the random function module. However, the random functions used for different test requirement keywords and time quantities are also different. For example, some random functions can calculate the weights of three events, and some random functions can calculate the weights of ten events. Therefore, it is necessary to determine the distribution rules that can be used under the current requirement keywords based on the test requirement keywords and the weight distribution rules. The weight distribution rules are provided with distribution rules that can test requirement keywords and test requirement keywords. After determining the distribution rules corresponding to all test requirement keywords, the distribution rules are intersected. The distribution rules corresponding to the number of events are selected from the distribution rules after the intersection. The distribution rules are used as the distribution rules. The weight distribution ratio is randomly distributed through the random function module to obtain the event weight ratio of each target test event. It should be noted that the event weight is related to the number of executions of each event. The specific weight ratio and the number of executions need to be set according to actual needs. As long as it can be completed within the total test time, no specific limitation is made here.
[0080] Step S104: Acquire the event type of the target test event.
[0081] In this embodiment, the event type of the target test event supports further subdivision of the test event type, including but not limited to voice wake-up word wake-up, system dialing, system hang-up, and service startup. The division and naming of specific event types need to be set according to actual needs and are not specifically limited here.
[0082] Step S105: Determine the test time interval based on the event type and the total duration of the event test.
[0083] For step S105, determine the execution steps of the target test event based on the event type; obtain the step execution time; determine the single event execution time of the target test event based on the step execution time and the execution steps; determine the event execution time based on the single event execution time, the number of events and the weight distribution ratio; determine the test interval time based on the event execution time and the total event test time; determine the test time interval based on the test interval time, the number of events and the weight distribution ratio.
[0084] Furthermore, an interval duration range is obtained; the number of test intervals is determined based on the number of events; a duration is selected from the interval duration range based on the number of test intervals and the weight distribution ratio to determine at least one interval duration; and the interval duration is used as the test time interval.
[0085] In this embodiment, the test time interval is also implemented through coding, and can be implemented according to the sleep function module of the coded event module, that is, adding a sleep function after each event. However, before adding the sleep function, it is necessary to determine the length of time that can be used for the interval and the length of the interval after each event.
[0086] First, determine the step execution time according to the execution steps of the target test event, and sum up the step execution time to obtain the single execution time of each target test event, and determine the total single execution time of each target test event according to the weight distribution, add up the total single execution time of all target test events to obtain the event execution time, and use the total event test time to subtract the event execution time to obtain the final test interval time. After obtaining the test interval time, determine the maximum and minimum values allowed for the interval time according to the set interval time interval, and use the number of test intervals and the weight distribution ratio to select the time within the interval time interval. When selecting the time, the test interval time can be evenly divided, and the corresponding value percentage can be set according to the weight distribution ratio. The total interval time of each target test event is determined according to the value percentage, and the interval time of the target test event is obtained by the number of individual target test events, thereby obtaining the test time interval. The specific distribution method needs to be set according to actual needs and is not specifically limited here.
[0087] Step S106: Generate a random test plan based on the target test event, the total event test duration, the event weight ratio and the test time interval.
[0088] In this embodiment, the target test event, the total event test duration, the event weight ratio and the test time interval are bound to ensure that the other data can be accurately obtained through one of the data, and the bound data is used as a random test scheme.
[0089] Step S107: Perform an in-vehicle voice test on the target vehicle based on a random test scheme.
[0090] For step S107, obtain the test start time of the random test scheme; monitor the test performance data based on the test start event; record the performance data in real time to generate performance test data; bind the performance test data with the random test scheme and the test start time to generate a test operation log.
[0091] In this embodiment, when the in-vehicle voice test begins, the test process is monitored in real time, the test start time is marked, and the test performance data is monitored in real time. A multi-threaded module is used to perform random tests on the in-vehicle system voice while saving relevant test data. The saved relevant test data is used as performance test data. Specifically, the application's performance data cpu / memory can be obtained through adb related commands. The command to obtain application cpu data is: top|grep "application package name"; to obtain application memory data: Dumpsys meminfo "application package name". The process number and thread number information of the relevant application are obtained through coding, and then the relevant application process number and thread number are monitored for changes. If changes occur, the latest log information is obtained and saved. The performance test data is bound to the random test plan and the test start time to generate a test operation log. After the test is completed, the file can be viewed to know what tests the current monkey test has performed, which is also convenient for subsequent problem reproduction.
[0092] In this embodiment, the test operation log is analyzed to generate a test report; and the test report is sent to a mobile terminal of a staff member.
[0093] After obtaining the test operation log, the test operation log is analyzed and processed to obtain the test duration, whether there are any anomalies in the performance data of each application, the number of crashes of each application, etc. The obtained data information is summed up to generate a test report, and the generated test report is sent to the staff's mobile terminal for the staff to analyze and view.
[0094] Figure 2 A structural block diagram of a random testing system 200 for an in-vehicle assistant provided in an embodiment of the application.
[0095] like Figure 2 As shown, the in-vehicle assistant random testing system 200 mainly includes:
[0096] The test requirement acquisition module 201 is used to obtain the test requirement content in response to the test instruction of the staff;
[0097] A target event determination module 202 is configured to determine a target test event and a total event test duration based on the test requirements;
[0098] An event weight determination module 203 is configured to determine an event weight ratio of a target test event based on the test requirement content and the target test event;
[0099] An event type acquisition module 204 is used to acquire the event type of the target test event;
[0100] A test interval determination module 205 is configured to determine a test time interval based on an event type and a total event test duration;
[0101] A test plan generation module 206 is configured to generate a random test plan based on the target test event, the total test duration of the event, the event weight ratio, and the test time interval;
[0102] The vehicle voice test module 207 is used to perform an in-vehicle voice test on the target vehicle based on a random test scheme.
[0103] As an optional implementation of this embodiment, the target event determination module 202 is specifically used to obtain test support event data; determine the test requirement keywords based on the test requirement content; determine the target test event based on the test requirement keywords and the test support event data; obtain the number of events of the target test event; determine the total duration of the event test based on the target test event, the number of events and the preset duration rules.
[0104] As an optional implementation of this embodiment, the event weight determination module 203 is specifically used to obtain weight allocation rules; determine target allocation rules based on test requirement keywords, event quantity and weight allocation rules; obtain the weight allocation ratio of the target allocation rule; and determine the event weight ratio of the target test event based on the weight allocation ratio.
[0105] As an optional implementation of this embodiment, the test interval determination module 205 includes:
[0106] An execution step determination module, used to determine the execution steps of a target test event based on the event type;
[0107] Step duration acquisition module, used to obtain step execution duration;
[0108] A single duration determination module, used to determine a single event execution duration of a target test event based on the step execution duration and the execution step;
[0109] An event duration determination module is used to determine the event execution duration based on the execution duration of a single event, the number of events, and the weight distribution ratio;
[0110] A test duration determination module is used to determine the test interval duration based on the event execution duration and the total event test duration;
[0111] The time interval determination module is used to determine the test time interval based on the test interval length, the number of events and the weight distribution ratio.
[0112] In this optional embodiment, the time interval determination module is specifically used to obtain the interval duration range; determine the number of test intervals based on the number of events; select the duration in the interval duration range based on the number of test intervals and the weight distribution ratio, and determine at least one interval duration; and use the interval duration as the test time interval.
[0113] As an optional implementation of this embodiment, the vehicle voice test module 207 is specifically used to obtain the test start time of the random test scheme; monitor the test performance data based on the test start event; record the performance data in real time to generate performance test data; bind the performance test data with the random test scheme and the test start time to generate a test operation log.
[0114] As an optional implementation of this embodiment, the in-vehicle assistant random testing system 200 further includes:
[0115] Test report generation module, used to analyze test operation logs and generate test reports;
[0116] The test report sending module is used to send the test report to the staff's mobile terminal.
[0117] In one example, the module in any of the above devices can be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.
[0118] For another example, when the modules in the device can be implemented in the form of a processing element scheduling program, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0119] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0120] Figure 3 This is a structural block diagram of the electronic device 300 provided in an embodiment of the present application.
[0121] like Figure 3 As shown, the electronic device 300 includes a processor 301 and a memory 302 , and may further include an information input / information output (I / O) interface 303 , one or more communication components 304 , and a communication bus 305 .
[0122] The processor 301 is used to control the overall operation of the electronic device 300 to complete all or part of the steps of the above-mentioned random testing method for the in-vehicle assistant. The memory 302 is used to store various types of data to support the operation of the electronic device 300. Such data may include, for example, instructions for any application or method operating on the electronic device 300, as well as application-related data. The memory 302 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0123] The I / O interface 303 provides an interface between the processor 301 and other interface modules, which may be a keyboard, a mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 304 is used for wired or wireless communication between the electronic device 300 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more thereof, therefore, the corresponding communication component 104 may include: Wi-Fi components, Bluetooth components, NFC components.
[0124] The electronic device 300 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to execute the random testing method for the in-vehicle assistant given in the above embodiment.
[0125] Communication bus 305 may include a path for transmitting information between the aforementioned components. Communication bus 305 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, for example. Communication bus 305 may be divided into an address bus, a data bus, a control bus, and the like.
[0126] The electronic device 300 may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., as well as fixed terminals such as digital TVs, desktop computers, etc., and may also be servers, etc.
[0127] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned in-vehicle assistant random testing method are implemented.
[0128] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., which can store program codes.
[0129] The terms "comprises," "comprising," or any other variations thereof are 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 inherent to such process, method, article, or apparatus.
[0130] The above description is merely a preferred embodiment of the present application and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of application involved in this application is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the aforementioned application concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions applied for in this application.
Claims
1. A random testing method for an in-vehicle assistant, characterized in that: include: Responding to the staff's test instructions, obtaining the test requirements; Determine the target test event and the total duration of the event test based on the test requirement content; Determine the event weight ratio of the target test event based on the test requirement content and the target test event; Obtaining the event type of the target test event; Determine a test time interval based on the event type and the total duration of the event test; Generate a random test plan based on the target test event, the total test duration of the event, the event weight ratio and the test time interval; An in-vehicle voice test is performed on the target vehicle based on the random test scheme.
2. The method according to claim 1, characterized in that Determining the target test event and the total duration of the event test based on the test requirement content includes: Get test support incident data; Determine test requirement keywords based on the test requirement content; Determine a target test event based on the test requirement keyword and the test support event data; Obtaining the event number of the target test event; The total duration of the event test is determined based on the target test event, the number of events and a preset duration rule.
3. The method according to claim 2, characterized in that The determining the event weight ratio of the target test event based on the test requirement content and the target test event includes: Get the weight distribution rule; Determine a target allocation rule based on the test requirement keyword, the number of events and the weight allocation rule; Obtaining a weight distribution ratio of the target distribution rule; The event weight ratio of the target test event is determined based on the weight allocation ratio.
4. The method according to claim 3, characterized in that Determining the test time interval based on the event type and the total duration of the event test includes: Determining execution steps of the target test event based on the event type; Get the step execution time; Determine a single event execution time of the target test event based on the step execution time and the execution step; Determine the event execution duration based on the single event execution duration, the number of events and the weight distribution ratio; Determine the test interval duration based on the event execution duration and the total event test duration; The test time interval is determined based on the test interval duration, the number of events and the weight distribution ratio.
5. The method according to claim 1, characterized in that Determining the test time interval based on the test interval duration, the number of events and the weight distribution ratio includes: Get the interval duration; determining a number of test intervals based on the number of events; Selecting a duration in the interval duration range based on the number of test intervals and the weight distribution ratio, and determining at least one interval duration; The interval duration is used as the test time interval.
6. The method according to claim 1, characterized in that The performing of an in-vehicle voice test on a target vehicle based on the random test scheme includes: Obtaining the test start time of the random test scheme; Perform test performance data monitoring based on the test start event; Recording the performance data in real time to generate performance test data; The performance test data is bound to the random test scheme and the test start time to generate a test operation log.
7. The method according to claim 6, characterized in that After binding the performance test data with the random test scheme and the test start time to generate a test operation log, the method further includes: Analyze the test operation log and generate a test report; The test report is sent to the mobile terminal of the staff member.
8. A random testing system for an in-vehicle assistant, characterized in that: include: A test requirement acquisition module is used to obtain test requirement content in response to the test instruction of the staff; A target event determination module, used to determine a target test event and a total event test duration based on the test requirement content; An event weight determination module, used to determine the event weight ratio of the target test event based on the test requirement content and the target test event; An event type acquisition module, used to acquire the event type of the target test event; A test interval determination module, used to determine a test time interval based on the event type and the total duration of the event test; A test plan generation module, used to generate a random test plan based on the target test event, the total test duration of the event, the event weight ratio and the test time interval; The vehicle voice test module is used to perform an in-vehicle voice test on a target vehicle based on the random test scheme.
9. An electronic device, characterized in that: comprising a processor coupled to a memory; The processor is configured to execute a computer program stored in the memory, so that the electronic device executes the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The method comprises a computer program or an instruction, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 7.