CN111459798A - Test methods, devices, media and electronic equipment - Google Patents

Abstract

The present application relates to a testing method and a related device, belonging to the technical field of computers. The method includes: acquiring configuration information of test cases in a test case set used for a target test task; extracting test case configuration information from the test case configuration information Use case feature information; input the test case feature information into the pre-trained grouping model to obtain multiple test case groups; concurrently execute the test cases in the parallel-type test case group, and access the thread lock to lock the concurrent execution while running and the thread lock is released at the end of the running; when the execution of the test cases in the parallelizable test case group ends, the concurrent test result is obtained. The present application can improve test reliability and stability.

Description

Test methods, devices, media and electronic equipment

technical field

The present application relates to the field of computer technology, and in particular, to a testing method, apparatus, medium and electronic device.

Background technique

At present, there will be some false alarm rates during the execution process of the current test scripts. The false alarm rates are generally divided into two categories. One is force majeure factors, that is, network disconnection, power failure, system restart or failure to start normal operation. This type of situation in the test script is called environmental false positives. The probability of such errors occurring is extremely small. The second type is logical false positives, that is to say, logical errors in the verification process mentioned above lead to the verification results and the expected results. The results do not match. This type of error is often caused by not considering perfection when executing a test case. The application of multi-threaded control is unreliable, and logic errors are prone to occur. When the multi-threaded control test script is not completed, the previous test is triggered. A logic test causes script execution errors, and such false positives will have a serious impact on the stability of the test. Therefore, there are problems of low test reliability and test stability during testing at present.

SUMMARY OF THE INVENTION

The purpose of the present application is to provide a test solution, thereby improving test reliability and stability at least to a certain extent.

According to one aspect of the present application, a test method is provided, comprising:

Obtain the configuration information of the test case in the test case collection for the target test task;

Extract test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case;

Inputting the test case feature information into a pre-trained grouping model to obtain multiple test case groups;

Concurrently execute the test cases in the parallel test case group, and access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the operation;

When the execution of the test cases in the test case group of the parallelizable type ends, the concurrent test result is obtained.

In an exemplary embodiment of the present application, the training method of the grouping model includes:

Collect a sample set of test case feature information, where each sample in the sample set is pre-calibrated with the grouping label of the corresponding test case;

Input the samples in the sample set into the grouping model, and output the predicted grouping labels of the samples;

When the predicted grouping label is inconsistent with the pre-calibrated grouping label for the sample, adjust the coefficients of the grouping model until they are consistent;

When the grouping model is for the sample set, the predicted grouping labels of all the samples are consistent with the pre-calibrated grouping labels for the samples, and the training ends.

In an exemplary embodiment of the present application, the concurrent execution of the test cases in the test case group of the parallel type is performed, and the thread lock is used to lock the running test cases during the concurrent execution, and all the test cases are released at the end of the running. Thread locks described above, including:

Start the concurrent execution of the test cases in the parallel test case group, and access the first thread lock to lock the first test case to start running;

When the first start-running test case finishes running, release the first thread lock, and access the second thread lock to lock the second start-running test case;

When the second start-running test case finishes running, the second thread lock is released, and subsequent thread locks are alternately accessed and released to execute subsequent start-running test cases until the test is completed. test cases in the test case group.

In an exemplary embodiment of the present application, the extracting test case feature information from the configuration information of the test case includes:

Based on the preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain the test case feature information.

In an exemplary embodiment of the present application, based on a preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain the test case Use case characteristic information, including:

Obtain the preset attribute keyword corresponding to the use case type of each test case, the preset attribute keyword includes a general attribute keyword and a special attribute keyword, the general attribute keyword corresponds to all test cases, and the The dedicated attribute keywords described above correspond to each use case type;

According to the dedicated attribute keyword and the general attribute keyword corresponding to each test case, test case attribute information is extracted from the configuration information of each test case to obtain the test case feature information.

In an exemplary embodiment of the present application, the multiple test case groups further include test case groups whose test cases need to be serialized, and the method further includes:

Serially execute the test cases in the test case group to be serialized until all the test cases are executed;

When the execution of the test cases in the test case group to be serialized ends, the serial test result is obtained;

The concurrent test result and the serial test result are taken as the total test result.

In an exemplary embodiment of the present application, the test case groups to be serialized are arranged into groups in a serial order, and the serial execution of the test cases in the test case group to be serialized includes:

