Android interface concurrent testing method, device, equipment and storage medium

By obtaining and classifying the Android interface, using preset applications and thread pools to generate test threads and conducting concurrent testing, the problems of low testing efficiency and accuracy in the existing technology are solved, and efficient concurrent testing of the Android interface is achieved.

CN113836032BActive Publication Date: 2024-11-26DONGFENG MOTOR CO LTD DONGFENG NISSAN PASSENGER VEHICLE CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111168562.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-30
Publication Date
2024-11-26
Estimated Expiration
2041-09-30

AI Technical Summary

Technical Problem

The prior art tests the Android interface concurrently, and the testing efficiency and accuracy are low, and it is impossible to accurately and efficiently simulate the concurrent calls of multiple APPs to the interface.

Method used

By obtaining the Android interfaces of the target vehicle, generating a collection of test threads according to the interface type, using preset applications and thread pools to simulate concurrent tests, implementing concurrent tests on the interface, extracting test results and judging protection exceptions.

Benefits of technology

It improves the accuracy and efficiency of concurrent testing of Android interfaces, and can quickly and effectively simulate large-scale concurrent call interface tests.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113836032B_ABST
    Figure CN113836032B_ABST
Patent Text Reader

Abstract

The present invention relates to the technical field of interface testing, and discloses an Android interface concurrent testing method, device, equipment and storage medium. The method comprises: determining a corresponding interface type according to each Android interface of a target vehicle computer; generating a target test thread set according to each preset application and a preset thread pool; extracting each test thread in the target test thread set; performing concurrent testing on each Android interface through each test thread and the interface type to obtain a corresponding test result; since the present invention generates each test thread in the target test thread set and the interface type of the target vehicle computer through each preset application and a preset thread pool, performs concurrent testing on each Android interface to obtain a corresponding test result, compared with the prior art of manually clicking on an application or using an automated tool to test the Android interfaces one by one, the present invention can quickly and effectively simulate large-scale concurrent interface call testing, and effectively improve the accuracy and efficiency of the test.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of interface testing technology, and in particular to an Android interface concurrent testing method, device, equipment and storage medium. Background Art

[0002] In recent years, with the rapid development of the automotive industry and the consumer electronics industry and the rapid popularization of artificial intelligence around the world, people's demand for car computers, mobile phones, and portable devices has increased. Currently, car computers, mobile phones, and portable devices generally use the Android system, and most of the functions are carried by applications (APP).

[0003] The Android interface is the bridge between the APP and the Android system. By calling the Android interface, the APP can interact with the hardware (vehicles, mobile phones, portable devices). Therefore, the performance of the Android interface is particularly important, and concurrent testing is the best way to test the performance of the Android interface. Especially for Android terminal system developers, it is necessary to test whether the Android interface is protected by concurrent calls to ensure the development quality. The commonly used concurrent testing scheme is to test each application manually or test each item through automated tools. However, due to (1) the slow speed of manual clicking, it is impossible to accurately and efficiently test a large number of Android interfaces (2) the current automated tools cannot simulate the concurrent testing of multiple APPs on the interface; therefore, the test efficiency and the accuracy of the test results are low.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide an Android interface concurrent testing method, device, equipment and storage medium, aiming to solve the technical problems of low accuracy and efficiency of concurrent testing of Android interfaces in the prior art.

[0006] To achieve the above object, the present invention provides an Android interface concurrent testing method, which comprises the following steps:

[0007] Obtain each Android interface of the target vehicle computer, and determine the corresponding interface type according to each Android interface;

[0008] Generate a target test thread set according to each preset application and preset thread pool;

[0009] Extracting each test thread in the target test thread set;

[0010] Concurrently test the Android interfaces through the test threads and the interface types to obtain corresponding test results.

[0011] Optionally, the obtaining of each Android interface of the target vehicle computer and determining a corresponding interface type according to each Android interface includes:

[0012] Obtain each Android interface of the target vehicle computer, and extract identification information of each Android interface;

[0013] Classifying the Android interfaces according to the identification information;

[0014] Determine the corresponding interface type based on the classification result.

[0015] Optionally, generating a target test thread set according to each preset application and a preset thread pool includes:

[0016] Obtain corresponding program running information according to each preset application program;

[0017] Simulating the program running information through a preset thread pool;

[0018] Generate a target test thread set based on the simulation results.

[0019] Optionally, the concurrently testing each Android interface by each test thread and the interface type to obtain corresponding test results includes:

