CN117370143A

CN117370143A - Vehicle-mounted device testing method and device, electronic equipment and storage medium

Info

Publication number: CN117370143A
Application number: CN202210772127.XA
Authority: CN
Inventors: 周长瑞
Original assignee: Beijing Rockwell Technology Co Ltd
Current assignee: Beijing Rockwell Technology Co Ltd
Priority date: 2022-06-30
Filing date: 2022-06-30
Publication date: 2024-01-09

Abstract

The disclosure relates to a vehicle testing method, a vehicle testing device, electronic equipment and a storage medium. The vehicle testing method is applied to a processor with an interaction function in a vehicle system, and specifically comprises the following steps: acquiring a first configuration file of a to-be-tested item, wherein the first configuration file comprises an identifier of at least one use case corresponding to the to-be-tested item; calling at least one use case to test according to the identification of the at least one use case in the first configuration file and generating a test result of the item to be tested; and displaying the test result in a pre-generated target interface, wherein the target interface is generated based on the acquired second configuration file of the item to be tested, and the second configuration file comprises relevant configuration of the interface. The method provided by the disclosure realizes the display of the test items and the interface of the vehicle-mounted device by means of the configuration file, increases the flexibility of debugging and improves the test efficiency.

Description

Vehicle-mounted device testing method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of vehicle testing, and in particular relates to a vehicle machine testing method, a vehicle machine testing device, electronic equipment and a storage medium.

Background

With the widespread use of vehicles, it is generally necessary to configure the vehicles with various functions in order to meet the use demands, and to put the vehicles into the market after each function of the vehicles passes the test. At present, the test items and the displayed functions are written in the codes for testing and displaying the codes, but a large number of codes are needed to be added if the use cases are needed to be added in the test process, so that the running efficiency of the codes is greatly reduced, the codes are also needed to be compiled after each time of code modification, the time needed for compiling the codes is longer, and the working efficiency is reduced. Therefore, when the existing method is used for testing the vehicle machine, the code needs to be adjusted and modified for multiple times, the debugging flexibility and the testing efficiency are low, and the testing cost is high.

Disclosure of Invention

In order to solve the technical problems, the present disclosure provides a vehicle testing method, a device, an electronic device and a storage medium, which increase the flexibility of debugging and reduce the development cost.

In a first aspect, an embodiment of the present disclosure provides a vehicle testing method, where the method includes:

acquiring a first configuration file of a to-be-tested item, wherein the first configuration file comprises an identifier of at least one use case corresponding to the to-be-tested item;

Calling the at least one use case to test according to the identification of the at least one use case in the first configuration file and generating a test result of the item to be tested;

and displaying the test result in a pre-generated target interface, wherein the target interface is generated based on the acquired second configuration file of the item to be tested, and the second configuration file comprises relevant configuration of the interface.

Optionally, the second configuration file further includes a mode selection identifier.

Optionally, the calling the at least one use case to test according to the identifier of the at least one use case in the first configuration file and generating a test result of the item to be tested includes:

analyzing the first configuration file, and determining the identification of the at least one use case;

analyzing the acquired second configuration file, and determining a target mode, wherein the target mode is used for determining a mode of testing based on the at least one use case;

and calling the at least one use case to test and generating a test result of the item to be tested based on the identification of the at least one use case in the target mode.

Optionally, the calling the at least one use case to test and generating a test result of the item to be tested based on the identifier of the at least one use case in the target mode includes:

If the target mode is the first mode, directly calling the at least one use case to test based on the identification of the at least one use case, and generating a test result of the item to be tested; or,

and if the target mode is the second mode, calling the at least one use case to test according to the target interface and the identification of the at least one use case, and generating a test result of the item to be tested.

Optionally, the calling the at least one use case to test according to the target interface and the identifier of the at least one use case and generating a test result of the item to be tested includes:

displaying a target interface, wherein the target interface comprises a target identifier, and the target identifier corresponds to the identifier of the at least one use case;

and responding to the triggering operation of the target identifier, calling the target case corresponding to the target identifier in the at least one case to test, and generating a test result of the item to be tested.

Optionally, after displaying the test result, the method further includes:

and if the test result does not meet the test target of the item to be tested, acquiring an updated first configuration file, wherein the identifier of at least one use case is added and/or deleted in the updated first configuration file.