According to the serial order of the test cases in the test case group to be serialized, the test cases in the test case group to be serialized are executed serially.

According to one aspect of the present application, a testing device is provided, characterized in that it includes:

The acquisition module is used to acquire the configuration information of the test cases in the test case set used for the target test task;

an extraction module, configured to extract test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case;

a grouping module for inputting the test case feature information into a pre-trained grouping model to obtain multiple test case groups;

A concurrency module, used for concurrently executing the test cases in the parallel-type test case group, and accessing the thread lock to lock the running test case during concurrent execution, and releasing the thread lock at the end of the operation;

The concurrency ending module is used to obtain the concurrent test result when the execution of the test cases in the test case group of the parallelizable type ends.

According to an aspect of the present application, there is provided a computer-readable storage medium on which program instructions are stored, characterized in that, when the program instructions are executed by a processor, any one of the methods described above is implemented.

According to one aspect of the present application, an electronic device is provided, characterized in that it includes:

processor; and

a memory for storing program instructions of the processor; wherein the processor is configured to perform any of the methods described above by executing the program instructions.

The present application provides a testing method and related device. First, the configuration information of test cases in the test case set used for the target test task is obtained; the test case related information describing the configuration of the target test task can be obtained. Then, the test case feature information is extracted from the configuration information of the test case, and the test case feature information is the key attribute feature of the execution strategy of each test case; Potential relationships between use cases that enforce the policy and key characteristics of the use cases. Then, input the test case feature information into the pre-trained grouping model to obtain multiple test case groups; based on the test case feature information based on the grouping model, the test case groups that can be parallelized by the test cases can be analyzed, and then the efficient concurrency of test cases can be carried out. implement. Further, concurrently execute the test cases in the parallel test case group, and access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the running test case; When a test case is executed, access the thread lock to lock the thread, release the thread lock at the end, and access the next thread lock until the end of the test, to ensure the high concurrency process, and all tests to be carried out in an orderly and reliable manner. Finally, when the execution of the test cases in the parallel test case group ends, the concurrent test results are obtained, which effectively improves the test reliability and stability.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not limiting of the present application.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application. Obviously, the drawings in the following description are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 schematically shows a flow chart of a testing method.

FIG. 2 schematically shows an example diagram of an application scenario of a testing method.

FIG. 3 schematically shows a flow chart of a method for concurrent execution.

FIG. 4 schematically shows a block diagram of a testing device.

FIG. 5 schematically shows a block diagram of an example of an electronic device for implementing the above-mentioned testing method.

FIG. 6 schematically shows a computer-readable storage medium for implementing the above-mentioned testing method.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments, however, can be embodied in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided in order to give a thorough understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical solutions of the present application may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be employed. In other instances, well-known solutions have not been shown or described in detail to avoid obscuring aspects of the application.

Furthermore, the drawings are merely schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repeated descriptions will be omitted. Some of the block diagrams shown in the figures are functional entities that do not necessarily necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

In the embodiment of the present application, a test method is provided first, and the test method can be run on a server, a server cluster or a cloud server, etc. Of course, those skilled in the art can also run the method of the present application on other platforms as required. This is not particularly limited in the exemplary embodiment. Referring to Figure 1, the test method may include the following steps:

Step S110, obtaining configuration information of test cases in the test case set used for the target test task;

Step S120, extracting test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case;

Step S130, inputting the test case feature information into a pre-trained grouping model to obtain multiple test case groups;

Step S140, concurrently execute the test cases in the parallel-type test case group, and access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the operation;

Step S150, when the execution of the test cases in the test case group of the parallel type is completed, a concurrent test result is obtained.

First, the configuration information of the test case in the test case set used for the target test task is obtained; the test case related information describing the configuration for the target test task can be obtained. Then, the test case feature information is extracted from the configuration information of the test case, and the test case feature information is the key attribute feature of the execution strategy of each test case; Potential relationships between use cases that enforce the policy and key characteristics of the use cases. Then, input the test case feature information into the pre-trained grouping model to obtain multiple test case groups; based on the test case feature information based on the grouping model, the test case groups that can be parallelized by the test cases can be analyzed, and then the efficient concurrency of test cases can be carried out. implement. Further, concurrently execute the test cases in the parallel test case group, and access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the running test case; When a test case is executed, access the thread lock to lock the thread, release the thread lock at the end, and access the next thread lock until the end of the test, to ensure the high concurrency process, and all tests to be carried out in an orderly and reliable manner. Finally, when the execution of the test cases in the parallel test case group ends, the concurrent test results are obtained, which effectively improves the test reliability and stability.