[0020] Obtaining an execution order of the Android interfaces according to the interface type;

[0021] Concurrently testing the Android interfaces through the test threads and the execution order to obtain corresponding test results.

[0022] Optionally, the concurrently testing the Android interfaces through the test threads and the execution order to obtain corresponding test results includes:

[0023] Obtain a preset random strategy, and generate a target random number according to the preset random strategy;

[0024] Determine an initial Android interface and a non-initial Android interface according to the target random number and the Android interfaces;

[0025] The initial Android interface and the non-initial Android interface are tested concurrently by each test thread and the execution order to obtain corresponding test results.

[0026] Optionally, after concurrently testing the Android interfaces through the test threads and the interface types to obtain corresponding test results, the method further includes:

[0027] Extract the test return value and test log in the test results;

[0028] Determine whether the test return value is within a target range and / or whether abnormal information appears in the test log;

[0029] If the test return value is not within the target range and / or abnormal information appears in the test log, it is determined that the concurrent protection of the target locomotive is abnormal.

[0030] Optionally, the determining whether the test return value is within a target range and / or whether the test log contains abnormal information further includes:

[0031] If the test return value is within the target range and / or the test log does not contain abnormal information, determining whether the interface of the target vehicle computer displays abnormality during the operation of each preset application;

[0032] If the interface display of the target locomotive is abnormal, it is determined that the concurrent protection of the target locomotive is abnormal.

[0033] In addition, to achieve the above purpose, the present invention also proposes an Android interface concurrent testing device, the Android interface concurrent testing device comprising:

[0034] A determination module, used to obtain various Android interfaces of the target vehicle computer, and determine the corresponding interface type according to the various Android interfaces;

[0035] A generation module, used for generating a target test thread set according to each preset application program and preset thread pool;

[0036] An extraction module, used to extract each test thread in the target test thread set;

[0037] The concurrent testing module is used to perform concurrent testing on each Android interface through each test thread and the interface type to obtain corresponding test results.

[0038] In addition, to achieve the above-mentioned purpose, the present invention also proposes an Android interface concurrent testing device, which includes: a memory, a processor, and an Android interface concurrent testing program stored in the memory and executable on the processor, and the Android interface concurrent testing program is configured to implement the Android interface concurrent testing method as described above.

[0039] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which an Android interface concurrent testing program is stored. When the Android interface concurrent testing program is executed by a processor, the Android interface concurrent testing method as described above is implemented.

[0040] The Android interface concurrent testing method proposed in the present invention obtains each Android interface of the target vehicle computer, determines the corresponding interface type according to each Android interface; generates a target test thread set according to each preset application and a preset thread pool; extracts each test thread in the target test thread set; concurrently tests each Android interface through each test thread and the interface type to obtain corresponding test results; since the present invention generates each test thread in the target test thread set and the interface type of the target vehicle computer through each preset application and a preset thread pool to concurrently test each Android interface to obtain corresponding test results, compared with the prior art of manually clicking on the application or using automated tools to test the Android interfaces one by one, it can quickly and effectively simulate large-scale concurrent interface call testing, and effectively improve the accuracy and efficiency of the test. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a structural diagram of an Android interface concurrent testing device of a hardware operating environment involved in an embodiment of the present invention;

[0042] Figure 2 This is a flow chart of the first embodiment of the Android interface concurrent testing method of the present invention;

[0043] Figure 3 This is a flow chart of a second embodiment of the Android interface concurrent testing method of the present invention;

[0044] Figure 4 A flowchart of a third embodiment of the concurrent testing method for an Android interface according to the present invention;

[0045] Figure 5 This is a schematic diagram of the functional modules of the first embodiment of the Android interface concurrent testing device of the present invention.

[0046] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0048] Reference Figure 1 , Figure 1 This is a schematic diagram of the structure of an Android interface concurrent testing device in the hardware operating environment involved in an embodiment of the present invention.

[0049] like Figure 1As shown, the Android interface concurrent testing device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0050] Those skilled in the art will understand that Figure 1 The structure shown in does not constitute a limitation on the Android interface concurrent testing device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0051] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and an Android interface concurrent testing program.

[0052] exist Figure 1 In the Android interface concurrent testing device shown, the network interface 1004 is mainly used for data communication with the network integration platform workstation; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the Android interface concurrent testing device of the present invention can be set in the Android interface concurrent testing device, and the Android interface concurrent testing device calls the Android interface concurrent testing program stored in the memory 1005 through the processor 1001, and executes the Android interface concurrent testing method provided by the embodiment of the present invention.