Optionally, the method further comprises:

acquiring an updated second configuration file;

analyzing the updated second configuration file to obtain interface information corresponding to the item to be tested;

and based on the interface information, calling a vehicle display interface to update the target interface.

Optionally, the method further comprises:

and sending the test result to an upper computer, wherein the upper computer is used for analyzing the item to be tested.

In a second aspect, an embodiment of the present disclosure provides a vehicle testing apparatus, including:

the device comprises an acquisition unit, a storage unit and a storage unit, wherein the acquisition unit is used for acquiring a first configuration file of a to-be-tested item, and the first configuration file comprises an identifier of at least one use case corresponding to the to-be-tested item;

the testing unit is used for calling the at least one use case to test according to the identification of the at least one use case in the first configuration file and generating a test result of the item to be tested;

and the display unit is used for displaying the test result in a pre-generated target interface, wherein the target interface is generated based on the acquired second configuration file of the item to be tested, and the second configuration file comprises relevant configuration of the interface.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

a memory;

a processor; and

a computer program;

wherein the computer program is stored in the memory and configured to be executed by the processor to implement the vehicle testing method as described above.

In a fourth aspect, embodiments of the present disclosure provide a computer readable storage medium having a computer program stored thereon, which when executed by a processor, implements the steps of the vehicle testing method described above.

The embodiment of the disclosure provides a vehicle testing method, a vehicle testing device, electronic equipment and a storage medium. The vehicle testing method is applied to a processor with an interaction function in a vehicle system, and specifically comprises the following steps: acquiring a first configuration file of a to-be-tested item, wherein the first configuration file comprises an identifier of at least one use case corresponding to the to-be-tested item; calling at least one use case to test according to the identification of the at least one use case in the first configuration file and generating a test result of the item to be tested; and displaying the test result in a pre-generated target interface, wherein the target interface is generated based on the acquired second configuration file of the item to be tested, and the second configuration file comprises relevant configuration of the interface. The method provided by the disclosure realizes the display of the test items and the interface of the vehicle-mounted device by means of the configuration file, increases the flexibility of debugging, improves the test efficiency, and further reduces the test cost.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

In order to more clearly illustrate the embodiments of the present disclosure or the solutions in the prior art, the drawings that are required for the description of the embodiments or the prior art will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.

Fig. 1 is a schematic structural diagram of a vehicle-mounted system according to an embodiment of the disclosure;

fig. 2 is a schematic flow chart of a vehicle testing method according to an embodiment of the disclosure;

FIG. 3 is a schematic illustration of an interface provided by an embodiment of the present disclosure;

fig. 4 is a schematic flow chart of a testing method of a vehicle machine according to an embodiment of the disclosure;

fig. 5 is a schematic structural diagram of a vehicle testing device according to an embodiment of the disclosure;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

In order that the above objects, features and advantages of the present disclosure may be more clearly understood, a further description of aspects of the present disclosure will be provided below. It should be noted that, without conflict, the embodiments of the present disclosure and features in the embodiments may be combined with each other.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced otherwise than as described herein; it will be apparent that the embodiments in the specification are only some, but not all, embodiments of the disclosure.

With the widespread use of vehicles, it is generally necessary to configure the vehicles with various functions in order to meet the use demands, and to put the vehicles into the market after each function of the vehicles passes the test. At present, the test items and the displayed functions are written in the codes for testing and displaying the codes, but a large number of codes are needed to be added if the use cases are needed to be added in the test process, so that the running efficiency of the codes is greatly reduced, the codes are also needed to be compiled after each time of code modification, the time needed for compiling the codes is longer, and the working efficiency is reduced. Secondly, if the interface display corresponding to the test item needs to be modified, the modification in the code is also needed, and after the code is modified, the code is compiled again, so that a great deal of time is consumed. Therefore, when the existing method is used for testing the vehicle machine, the code needs to be adjusted and modified for multiple times, the debugging flexibility and the testing efficiency are low, and the testing cost is high.