Hereinafter, each step in the above-mentioned concurrent testing method in this exemplary embodiment will be explained and described in detail with reference to the accompanying drawings.

In step S110, the configuration information of the test cases in the test case set for the target test task is acquired.

In the implementation of this example, referring to FIG. 2 , the server 201 uses the configuration information of the test case in the test case set of the target test task from the user terminal 202 . In this way, in the subsequent steps, the server 201 can carry out the formulation and testing of the test strategy according to the configuration information of the test case. It can be understood that the server 201 can be any device with processing capabilities, such as a computer, a microprocessor, etc., which is not particularly limited here; the user terminal 202 can be any terminal with an information input function.

A test case can be a set of test inputs, execution conditions, and expected results prepared for a particular goal in order to test a program path or verify that a particular requirement is met.

The configuration information of the test case is the case-related information of the configuration configured for each test case, and can include the elements of each test case: the title of the test case, the test idea, the preset conditions, the test steps, the expected output, the name of the software or project , the software or project version (internal version number), the dependencies between this test case and other test cases, etc.

Usually, a test task will include a set of test cases of multiple test cases, such as a set of 1000 test cases, and these test cases may have a logical calling relationship (for example, when method A runs, one of the variables has a value of B The dynamic output value of the method. In this way, method B must be executed first. Other test cases can be independent of each other without calling relationship.

The test case set corresponding to the task identifier of the target test task and the configuration information of each test case can be obtained through the task identifier of the target test task. The configuration information of the test case of the target test task can be configured by the developer in advance.

In this way, the relevant information of the test case describing the configuration for the target test task can be obtained, and then the analysis and formulation of the test strategy can be performed based on the configuration information in the subsequent steps.

In step S120, test case feature information is extracted from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case.

In the implementation of this example, the key attribute characteristics of the execution strategy of each test case, that is, the test case characteristic information, may be the key information reflecting the execution strategy in the test case configuration information, and these key information may be corresponding to multiple key information. element information. For example, key elements can be test ideas, preset conditions, test steps, expected output, and dependencies between this test case and other test cases, etc. Key attribute features can be attribute information corresponding to these key attributes, which can be directly passed through the preset Key elements, the information corresponding to the key elements is directly used as the use case feature information, which can completely contain the key attribute characteristics of the execution strategy of each test case.

The content of each test case element can be configured in the configuration information according to the comparison relationship between attributes and attribute information in advance, and then the key attribute features in each test case element can be determined by preset attribute keywords.

By extracting the key attribute features of the execution strategy of each test case, the potential relationship between the use cases and the key features of the use cases that reflect the execution strategy of the use case can be obtained.

In one of the embodiments, the extracting test case feature information from the configuration information of the test case includes:

Based on the preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain the test case feature information.

The preset attribute keywords may be test element names (eg, test ideas, preset conditions, test steps, expected outputs, and dependencies, etc.) in the preset multiple test case configuration information. It can also be the content attribute in the content of each test element. For example, for the test idea element, the content can be: abnormal condition 1 - after the storage space is full, abnormal condition 2 - run the program that occupies the space, test purpose - the terminal is in Whether an exception will occur in the case of storage overflow, the content attribute keywords in the content of the test idea elements are abnormal condition 1, abnormal condition 2, and test purpose. Furthermore, according to the preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword can be extracted from the configuration information of the test case to obtain the test case characteristic information.

In one embodiment, based on a preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain the test case feature information, include:

Obtain the preset attribute keyword corresponding to the use case type of each test case, the preset attribute keyword includes a general attribute keyword and a special attribute keyword, the general attribute keyword corresponds to all test cases, and the The dedicated attribute keywords described above correspond to each use case type;

According to the dedicated attribute keyword and the general attribute keyword corresponding to each test case, test case attribute information is extracted from the configuration information of each test case to obtain the test case feature information.

The use case type of each test case, such as: functional test, usability test, installability test, exception test, stress test, GUI test, compatibility test, security test, reliability test, etc.

The use case types of test cases are different, and the configuration information such as the test idea is adapted to the use case type. By obtaining the preset attribute keywords corresponding to the use case type of each test case, the characteristic information of each test case can be accurately obtained.

Among them, the preset attribute keywords include general attribute keywords and special attribute keywords. The general attribute keywords correspond to all test cases, that is, the general attribute keywords are applicable to all test case configuration information, and the test case information can be obtained. Keywords corresponding to common attributes, such as test purpose, etc. The dedicated attribute keyword corresponds to the configuration information of each use case type, and corresponds to the type of the test case. For example, for a test case of an exception test, the dedicated attribute keyword can be exception condition 1, exception condition 2, and so on. In this way, the characteristic information of the test case can be completely obtained through the general attribute keyword and the special attribute keyword.

In step S130, the test case feature information is input into a pre-trained grouping model to obtain multiple test case groups.

In the implementation of this example, the pre-trained grouping model is based on the test case feature information of a large number of test cases as input, and the group label to which each test case belongs is used as output. grouping. In one embodiment, the number of test cases in each test case group is less than a predetermined threshold.

This group of tags can include parallel tags and total tags requiring serial tags; the parallel tags can also include parallel tags 1, parallel tags 2 and other sub tags, and serial tags can also include serial tags 1 , Sub-tags such as serial tag 2 are required.

The test cases pointed to by the parallelizable tag can be parallelized, and each subtag of the parallelizable tag can correspond to multiple test cases, that is, each subtag can correspond to a test case group, and the use cases in each parallelizable test case group are together. During concurrent execution, based on the potential relationship between each use case and the key characteristics of the use case in the use case execution strategy of each use case, the use case grouping is more reasonable, and the test case can effectively improve the test efficiency during execution. Conduct robustness tests.

Generally, an efficient test script needs to complete thousands of test cases in one hour. The time spent on one test case is 1-2 minutes, and 1000 test cases are executed. If the serial method is 1000*(1-2) about It takes more than a day. Furthermore, through the parallel method: running 1000 test cases in 1 hour, about 16 test cases need to be completed in one minute of parallel tasks, which can effectively save time and improve efficiency.

At the same time, for some special scenarios, for example, test case 2 can only be run after test case 1 is completed, so that the test method can only be used in serial mode. Through grouping, for example, 1000 items are dynamically divided into 100 groups. In the subsequent steps, the test cases in the parallel groups of the 100 groups can be executed in parallel, and the test cases that need to be serialized can be executed serially.

Based on the grouping model, the test case group can be accurately and reasonably divided into multiple groups by using the test case feature information, including multiple parallel test case groups, and then each parallel test case group in the subsequent steps can be realized. Concurrent testing ensures the efficiency, reliability and stability of test case execution in subsequent steps, and at the same time, through the reasonable grouping of models, it ensures that thread locks are added in concurrent execution in subsequent steps (concurrent execution of test cases in parallel test case groups) Addition of thread locks in ) reliability.