[0053] Based on the above hardware structure, an embodiment of the Android interface concurrent testing method of the present invention is proposed.

[0054] Reference Figure 2 , Figure 2 This is a flow chart of the first embodiment of the Android interface concurrent testing method of the present invention.

[0055] In a first embodiment, the Android interface concurrent testing method comprises the following steps:

[0056] Step S10, obtaining each Android interface of the target vehicle computer, and determining the corresponding interface type according to each Android interface.

[0057] It should be noted that the executor of this embodiment is an Android interface concurrent testing device, and may also be other devices that can achieve the same or similar functions, such as an Android interface tester, etc. This embodiment does not limit this. In this embodiment, the Android interface tester is taken as an example for explanation.

[0058] It should be understood that each Android interface refers to the Android interface called when the application in the target vehicle is running, such as the pop-up interface, the player interface, and the sound setting interface, etc. The interface type refers to the type to which each Android interface belongs, for example, each Android interface may include a sound setting interface, a system setting interface, a headlight interface, a turn signal interface, a door interface, a back door interface, and a seat belt interface. The sound setting interface and the system setting interface belong to the setting interface type, the headlight interface and the turn signal interface belong to the light interface, and the door interface, the back door interface, and the seat belt interface belong to the door and seat belt interface.

[0059] Step S20, generating a target test thread set according to each preset application program and preset thread pool.

[0060] It should be understood that each preset application refers to an application that can run normally in the target vehicle computer, such as music, radio, children's stories, maps, and voice, and the preset thread pool refers to a thread pool that can simulate the same functions as the preset applications. The preset thread pool can be an Android ThreadPoolExecutor thread pool or other thread pools. This embodiment does not limit this and takes the Android ThreadPoolExecutor thread pool as an example for illustration.

[0061] Furthermore, step S20 includes: obtaining corresponding program running information according to each preset application program; simulating the program running information through a preset thread pool; and generating a target test thread set according to the simulation result.

[0062] It can be understood that the program running information refers to the information when each preset application is running normally in the target vehicle computer. For example, when the preset application is music, the program running information is startup, song selection, volume adjustment, seat comfort adjustment, lighting adjustment, etc. After obtaining the program running information, the program running information is simulated by the threads in the preset thread pool, that is, the corresponding test thread is obtained. The test thread is consistent with the process of the Android interface called by the preset application. The target test thread set refers to the set of test threads simulated by each preset application. Simulating program running information specifically simulates multiple preset applications concurrently and randomly accessing each Android interface.

[0063] Step S30, extracting each test thread in the target test thread set.

[0064] It should be understood that after obtaining the target test thread set, each test thread in the target test thread set is extracted. For example, the target test thread set includes a music test thread, a map test thread, and a radio test thread.

[0065] Step S40, concurrently testing the Android interfaces through the test threads and the interface types to obtain corresponding test results.

[0066] It can be understood that concurrent testing refers to testing each Android interface at the same time. For example, each Android interface includes a sound setting interface, a system setting interface, and a headlight interface. The sound setting interface, the system setting interface, and the headlight interface are tested concurrently through the corresponding test threads. Concurrent testing is performed specifically according to the interface type to which each Android interface belongs. The choice of interface type is determined by the user scenario and the business scenario. The interfaces in the interface type are tested sequentially in the order of execution. After multiple threads execute the above test steps in a random sequence, large-scale concurrent random testing is achieved.

[0067] Furthermore, after step S40, it also includes: extracting the test return value and test log in the test results; determining whether the test return value is within the target range and / or whether abnormal information appears in the test log; if the test return value is not within the target range and / or abnormal information appears in the test log, determining that the concurrent protection of the target locomotive is abnormal.

[0068] It should be understood that the test return value refers to the value returned at the end of the test of each Android interface, the test log refers to the log generated during the test of each Android interface, and the target range refers to the normal value of the test range of each Android interface. For example, the tested Android interface is the sound setting interface, and the target range of the sound setting interface is AB. If the corresponding test return value is C, and C is not between AB, it indicates that the concurrent protection of the target locomotive is abnormal. The abnormal information refers to the abnormal information in the test log. If abnormal information appears in the test log, it indicates that the concurrent protection of the target locomotive is abnormal, that is, the test return value is not within the target range and the abnormal information appears in the test log. Satisfy one condition to determine the concurrent protection abnormality of the target vehicle.