Aiming at the technical problems, the embodiment of the disclosure provides a vehicle testing method, which is specifically described in detail through the following embodiments.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a vehicle system provided by an embodiment of the disclosure, where the vehicle system 100 in fig. 1 includes a processor 110, an upper computer 120, a use case database 130 and a user interface 140, where the vehicle system 100 may be understood as a vehicle test item configurable DV system, the DV system is a lightweight vehicle test system, the processor 110 is denoted as a DV core, the processor 110 is a core of the entire vehicle system, and the DV core is responsible for an interactive function and other functions of the entire vehicle system; the upper computer 120 is configured to receive a test result generated by the processor 110, and perform information interaction with the processor 110; the use case database 130 stores a plurality of use cases in advance, the use cases are stored in a code form, each use case can realize different functions, each use case can also be called a test item, the use cases are marked as cases, each case has a corresponding identifier, such as case1, case2, case n and the like, each case can also comprise a plurality of tests, each test has a corresponding identifier, the plurality of tests can be directly called, for example, 2 tests are also marked as case1-1 and case1-2; the user interface 140 is responsible for UI display and touch functions (touch functions) of the entire vehicle system, denoted DV UI (libui. So), and specifically may call the packaged. C file to implement the display and touch functions. The working process of the vehicle machine system is that the processor 110 receives a first configuration file and a second configuration file, the first configuration file can be understood as a test item configuration file (case config), the second configuration file can be understood as an interface configuration file (UI config), the processor 110 analyzes the first configuration file and the second configuration file, calls a test case in the case database 130 according to the analyzed first configuration file to test, generates a test result, and simultaneously displays a target interface through the user interface 140 according to the second configuration file, wherein the target interface is an interface corresponding to a to-be-tested item, and the subsequently generated test result is displayed on the target interface.

Fig. 2 is a flow chart of a vehicle testing method according to an embodiment of the present disclosure, which is applied to a processor 110 with an interaction function, and specifically includes the following steps S210 to S230 shown in fig. 2:

s210, acquiring a first configuration file of the item to be tested, wherein the first configuration file comprises an identifier of at least one use case corresponding to the item to be tested.

It can be understood that the processor obtains a first configuration file of an item to be tested, where the item to be tested refers to related content of a vehicle machine to be tested currently, for example, stability of performance of the test vehicle machine, and the first configuration file can be generated by using a tool running on a linux operating system, the tool can configure at least one use case related to the item to be tested, and determine an identifier of the at least one use case corresponding to the item to be tested, for example, the first configuration file includes identifiers of multiple use cases such as case1, case2, case3-1, and the like, where case3-1 represents a first test in case3, and the content of the item to be tested currently can be tested by calling 3 use cases according to the identifier related to the first configuration file.

S220, calling the at least one use case to test according to the identification of the at least one use case in the first configuration file, and generating a test result of the item to be tested.

It may be understood that, on the basis of S210 above, the processor obtains the first configuration file, parses the first configuration file, determines the identifier of at least one use case included in the first configuration file, then invokes a corresponding use case in the use case database 130 according to the identifier of the at least one use case to perform a test, and generates a test result of the item to be tested, where it may be understood that the first configuration file further includes parameter information of a use case that needs to be configured with parameters in the at least one use case, where the parameter information is used to assign a value to a variable related to the invoked use case.

And S230, displaying the test result in a pre-generated target interface.

The target interface is generated based on the acquired second configuration file of the item to be tested, and the second configuration file comprises relevant configuration of the interface.

It can be understood that the processor may acquire the second configuration file of the item to be tested while acquiring the first configuration file, or acquire the first configuration file and the second configuration file in order, where the acquisition order is not limited, the second configuration file is an interface configuration file related to the item to be tested, and the second configuration file includes at least one icon related to the identifier of the use case and related configurations displayed, for example, the color, the size, etc. of the icon, where the related configuration file displayed may be a displayed area, displayable content in each area, etc., and specifically, the configuration of a specific interface in the second configuration file is not limited and may be selected according to the user requirement. After the processor obtains the second configuration file, the processor analyzes the second configuration file to obtain analysis data of the display interface, the analysis data of the display interface is displayed through the user interface 140, the interface displayed by the user interface 140 is marked as a target interface, and the target interface can display at least one identification of a use case and also can display related contents such as items to be tested. And then, after the processor acquires the test result, displaying the test result on the target interface.