In one embodiment, the training method of the grouping model includes:

Collect a sample set of test case feature information, where each sample in the sample set is pre-calibrated with the grouping label of the corresponding test case;

Input the samples in the sample set into the grouping model, and output the predicted grouping labels of the samples;

When the predicted grouping label is inconsistent with the pre-calibrated grouping label for the sample, adjust the coefficients of the grouping model until they are consistent;

When the grouping model is for the sample set, the predicted grouping labels of all the samples are consistent with the pre-calibrated grouping labels for the samples, and the training ends.

In the test case feature information sample set, each sample has been demarcated by experts in advance according to the combined experience between test cases and the corresponding test case grouping labels, and then, by inputting the test case feature information samples into the grouping model, the training model outputs corresponding The sample implements the label of the calibration, and the label can be represented by a string or a numerical code. When the grouping model is aimed at the sample set, the predicted grouping labels of all the samples are consistent with the pre-calibrated grouping labels for the samples, and the training ends. In this way, the analysis output grouping labels of the latent features of various use cases reflected by the feature information of the test cases can be obtained by training.

In step S140, concurrently execute the test cases in the parallelizable test case group, access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the running.

In the implementation of this example, the concurrent execution of the test case group is to use multiple threads to execute multiple test cases concurrently, thereby effectively improving the test speed.