[0069] Furthermore, after determining whether the test return value is within the target range and / or whether abnormal information appears in the test log, it also includes: if the test return value is within the target range and / or no abnormal information appears in the test log, determining whether the interface of the target vehicle computer displays an abnormality during the operation of each preset application; if the interface of the target vehicle computer displays an abnormality, determining that the concurrency protection of the target vehicle computer is abnormal.

[0070] It can be understood that if the test return value is within the target range and there is no abnormal information in the test log, that is, both conditions are met, then it is determined whether the display of the target vehicle is abnormal. The display abnormality includes black screen, freeze, and no response. If the display is abnormal, the concurrent protection of the target locomotive is abnormal. Otherwise, the concurrent protection of the target locomotive is normal.

[0071] This embodiment obtains each Android interface of the target vehicle computer, determines the corresponding interface type according to each Android interface; generates a target test thread set according to each preset application and a preset thread pool; extracts each test thread in the target test thread set; concurrently tests each Android interface through each test thread and the interface type to obtain corresponding test results; since this embodiment concurrently tests each Android interface through each test thread in the target test thread set generated by each preset application and a preset thread pool and the interface type of the target vehicle computer to obtain corresponding test results, compared with the prior art of manually clicking on the application or using automated tools to test the Android interfaces one by one, it can quickly and effectively simulate large-scale concurrent interface call testing, and effectively improve the accuracy and efficiency of the test.

[0072] In one embodiment, if Figure 3 Based on the first embodiment, a second embodiment of the Android interface concurrent testing method of the present invention is proposed, and step S10 includes:

[0073] Step S101, obtaining each Android interface of the target vehicle computer, and extracting identification information of each Android interface.

[0074] It should be understood that each Android interface refers to the Android interface called when the application in the target vehicle computer is running, and the identification information refers to the information that can uniquely identify each Android interface. For example, the identification information of the sound setting interface and the system setting interface is setting, and the application will call the sound setting interface or the system setting interface during the setting process.

[0075] Step S102: classify the Android interfaces according to the identification information.

[0076] It is understandable that after obtaining the identification information of each Android interface, each Android interface is classified according to the identification information, that is, divided into corresponding groups. The division method can be based on the function of the interface or other division standards of the interface. This embodiment does not limit this. It is explained by taking the division by the function of the interface as an example. For example, each Android interface can include a sound setting interface, a system setting interface, a headlight interface, a turn signal interface, a door interface, a back door interface, and a seat belt interface. The sound setting interface and the system setting interface belong to the setting interface type, the headlight interface and the turn signal interface belong to the light interface, and the door interface, the back door interface, and the seat belt interface belong to the door and seat belt interface.

[0077] Step S103: determine the corresponding interface type according to the classification result.

[0078] It should be understood that after each Android interface is classified, the interface type of each Android interface is determined according to the classification result. For example, the sound setting interface and the system setting interface belong to the setting interface type, the headlight interface and the turn indicator interface belong to the light interface, and the door interface, the back door interface, and the seat belt interface belong to the door and seat belt interface.

[0079] This embodiment obtains each Android interface of the target vehicle computer and extracts the identification information of each Android interface; classifies each Android interface according to the identification information; determines the corresponding interface type according to the classification result; classifies each Android interface of the target vehicle computer according to the identification information, and determines the interface type corresponding to each Android interface according to the classification result, thereby effectively improving the efficiency of concurrent testing of each Android interface.

[0080] In one embodiment, if Figure 4 Based on the first embodiment, a third embodiment of the Android interface concurrent testing method of the present invention is proposed, and step S40 includes:

[0081] Step S401, obtaining the execution order of the Android interfaces according to the interface type.

[0082] It can be understood that the execution order refers to the order in which each test thread tests each Android interface. For example, there are 5 Android interfaces in the interface type, and the test order of the 5 Android interfaces is A, C, E, B and D, then this test order is the execution order.

[0083] Step S402, concurrently testing the Android interfaces through the test threads and the execution order to obtain corresponding test results.

[0084] It can be understood that after obtaining the execution order, each Android interface is concurrently tested through each test thread and execution order to obtain the corresponding test results. The concurrent test in the interface type needs to be tested according to the execution order, and the concurrent test of the Android interface corresponding to the interface type is random.