For example, referring to fig. 3, fig. 3 is an interface schematic diagram provided in the embodiment of the present disclosure, where the target interface 310 is an initial interface generated according to the second configuration file, the target interface 310 includes at least one identifier 311 of a use case and a display area 312, the color, the display position, and the size of the at least one identifier 311 of the use case are determined based on the second configuration file, the target interface 310 includes 3 icons, which are respectively denoted as icon 1, icon 2, and icon 3, each icon corresponds to at least one use case, the display area 312 may display a test result of an item to be tested, for example, display contents such as "test success" or "test failure", and may also display "test abnormality", specifically, see the target image 320, display a word such as "test success" in the display area 312, and further may display a cause of test failure of the tester and related data of the test, where specific display contents are not limited.

Optionally, after displaying the test result, the method further includes:

It can be understood that, on the basis of S230, after the test result of the test item is obtained, if the obtained test result is a test failure, that is, the test result does not meet the preset test target of the test item to be tested, the test target may be determined by the user according to the test item, for example, when the stability test of the vehicle is performed, the stability prediction target is set to 98%. In this case, the test item may be adjusted by modifying the identifier of the use case or the parameter value of the use case in the first configuration file, that is, the first configuration file is updated, specifically, the identifier of at least one use case may be increased or decreased, and/or the parameter value of the use case may be modified to perform multiple tests, until the prediction target is met, so that the work of modifying the code, compiling the code, and the like is not required, and the flexibility of the test and the test rate are increased.

Optionally, the method further comprises:

acquiring an updated second configuration file; analyzing the updated second configuration file to obtain interface information corresponding to the item to be tested; and based on the interface information, calling a vehicle display interface to update the target interface.

It can be understood that after the target interface is displayed based on the second configuration file, if the target interface needs to be adjusted, only the second configuration file needs to be updated, specifically, the display size, color and other parameters of the icon in the second configuration file can be adjusted, then the updated second configuration file is analyzed to obtain updated interface information, and the interface information is displayed through a user interface (DV UI), that is, the layout of the target interface is readjusted. It can be understood that the first configuration file and the second configuration file are related, and the identifier of at least one use case in the first configuration file has a corresponding icon in the second configuration file, and it is also possible that two use cases correspond to one icon, and a specific correspondence is not limited, so that after the identifier of the use case in the first configuration file is adjusted, that is, after the use case is increased or decreased, interface information in the second configuration file is correspondingly adjusted.

Optionally, the method further comprises:

It can be understood that after the processor generates the test result, the test result is sent to the upper computer connected with the processor, and after the upper computer receives and stores the test result, the test result can be comprehensively analyzed, so that the use cases and parameter values required by the test items can be conveniently and better adjusted, the test efficiency is improved,

the vehicle-mounted device testing method provided by the embodiment of the disclosure is applied to a processor with an interaction function, the processor can acquire a first configuration file and a second configuration file at the same time, or can acquire the first configuration file and the second configuration file according to a sequence, analyze the acquired first configuration file and the second configuration file, call each application example corresponding to at least one application example after analysis to test according to the identification of each identification, generate a testing result, construct a target interface according to the analyzed interface information, display the testing result in the target interface, and display the testing result, parameter values and the like of each generated testing result and each application example in real time in the process of performing multiple adjustment testing. According to the method provided by the embodiment of the disclosure, the code amount is reduced by using the configuration file, the flexibility of modification and the running efficiency of the code are improved, the configuration file is only required to be modified to reduce or increase the use cases in the process of testing and adjusting, interface information such as icons and the like can be directly modified in the configuration file, the provided configuration file can be directly debugged in hardware equipment, operations such as code modification and code compiling are not required, the debugging time is saved, the working efficiency is improved, and the implementation is convenient.

On the basis of the foregoing embodiments, fig. 4 is a schematic flow chart of a vehicle-mounted device testing method according to the embodiment of the present disclosure, optionally, according to the identifier of the at least one use case in the first configuration file, invoking the at least one use case to perform testing and generating a testing result of the item to be tested, which specifically includes the following steps S410 to S430 shown in fig. 4:

It is understood that the second configuration file (UI configuration file) includes, in addition to the interface information, a mode selection identifier, where the mode selection identifier is used to configure whether to perform a test of a certain use case or a test of a certain use case by clicking on the target interface, and it is understood that the target interface is a clickable touch screen.