When high-concurrency tests are executed out of order and in parallel, only a single environment, such as a scenario test, can be tested. It cannot be done for multi-scenario testing, because high concurrency uses the disordered arrangement of threads, that is, whichever thread preempts the resource will be mounted, which will lead to a certain probability of deadlock, and this kind of problem will cause false positives. . By arranging the unordered threads into the thread pool, dynamically grouping them based on the grouping model, obtaining multiple parallel test case groups, executing the test cases in parallel, and further locking the running test cases by thread locks. , you can release the thread lock after the execution ends, release the thread lock at the end of each test case execution, and access the next lock until the concurrent test of the test case group ends, effectively ensuring the test case in the concurrent process. orderliness. This ensures that resources can be released after each test case thread is completed, and will not cause problems such as false positives.

In one of the embodiments, as shown in FIG. 3 , the concurrent execution of the test cases in the test case group of the parallel type is performed, and the thread lock is used to lock the running test cases during concurrent execution, and when the execution ends Release the thread lock, including:

Step S310, start the concurrent execution of the test cases in the test case group of the parallel type, and access the first thread lock to lock the first start-running test case;

Step S320, when the first test case that starts to run ends, releases the first thread lock, and accesses the second thread lock to lock the second test case that starts to run;

Step S330, when the second test case started to run ends, the second thread lock is released, and subsequent thread locks are alternately accessed and released to execute subsequent test cases that are started and run until the test is completed. Describe the test cases in the parallelizable test case group.

For example, when a set of 7 test cases is not serial, use thread lock to lock the running test case, and then continue to access the second thread lock through the process of releasing the lock after completion of execution, so that the test case and the There will not be a false positive bug due to mutual exclusion between use cases, and it can also save testing time during execution and ensure the quality of testing. Especially for test cases with very complex business logic, it can effectively ensure the authenticity of test results and test efficiency. Likewise, parallel testing is possible for test cases that do not require business logic.

In step S150, when the execution of the test cases in the test case group of the parallel type is completed, a concurrent test result is obtained.

In the implementation of this example, when the parallelizable test case group can cover all test cases, when the execution of the test cases in the parallelizable test case group ends, the concurrent test result is obtained, that is, the final test result corresponding to the current target test task . In this way, by obtaining the concurrent test result when the execution of the test case in the parallelizable test case group ends, the test result of the test task can be obtained efficiently, accurately and stably.

If the model grouping result includes other test case groups in addition to parallel test case groups, for example, serial test case groups, the concurrent test result is a partial result of the test task test result. In this way, the concurrent test results are obtained at the end of the execution of the test cases in the parallel test case group, so that the test results of this part of the test task can be obtained as efficiently, accurately and stably as possible, thereby ensuring the overall efficiency, accuracy and stability of the test. .

In one embodiment, the multiple test case groups further include test case groups whose test cases need to be serialized, and the method further includes:

Serially execute the test cases in the test case group to be serialized until all the test cases are executed;

When the execution of the test cases in the test case group to be serialized ends, the serial test result is obtained;

The concurrent test result and the serial test result are taken as the total test result.

The test case pointed to by the serial tag needs to be serialized, and the result of the previous test case needs to be used by the next test case after the execution of the test case. However, each sub-tag of the serial tag can correspond to multiple test cases, that is, each sub-tag can correspond to a test case group, and the use cases in each test case group are executed serially during execution. In an example, the test cases in a test case group that needs to be serialized do not absolutely need to be serialized, but can be reflected by the potential relationship between the use cases and the key characteristics of the use cases through the use case execution strategy of each use case. Multiple test cases that can effectively improve test stability when the test cases are executed serially form a group.

Taking the concurrent test results and serial test results as the total test results, the test can be completed completely and reliably, and the test results can be obtained.

In one embodiment, the test case groups to be serialized are arranged into groups in a serial order, and the serial execution of the test cases in the test case group to be serialized includes:

According to the serial order of the test cases in the test case group to be serialized, the test cases in the test case group to be serialized are executed serially.

Through the grouping model, adding group labels and label serial numbers to the test cases that need to be serialized according to the characteristics of the calling relationship of the test cases, the serial order of the test case groups can be obtained, and then the test case groups that need to be serialized are arranged in serial order into Group. When the test cases in the test case group to be serialized are executed serially according to the serial order of the test cases in the test case group to be serialized, the serial accuracy can be effectively guaranteed.

The present application also provides a testing device. Referring to Figure 4, the concurrent testing device is characterized in that it includes:

The obtaining module 410 is used for obtaining the configuration information of the test case in the test case set for the target test task;