[0085] Further, step S402 includes: obtaining a preset random strategy, generating a target random number according to the preset random strategy; determining the initial Android interface and the non-initial Android interface according to the target random number and the Android interfaces; performing concurrent testing on the initial Android interface and the non-initial Android interface through each test thread and the execution order to obtain corresponding test results, specifically, in the main controller (CPU) of the tested device, the operation of each thread running time slice is random; using this randomness, the above-mentioned concurrent test also has randomness, which can simulate the actual operation state of multiple applications concurrently accessing the interface.

[0086] It should be understood that the preset random strategy refers to a strategy for generating random numbers, that is, the generated target random number is uncertain, that is, the initial Android interface and the non-initial Android interface obtained according to the target random number and each Android interface are also uncertain. For example, the classified interface types are X, Y and Z, and the target random number generated for the first time by the preset random strategy is 2, and the corresponding type is Y, that is, the initial Android interface is Y, and the non-initial Android interfaces are X and Z. Through each test thread and execution order, Y is first concurrently tested; then X is concurrently tested; finally, Z is concurrently tested to obtain the corresponding test results.

[0087] This embodiment obtains the execution order of each Android interface according to the interface type; concurrently tests each Android interface through each test thread and the execution order to obtain corresponding test results; because this implementation concurrently tests each Android interface through the execution order obtained by each test thread and the interface type, thereby effectively improving the accuracy of concurrent testing of Android interfaces.

[0088] In addition, an embodiment of the present invention further proposes a storage medium, on which an Android interface concurrent testing program is stored. When the Android interface concurrent testing program is executed by a processor, the steps of the Android interface concurrent testing method described above are implemented.

[0089] Since the storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0090] In addition, refer to Figure 5 The embodiment of the present invention further provides an Android interface concurrent testing device, the Android interface concurrent testing device comprising:

[0091] The determination module 10 is used to obtain various Android interfaces of the target vehicle computer and determine the corresponding interface type according to the various Android interfaces.

[0092] It should be understood that each Android interface refers to the Android interface called when the application in the target vehicle is running, such as the pop-up interface, the player interface, and the sound setting interface, etc. The interface type refers to the type to which each Android interface belongs, for example, each Android interface may include a sound setting interface, a system setting interface, a headlight interface, a turn signal interface, a door interface, a back door interface, and a seat belt interface. The sound setting interface and the system setting interface belong to the setting interface type, the headlight interface and the turn signal interface belong to the light interface, and the door interface, the back door interface, and the seat belt interface belong to the door and seat belt interface.

[0093] The generating module 20 is used to generate a target test thread set according to each preset application program and a preset thread pool.

[0094] It should be understood that each preset application refers to an application that can run normally in the target vehicle computer, such as music, radio, children's stories, maps, and voice, and the preset thread pool refers to a thread pool that can simulate the same functions as the preset applications. The preset thread pool can be an Android ThreadPoolExecutor thread pool or other thread pools. This embodiment does not limit this and takes the Android ThreadPoolExecutor thread pool as an example for illustration.

[0095] Furthermore, the generating module 20 is also used to obtain corresponding program running information according to each preset application program; simulate the program running information through a preset thread pool; and generate a target test thread set according to the simulation result.

[0096] It can be understood that the program running information refers to the information when each preset application is running normally in the target vehicle computer. For example, when the preset application is music, the program running information is startup, song selection, volume adjustment, seat comfort adjustment, lighting adjustment, etc. After obtaining the program running information, the program running information is simulated by the threads in the preset thread pool, that is, the corresponding test thread is obtained. The test thread is consistent with the process of the Android interface called by the preset application. The target test thread set refers to the set of test threads simulated by each preset application. The simulation of program running information specifically simulates multiple preset applications concurrently and randomly accessing each Android interface.

[0097] The extraction module 30 is used to extract each test thread in the target test thread set.

[0098] It should be understood that after obtaining the target test thread set, each test thread in the target test thread set is extracted. For example, the target test thread set includes a music test thread, a map test thread, and a radio test thread.

[0099] The concurrent testing module 40 is used to perform concurrent testing on the Android interfaces through the test threads and the interface types to obtain corresponding test results.

[0100] It can be understood that concurrent testing refers to testing each Android interface at the same time. For example, each Android interface includes a sound setting interface, a system setting interface, and a headlight interface. The sound setting interface, the system setting interface, and the headlight interface are concurrently tested through the corresponding test threads. Concurrent testing is performed specifically according to the interface type to which each Android interface belongs. The choice of interface type is determined by the user scenario and the business scenario. The interfaces in the interface type are tested sequentially in the order of execution. After multiple threads execute the above test steps in a random sequence, large-scale concurrent random testing is achieved.