S410, analyzing the first configuration file, and determining the identification of the at least one use case.

It can be understood that the processor analyzes the first configuration file, determines the identifier of each use case in the first configuration file, and may also obtain the parameter values and the like required by the use cases, for example, in the above example, the identifiers of case1, case2, case3-1 and the like obtained by analysis.

S420, analyzing the acquired second configuration file, and determining a target mode, wherein the target mode is used for determining a mode of testing based on the at least one use case.

It can be understood that the second configuration file is analyzed, and a target mode is determined according to the mode selection identifier obtained after the analysis, specifically, the processor obtains the second configuration file, analyzes the second configuration file to obtain analyzed data, the analyzed data includes interface information and mode selection identifiers, then determines the target mode according to the mode selection identifier, and corresponds to different calling cases in different modes, the target mode can be a first mode or a second mode, for example, the parameter configured by the mode selection identifier is 1, the target mode can be determined to be the first mode, if the parameter configured by the mode selection identifier is 2, the target mode can be determined to be the second mode, the first mode means that a user is not required to click on an icon of a case in the target interface, after the processor analyzes the first configuration information, the processor can directly test according to the calling case of the case, that is, interaction with the target interface is not required before the test is performed, and the operation can be performed directly at the rear end; the second mode refers to that after the user needs to click on an icon of a use case in the target interface, the processor rerun the use case, that is, does not directly run the use case, but runs the use case by clicking on the icon of the use case in the target interface.

S430, calling the at least one use case to test and generating a test result of the item to be tested based on the identification of the at least one use case in the target mode.

It can be understood that, based on the above S410 and S420, in the target mode, based on the identifier of at least one use case, a corresponding use case is called in the constructed use case database to perform a test, and a test result of the current item to be tested is generated, which is specifically described in the following embodiments.

Optionally, in S430 above, based on the identification of the at least one use case in the target mode, the at least one use case is called to perform a test and generate a test result of the item to be tested, which may be specifically implemented by the following steps:

It may be understood that, based on the foregoing embodiment, whether the target mode is the first mode is determined, if the target mode is the first mode, in the first mode, the processor directly invokes the application corresponding to the identifier according to the identifier of at least one application parsed by the first configuration file to perform the test, and generates the test result of the item to be tested, where at least one test application may run simultaneously, may run sequentially, may also obtain the output of the previous application, and then run the next application according to the output, and the specific running situation is not limited. If the target mode is the second mode, calling at least one use case to test based on the target interface and the identification of the at least one use case, and generating a test result of the item to be tested, wherein the flow of generating the test result in the application scene of the second mode is specifically referred to the following embodiments.

Optionally, the step of calling the at least one use case to test and generating a test result of the item to be tested according to the target interface and the identifier of the at least one use case may specifically be implemented by the following steps:

It can be understood that, on the basis of the above embodiment, if the target mode is determined to be the second mode by judging, the user is required to click on the icon of the case in the target interface to perform the case test, that is, the user actively determines the case test sequence, for example, see the above example, the first configuration file includes identifiers of 3 cases such as case1, case2, and case3-1, and there is a corresponding icon in the target interface, where the icon may be denoted as a target identifier, the icons corresponding to the identifiers of 3 cases such as case1, case2, and case3-1 are denoted as icon 1, icon 2, and icon 3 in sequence, after clicking on the icon 1 in the target interface, the processor detects a triggering operation of the icon 1, and calls the case in the case database based on the identifier of the case (target case) corresponding to the icon 1, and running case1 to test, generating test result of case1, recording as test result 1, sending the test result 1 to the target interface to display, then, if the test result 1 meets the set test target, referring specifically to fig. 3, clicking icon 1 in the target interface 310, then, running case1 to generate test result 1, updating the target interface 310 to be the target interface 320, displaying test result 1 in the display area 312, wherein test result 1 is "test success", in this case, icon 2 in the target interface 320 can be clicked continuously to run case2 corresponding to test, generating test result 2 referring to the process of generating test result 1, not being repeated here, if test result 1 does not meet the set target, adjusting the first configuration file, for example, the relevant parameters of use case1 are modified.