The extraction module 420 is configured to extract test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case;

The grouping module 430 is configured to input the test case feature information into a pre-trained grouping model to obtain multiple test case groups;

The concurrency module 440 is used for concurrently executing the test cases in the parallel-type test case group, and accessing the thread lock to lock the running test case during concurrent execution, and releasing the thread lock at the end of the operation;

The concurrency ending module 450 is configured to obtain a concurrent test result when the execution of the test cases in the test case group of the parallelizable type ends.

The specific details of each module in the above-mentioned test apparatus have been described in detail in the corresponding concurrent test method, and thus are not repeated here.

It should be noted that although several modules or units of the apparatus for action performance are mentioned in the above detailed description, this division is not mandatory. Indeed, according to embodiments of the present application, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into multiple modules or units to be embodied.

Additionally, although the various steps of the methods of the present application are depicted in the figures in a particular order, this does not require or imply that the steps must be performed in the particular order, or that all illustrated steps must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, and the like.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application may be embodied in the form of software products, and the software products may be stored in a non-volatile storage medium (which may be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present application.

In an exemplary embodiment of the present application, an electronic device capable of implementing the above method is also provided.

As will be appreciated by one skilled in the art, various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application can be embodied in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, which may be collectively referred to herein as implementations "circuit", "module" or "system".

The electronic device 500 according to this embodiment of the present application is described below with reference to FIG. 5 . The electronic device 500 shown in FIG. 5 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present application.

As shown in FIG. 5, electronic device 500 takes the form of a general-purpose computing device. Components of the electronic device 500 may include, but are not limited to, the above-mentioned at least one processing unit 510 , the above-mentioned at least one storage unit 520 , and a bus 530 connecting different system components (including the storage unit 520 and the processing unit 510 ).

Wherein, the storage unit stores program codes, and the program codes can be executed by the processing unit 510, so that the processing unit 510 executes various exemplary methods according to the present application described in the above-mentioned “Exemplary Methods” section of this specification. Implementation steps. For example, the processing unit 510 may perform the steps shown in FIG. 1 .

The storage unit 520 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 5201 and/or a cache storage unit 5202 , and may further include a read only storage unit (ROM) 5203 .

The storage unit 520 may also include a program/utility 5204 having a set (at least one) of program modules 5205 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, An implementation of a network environment may be included in each or some combination of these examples.

The bus 530 may be representative of one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any of a variety of bus structures. bus.

The electronic device 500 may also communicate with one or more external devices 700 (eg, keyboards, pointing devices, Bluetooth devices, etc.), with one or more devices that enable a customer to interact with the electronic device 500, and/or with Any device (eg, router, modem, etc.) that enables the electronic device 500 to communicate with one or more other computing devices. Such communication may occur through input/output (I/O) interface 550 . A display unit 540 connected to an input/output (I/O) interface 550 may also be included, and the electronic device 500 may also be connected to one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a network adapter 560 through a network adapter 560 ). or a public network such as the Internet). As shown, network adapter 560 communicates with other modules of electronic device 500 via bus 530 . It should be understood that, although not shown, other hardware and/or software modules may be used in conjunction with electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives and data backup storage systems.