[0101] Furthermore, the concurrent test module 40 is also used to extract the test return value and test log in the test results; determine whether the test return value is within the target range and / or whether abnormal information appears in the test log; if the test return value is not within the target range and / or abnormal information appears in the test log, it is determined that the concurrent protection of the target locomotive is abnormal.

[0102] It should be understood that the test return value refers to the value returned at the end of the test of each Android interface, the test log refers to the log generated during the test of each Android interface, and the target range refers to the normal value of the test range of each Android interface. For example, the tested Android interface is the sound setting interface, and the target range of the sound setting interface is AB. If the corresponding test return value is C, and C is not between AB, it indicates that the concurrent protection of the target locomotive is abnormal. The abnormal information refers to the abnormal information in the test log. If abnormal information appears in the test log, it indicates that the concurrent protection of the target locomotive is abnormal, that is, the test return value is not within the target range and the abnormal information appears in the test log. Satisfy one condition to determine the concurrent protection abnormality of the target vehicle.

[0103] Furthermore, after determining whether the test return value is within the target range and / or whether abnormal information appears in the test log, it also includes: if the test return value is within the target range and / or no abnormal information appears in the test log, determining whether the interface of the target vehicle computer displays an abnormality during the operation of each preset application; if the interface of the target vehicle computer displays an abnormality, determining that the concurrency protection of the target vehicle computer is abnormal.

[0104] It can be understood that if the test return value is within the target range and there is no abnormal information in the test log, that is, both conditions are met, then it is determined whether the display of the target vehicle is abnormal. The display abnormality includes black screen, freeze, and no response. If the display is abnormal, the concurrent protection of the target locomotive is abnormal. Otherwise, the concurrent protection of the target locomotive is normal.

[0105] This embodiment obtains each Android interface of the target vehicle computer, determines the corresponding interface type according to each Android interface; generates a target test thread set according to each preset application and a preset thread pool; extracts each test thread in the target test thread set; concurrently tests each Android interface through each test thread and the interface type to obtain corresponding test results; since this embodiment concurrently tests each Android interface through each test thread in the target test thread set generated by each preset application and a preset thread pool and the interface type of the target vehicle computer to obtain corresponding test results, compared with the prior art of manually clicking on the application or using automated tools to test the Android interfaces one by one, it can quickly and effectively simulate large-scale concurrent interface call testing, and effectively improve the accuracy and efficiency of the test.

[0106] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of them according to actual needs to achieve the purpose of the present embodiment, and no limitation is made here.

[0107] In addition, for technical details not fully described in this embodiment, please refer to the Android interface concurrent testing method provided in any embodiment of the present invention, and will not be repeated here.

[0108] In one embodiment, the determination module 10 is further used to obtain each Android interface of the target vehicle computer, extract identification information of each Android interface; classify each Android interface according to the identification information; and determine the corresponding interface type according to the classification result.

[0109] In one embodiment, the generation module 20 is further used to obtain corresponding program running information according to each preset application program; simulate the program running information through a preset thread pool; and generate a target test thread set according to the simulation result.

[0110] In one embodiment, the concurrent testing module 40 is further used to obtain the execution order of the Android interfaces according to the interface type; and concurrently test the Android interfaces through the test threads and the execution order to obtain corresponding test results.

[0111] In one embodiment, the concurrent testing module 40 is also used to obtain a preset random strategy, generate a target random number according to the preset random strategy; determine the initial Android interface and the non-initial Android interface according to the target random number and the Android interfaces; perform concurrent testing on the initial Android interface and the non-initial Android interface through each test thread and the execution order to obtain corresponding test results.

[0112] In one embodiment, the concurrent test module 40 is also used to extract the test return value and test log in the test results; determine whether the test return value is within the target range and / or whether abnormal information appears in the test log; if the test return value is not within the target range and / or abnormal information appears in the test log, it is determined that the concurrent protection of the target locomotive is abnormal.

[0113] In one embodiment, the concurrent test module 40 is further used to determine whether the interface of the target vehicle computer displays an abnormality during the operation of each preset application if the test return value is within the target range and / or the test log does not contain abnormal information; if the interface of the target vehicle computer displays an abnormality, it is determined that the concurrency protection of the target vehicle computer is abnormal.