According to the vehicle machine testing method provided by the embodiment of the disclosure, the mode identification identifier is configured in the second configuration file, the target mode is determined, that is, whether a certain icon in the target interface is clicked to test a certain use case is configured, if the target mode is determined to be the first mode, at least one use case can be called to test according to the identifier of the at least one use case determined after the analysis of the first configuration file, a testing result is generated, the testing result is displayed in the target interface, if the target mode is determined to be the second mode, a user is required to click the icon in the target interface to test the use case, and after the processor detects triggering operation on the certain icon (the target identifier), the use case corresponding to the icon is called to test, and the testing result of the use case is generated. According to the method provided by the disclosure, different modes can be configured through the configuration file to call at least one use case for testing, a test result is generated, interaction between the target interface and the use case can be realized based on the second mode, at least one use case can be more intuitively and clearly called for testing the automobile and the machine, the flexibility of testing can be further improved through interaction with the target interface, and the operation is simpler and more convenient.

Fig. 5 is a schematic structural diagram of a vehicle testing device according to an embodiment of the disclosure. The vehicle testing device provided in the embodiment of the present disclosure may execute the processing flow provided in the above-mentioned vehicle testing method embodiment, and be applied to the processor 110 in the vehicle system 100, as shown in fig. 5, the vehicle testing device 500 includes an obtaining unit 510, a testing unit 520, and a display unit 530, where:

the obtaining unit 510 is configured to obtain a first configuration file of a to-be-tested item, where the first configuration file includes an identifier of at least one use case corresponding to the to-be-tested item;

a test unit 520, configured to invoke the at least one use case to perform a test according to the identifier of the at least one use case in the first configuration file and generate a test result of the item to be tested;

and a display unit 530, configured to display the test result in a pre-generated target interface, where the target interface is generated based on an acquired second configuration file of the item to be tested, and the second configuration file includes relevant configurations of the interface.

Optionally, in the test unit 520, according to the identifier of the at least one use case in the first configuration file, the at least one use case is called to perform a test and generate a test result of the item to be tested, which is specifically configured to:

Optionally, the step of calling the at least one use case to perform the test and generating a test result of the item to be tested in the test unit 520 based on the identifier of the at least one use case in the target mode is specifically used for:

Optionally, after displaying the test result, the apparatus 500 is further configured to:

Optionally, the apparatus 500 is further configured to:

acquiring an updated second configuration file;

Optionally, the apparatus 500 is further configured to:

The vehicle testing device of the embodiment shown in fig. 5 may be used to implement the technical solution of the above method embodiment, and its implementation principle and technical effects are similar, and are not described herein again.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure. Referring now in particular to fig. 6, a schematic diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure is shown. The electronic device 600 in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), wearable electronic devices, and the like, and fixed terminals such as digital TVs, desktop computers, smart home devices, and the like. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 6, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphic processor, etc.) 601, which may perform various suitable actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603 to implement a multimedia information processing method of an embodiment as described in the present disclosure. In the RAM 603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program containing program code for performing the method shown in the flowcharts, thereby implementing the multimedia information processing method as described above. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 601.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

Alternatively, the electronic device may perform other steps described in the above embodiments when the above one or more programs are executed by the electronic device.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or the like that comprises the element.

The foregoing is merely a specific embodiment of the disclosure to enable one skilled in the art to understand or practice the disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown and described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A vehicle testing method, the method comprising:

2. The method of claim 1, wherein the second configuration file further includes a mode selection identifier, and the calling the at least one use case to test and generating a test result of the item to be tested according to the identifier of the at least one use case in the first configuration file includes:

3. The method according to claim 2, wherein invoking the at least one use case for testing and generating the test result of the item to be tested based on the identification of the at least one use case in the target mode comprises:

4. A method according to claim 3, wherein the calling the at least one use case to test and generating the test result of the item to be tested according to the target interface and the identification of the at least one use case includes:

5. The method of claim 1, wherein after displaying the test result, the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

acquiring an updated second configuration file;

7. The method according to claim 1, wherein the method further comprises:

8. A vehicle testing apparatus, the apparatus comprising:

9. An electronic device, comprising:

a memory;

a processor; and

a computer program;

wherein the computer program is stored in the memory and configured to be executed by the processor to implement the in-car testing method of any one of claims 1 to 7.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, carries out the steps of the vehicle testing method according to any one of claims 1 to 7.