From the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein may be implemented by software, or may be implemented by software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application may be embodied in the form of software products, and the software products may be stored in a non-volatile storage medium (which may be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiment of the present application.

In an exemplary embodiment of the present application, as shown in FIG. 6 , a computer-readable storage medium is also provided, on which a program product capable of implementing the above-mentioned method of the present specification is stored. In some possible implementations, various aspects of the present application can also be implemented in the form of a program product, which includes program code, which is used to cause the program product to run on a terminal device when the program product is executed. The terminal device performs the steps according to various exemplary embodiments of the present application described in the above-mentioned "Example Method" section of this specification.

Referring to FIG. 6, a program product 600 for implementing the above method according to an embodiment of the present application is described, which can adopt a portable compact disk read only memory (CD-ROM) and include program codes, and can be used in a terminal device, For example running on a personal computer. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal in baseband or as part of a carrier wave with readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium can also be any readable medium, other than a readable storage medium, that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural Programming Language - such as the "C" language or similar programming language. The program code may execute entirely on the client computing device, partly on the client device, as a stand-alone software package, partly on the client computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In the case of a remote computing device, the remote computing device may be connected to the client computing device through any kind of network, including a local area network (LAN) or wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

In addition, the above-mentioned figures are only schematic illustrations of the processes included in the methods according to the exemplary embodiments of the present application, and are not intended to be limiting. It is easy to understand that the processes shown in the above figures do not indicate or limit the chronological order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, in multiple modules.

Other embodiments of the present application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of this application that follow the general principles of this application and include common knowledge or conventional techniques in the technical field not disclosed in this application . The specification and examples are to be regarded as exemplary only, with the true scope and spirit of the application being indicated by the claims.

Claims (10)

1. a test method, is characterized in that, comprises: Obtain the configuration information of the test case in the test case collection for the target test task; Extract test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case; Inputting the test case feature information into a pre-trained grouping model to obtain multiple test case groups; Concurrently execute the test cases in the parallel test case group, and access the thread lock to lock the running test case during concurrent execution, and release the thread lock at the end of the operation; When the execution of the test cases in the parallelizable test case group ends, the concurrent test result is obtained. 2. The method according to claim 1, wherein the training method of the grouping model comprises: Collect a sample set of test case feature information, where each sample in the sample set is pre-calibrated with the grouping label of the corresponding test case; Input the samples in the sample set into the grouping model, and output the predicted grouping labels of the samples; When the predicted grouping label is inconsistent with the pre-calibrated grouping label for the sample, adjust the coefficients of the grouping model until they are consistent; When the grouping model is for the sample set, the predicted grouping labels of all the samples are consistent with the pre-calibrated grouping labels for the samples, and the training ends. 3. The method according to claim 1, characterized in that, the concurrent execution of the test cases in the parallel type test case group, and the access thread lock to lock the test cases in running during concurrent execution, and the end of the operation. when releasing the thread lock, including: Start the concurrent execution of the test cases in the parallel test case group, and access the first thread lock to lock the first test case to start running; When the first start-running test case finishes running, release the first thread lock, and access the second thread lock to lock the second start-running test case; When the second start-running test case finishes running, the second thread lock is released, and subsequent thread locks are alternately accessed and released to execute subsequent start-running test cases until the test is completed. test cases in the test case group. 4. The method according to claim 1, wherein the extracting test case feature information from the configuration information of the test case comprises: Based on the preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain the test case feature information. 5. The method according to claim 1, wherein, based on a preset attribute keyword, the test case attribute information corresponding to the preset attribute keyword is extracted from the configuration information of the test case to obtain The test case feature information includes: Obtain the preset attribute keyword corresponding to the use case type of each test case, the preset attribute keyword includes a general attribute keyword and a special attribute keyword, the general attribute keyword corresponds to all test cases, and the The dedicated attribute keywords described above correspond to each use case type; According to the dedicated attribute keyword and the general attribute keyword corresponding to each test case, test case attribute information is extracted from the configuration information of each test case to obtain the test case feature information. 6. The method according to claim 1, wherein the multiple test case groups further include test case groups whose test cases need to be serialized, and the method further comprises: Serially execute the test cases in the test case group to be serialized until all the test cases are executed; When the execution of the test cases in the test case group to be serialized ends, the serial test result is obtained; The concurrent test result and the serial test result are taken as the total test result. 7. The method according to claim 6, wherein the test case groups to be serialized are arranged into groups in a serial order, and the test cases in the test case groups to be serialized are executed serially ,include: According to the serial order of the test cases in the test case group to be serialized, the test cases in the test case group to be serialized are executed serially. 8. A test device, characterized in that, comprising: The acquisition module is used to acquire the configuration information of the test cases in the test case set used for the target test task; an extraction module, configured to extract test case feature information from the configuration information of the test case, where the test case feature information is a key attribute feature of the execution strategy of each test case; a grouping module for inputting the test case feature information into a pre-trained grouping model to obtain multiple test case groups; A concurrency module, used for concurrently executing the test cases in the parallel-type test case group, and accessing the thread lock to lock the running test case during concurrent execution, and releasing the thread lock at the end of the operation; The end concurrency module is used to obtain concurrent test results when the execution of the test cases in the parallelizable test case group ends. 9 . A computer-readable storage medium having program instructions stored thereon, wherein when the program instructions are executed by a processor, the method of any one of claims 1-7 is implemented. 10 . 10. An electronic device, comprising: processor; and a memory for storing program instructions of the processor; wherein the processor is configured to perform the method of any one of claims 1-7 by executing the program instructions.

Images