[0114] Other embodiments or implementation methods of the Android interface concurrent testing device described in the present invention can refer to the above-mentioned method embodiments, which are not repeated here.

[0115] In addition, it should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0116] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0117] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, an integrated platform workstation, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0118] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A concurrent testing method for Android interfaces. It is characterized in that The Android interface concurrent testing method comprises the following steps: Obtain each Android interface of the target vehicle computer, and determine the corresponding interface type according to each Android interface; Generate a target test thread set according to each preset application and preset thread pool, wherein each preset application refers to an application that can run normally in the target vehicle computer, and the preset thread pool refers to a thread pool that can simulate the same function as each preset application; Extracting each test thread in the target test thread set, wherein each test thread is obtained by simulating program running information by each thread in a preset thread pool; Obtaining an execution order of the Android interfaces according to the interface type; The Android interfaces are tested concurrently through the test threads and the execution order to obtain corresponding test results; wherein the Android interfaces include initial Android interfaces and non-initial Android interfaces determined according to a target random number.

2. The Android interface concurrent testing method as claimed in claim 1, It is characterized in that The obtaining of each Android interface of the target vehicle computer and determining a corresponding interface type according to each Android interface includes: Obtain each Android interface of the target vehicle computer, and extract identification information of each Android interface; Classifying the Android interfaces according to the identification information; Determine the corresponding interface type based on the classification result.

3. The Android interface concurrent testing method as claimed in claim 1, It is characterized in that The generating of a target test thread set according to each preset application program and a preset thread pool includes: Obtain corresponding program running information according to each preset application program; Simulating the program running information through a preset thread pool; Generate a target test thread set based on the simulation results.

4. The Android interface concurrent testing method as claimed in claim 1, It is characterized in that The concurrent testing of the Android interfaces through the test threads and the execution order to obtain corresponding test results includes: Obtain a preset random strategy, and generate a target random number according to the preset random strategy; Determine an initial Android interface and a non-initial Android interface according to the target random number and the Android interfaces; The initial Android interface and the non-initial Android interface are tested concurrently by each test thread and the execution order to obtain corresponding test results.

5. The Android interface concurrent testing method according to any one of claims 1 to 4, It is characterized in that After the concurrent testing of the Android interfaces by the test threads and the interface types is performed to obtain corresponding test results, the method further includes: Extract the test return value and test log in the test results; Determine whether the test return value is within a target range and / or whether abnormal information appears in the test log; If the test return value is not within the target range and / or abnormal information appears in the test log, it is determined that the concurrent protection of the target locomotive is abnormal.

6. The Android interface concurrent testing method as claimed in claim 5, It is characterized in that The step of determining whether the test return value is within a target range and / or whether abnormal information appears in the test log further includes: If the test return value is within the target range and / or the test log does not contain abnormal information, determining whether the interface of the target vehicle computer displays abnormality during the operation of each preset application; If the interface display of the target locomotive is abnormal, it is determined that the concurrent protection of the target locomotive is abnormal.

7. An Android interface concurrent testing method and device, It is characterized in that The Android interface concurrent testing method device comprises: A determination module, used to obtain various Android interfaces of the target vehicle computer, and determine the corresponding interface type according to the various Android interfaces; A generation module, used to generate a target test thread set according to each preset application and a preset thread pool, wherein each preset application refers to an application that can run normally on the target vehicle computer, and the preset thread pool refers to a thread pool that can simulate the same function as the preset application; An extraction module, used for extracting each test thread in the target test thread set, wherein each test thread is obtained by simulating program running information by each thread in a preset thread pool; A concurrent testing module is used to obtain the execution order of each Android interface according to the interface type; concurrently test each Android interface through each test thread and the execution order to obtain corresponding test results; wherein each Android interface includes an initial Android interface and a non-initial Android interface determined according to a target random number.

8. An Android interface concurrent testing method and device, It is characterized in that The Android interface concurrent testing method device includes: a memory, a processor, and an Android interface concurrent testing method program stored in the memory and executable on the processor, wherein the Android interface concurrent testing method program is configured to implement the Android interface concurrent testing method as described in any one of claims 1 to 6.

9. A storage medium, It is characterized in that The storage medium stores an Android interface concurrent testing method program, which, when executed by a processor, implements the Android interface concurrent testing method as described in any one of claims 1 to 6.