CN111309627A - Method and system for preventing test conflict in software test - Google Patents

Abstract

The present invention provides a method and system for preventing test conflicts in software testing. The present invention aims at low testing efficiency, unintelligent testing, waste of hardware equipment, and testing in the existing software testing process, such as changing the underlying configuration or restarting services and other related operations. Insufficient pressure, incomplete coverage of related business and high cost, when the target test case is requested to be executed, whether there is an equivalent operation of the system executing the target test case, whether there is a process in the service or configuration is running, and whether it is related The service is being executed, the urgency and importance of the target test case are monitored, and the execution operation request is sent to the associated user, and the decision whether to immediately execute the target test case is determined according to the needs of the associated user, thereby improving the intelligence of software testing, which is conducive to improving Product quality, increase company efficiency.

Description

A method and system for preventing test conflict in software testing

technical field

The invention relates to the technical field of software testing, in particular to a method and system for preventing testing conflicts in software testing.

Background technique

Nowadays, with the rapid development of information technology, software plays an increasingly important role in all aspects of social life. Software testing is produced along with the production of software. Issues such as software usability and security are the main concerns of users and developers. , There are many problems after the development of computer software, so the software must be tested, whether it is as small as an app, as large as an operating system or a cloud computing service platform, multiple testers are required to test it. Since there are multiple people working together on a test environment, the operations of one tester may affect another, especially when it involves low-level configuration or restarting services to verify certain services.

Existing software testing requires multiple testers to test in modules and layers for large environments such as cloud management platforms. Some of the underlying tests in the testing process require frequent configuration changes or restart of operating services. Sometimes it will affect the testing of other testers. At present, the main ways to deal with this problem are as follows: the communication software informs other testers of the operations that need to be done, asks whether it affects everyone's testing, and then starts the test; waits for other testers to test when they are not testing; redeploy a test New test environment for testing. However, it is inefficient and unintelligent to ask whether the communication affects the test of others or to wait until the test is over. However, if each person deploys a set of test environments, it wastes deployment time and requires more hardware equipment to support, wastes resources and increases costs, and each person tests one module in one set of environment, which will reduce the test pressure of the environment, and the differences between the modules will be reduced. The associated impact cannot be fully covered, and the test business cannot be carried out systematically.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a method and system for preventing test conflicts in software testing, aiming to solve the problems of low testing efficiency, unintelligent testing, waste of hardware equipment, insufficient testing pressure, incomplete coverage of related services, and high cost in the prior art , to improve the intelligence of software testing, which is conducive to improving product quality.

In order to achieve the above-mentioned technical purpose, the present invention provides a method for preventing test conflict in software testing, and the method includes the following operations:

Set up a feature database to record and store various services and the time required for processing;

When there is a test case execution request, obtain the target test case and issue a monitoring command;

Whether there is an equivalent operation involving the execution of the target test case in the operation of traversing all users, if it exists, it will be queued and polled at intervals according to the processing time stored in the feature database;

Determine whether there is a running process or associated process involved in executing the target test case, if there is, wait in line, and perform interval polling according to the processing time stored in the feature database;

Determine whether there is an associated service involved in executing the target test case, if not, execute the target test case directly, otherwise go to the next step;

Determine whether the urgency of the target test case is the highest. If it is the highest, execute the target test case directly. Otherwise, send an execution request to the associated test user. If the tester agrees to interrupt the test, execute the target test case. If they do not agree, wait in line.

Preferably, the feature database records and stores the time required for services and processing associated with changing configuration and restarting services, the process of each service and the time required for process processing, and the associated service and processing time required for each service.

Preferably, when there is an equivalent operation involving the execution of the target test case, interval polling is performed according to the time required for the process of changing the configuration and restarting the service associated with the service stored in the feature database; When the process of the target test case or the associated process, the interval polling is performed according to the process processing time of the process of each service stored in the feature database.

The present invention also provides a system for preventing test conflicts in software testing, the system comprising:

Feature database, which is used to set the feature database, record and store the time required for various services and processing;

The target test case acquisition module is used to acquire the target test case and issue the monitoring command when there is a test case execution request;

The monitoring module is used to traverse all user operations according to the monitoring command to see if there is an equivalent operation involving the execution of the target test case, to determine whether there is a running process or associated process that involves the execution of the target test case, and to determine whether there is a process that involves the execution of the target test case. Associate services, and send the monitoring results to the judgment and decision-making module;

The judgment and decision module is used to process the monitoring results returned by the monitoring module according to the priority. When there is an equivalent operation involving the execution of the target test case, it will wait in a queue and poll at intervals according to the processing time stored in the feature database. ; when there is a running process or associated process involved in executing the target test case, queue waiting, and poll at intervals according to the processing time stored in the feature database; and when there is an associated service involved in executing the target test case , decide whether to execute the target test case according to the urgency, and directly execute the target test case when it does not exist.

Preferably, the feature database records and stores the time required for services and processing associated with changing configuration and restarting services, the process of each service and the time required for process processing, and the associated service and processing time required for each service.

Preferably, when there is an equivalent operation involving the execution of the target test case, interval polling is performed according to the time required for the process of changing the configuration and restarting the service associated with the service stored in the feature database; When the process of the target test case or the associated process, the interval polling is performed according to the process processing time of the process of each service stored in the feature database.

The present invention also provides a device for preventing test conflicts in software testing, including:

memory for storing computer programs;

The processor is used for executing the computer program to implement the method for preventing test conflict in software testing.

The present invention also provides a readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the method for preventing test conflicts in software testing is implemented.

The effects provided in the summary of the invention are only the effects of the embodiments, rather than all the effects of the invention. One of the above technical solutions has the following advantages or beneficial effects:

Compared with the prior art, the present invention aims at low testing efficiency, unintelligent testing, waste of hardware equipment, insufficient testing pressure, incomplete coverage of related services and high cost in the related operations such as changing the underlying configuration or restarting services in the existing software testing process. This paper proposes a method to prevent test conflicts in software testing. When the target test case is requested to be executed, whether there is an equivalent operation of the target test case in the system, whether there is a process in the service or configuration is running, whether Monitor the execution of the associated service and the urgency and importance of the target test case, and send the execution operation request to the associated user, and judge and decide whether to execute the target test case immediately according to the needs of the associated user, thereby improving the intelligence of software testing. Conducive to improving product quality and increasing company benefits.

Description of drawings

1 is a flowchart of a method for preventing test conflicts in a software test provided in an embodiment of the present invention;

Fig. 2 is the working flow chart of judging and decision-making according to the priority according to the monitoring result provided in the embodiment of the present invention;

FIG. 3 is a block diagram of a system for preventing test conflicts in software testing according to an embodiment of the present invention.

Detailed ways

In order to clearly illustrate the technical features of the solution, the present invention will be described in detail below through specific embodiments and in conjunction with the accompanying drawings. The following disclosure provides many different embodiments or examples for implementing different structures of the invention. In order to simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in different instances. This repetition is for the purpose of simplicity and clarity and does not in itself indicate a relationship between the various embodiments and/or arrangements discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and processes are omitted from the present invention to avoid unnecessarily limiting the present invention.

The method and system for preventing test conflicts in software testing provided by the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

As shown in FIG. 1 , the present invention discloses a method for preventing test conflicts in software testing, and the method includes the following operations:

Set up a feature database to record and store various services and the time required for processing;

When there is a test case execution request, obtain the target test case and issue a monitoring command;

Whether there is an equivalent operation involving the execution of the target test case in the operation of traversing all users, if it exists, it will be queued and polled at intervals according to the processing time stored in the feature database;

Determine whether there is a running process or associated process involved in executing the target test case, if there is, wait in line, and perform interval polling according to the processing time stored in the feature database;

Determine whether there is an associated service involved in executing the target test case, if not, execute the target test case directly, otherwise go to the next step;

Determine whether the urgency of the target test case is the highest. If it is the highest, execute the target test case directly. Otherwise, send an execution request to the associated test user. If the tester agrees to interrupt the test, execute the target test case. If they do not agree, wait in line.

The embodiment of the present invention judges whether the target test case is allowed to be executed by monitoring the same user operation, service or configuration process, associated service and the urgency of the target test case being executed.

Collect test cases, when there is a new test case to be executed, obtain the target test case and save the test case, when the execution of the target test case is triggered, the monitoring command will be issued. The newly added test cases will be added to the test case library.

Set up a feature database, and record and store the operations associated with changing the configuration and restarting the service or the time required for the service and processing in the feature database, record and store the process of each service and the process processing time, and record the associated services and services of the service. operation and processing time.

Monitor the execution of target test cases, and make judgments and decisions according to priority according to the monitoring results.

As shown in Figure 2, when a request to execute a test case is received, whether the operation of traversing all users in the system involves executing the equivalent operation of the target test case, if the returned result is that there is an equivalent operation, it will be queued and waited, and according to the feature database The processing time stored in the database is polled at intervals; when no equivalent operation is detected, it is judged whether there is a process in the service or configuration running, and if so, it is queued, and the interval round is performed according to the processing time stored in the feature database. When it is detected that the service or the process in the configuration is not running, it is judged whether there is an associated service to operate, if not, the test case can be directly executed, if there is, it is judged whether the urgency and importance of the test case are The highest, if it is the highest, the test case will be executed directly. If it is not the highest, an execution request will be sent to the associated test user. When the tester agrees to interrupt the test, the test case will be executed. If they do not agree, they will wait in line.

In response to the above judgment and decision, the result of executing the test case is stored, and the result is returned to all testers whether the test case has been executed at present, the execution operation is recorded, and the user is warned to avoid the relevant operation and perform other tests first. Execute the request of the test case, and decide whether to allow the execution according to the need. You can also see if the user's own actions are affected by the execution of other use cases.

The embodiments of the present invention address the problems of low test efficiency, unintelligent testing, waste of hardware equipment, insufficient test pressure, incomplete coverage of related services, and high cost in the related operations such as changing the underlying configuration or restarting services in the existing software testing process. A method for changing the underlying configuration or restarting a service in software testing. When the target test case is requested to be executed, whether there is an equivalent operation of the system executing the target test case, whether there is a process in the service or configuration is running, whether there is The associated service is being executed, the urgency and importance of the target test case are monitored, and the execution operation request is sent to the associated user, and the decision is made to immediately execute the target test case according to the needs of the associated user, thereby improving the intelligence of software testing and conducive to Improve product quality and increase company efficiency.

As shown in FIG. 3 , an embodiment of the present invention further discloses a system for preventing test conflicts in software testing, the system comprising:

Feature database, which is used to set the feature database, record and store the time required for various services and processing;

The target test case acquisition module is used to acquire the target test case and issue the monitoring command when there is a test case execution request;

The monitoring module is used to traverse all user operations according to the monitoring command to see if there is an equivalent operation involving the execution of the target test case, to determine whether there is a running process or associated process that involves the execution of the target test case, and to determine whether there is a process that involves the execution of the target test case. Associate services, and send the monitoring results to the judgment and decision-making module;

The judgment and decision module is used to process the monitoring results returned by the monitoring module according to the priority. When there is an equivalent operation involving the execution of the target test case, it will wait in a queue and poll at intervals according to the processing time stored in the feature database. ; when there is a running process or associated process involved in executing the target test case, queue waiting, and poll at intervals according to the processing time stored in the feature database; and when there is an associated service involved in executing the target test case , decide whether to execute the target test case according to the urgency, and directly execute the target test case when it does not exist.

Collect test cases. When there is a new test case to be executed, obtain the target test case and save the test case. When the execution of the target test case is triggered, a judgment decision command will be issued. The newly added test cases will be added to the test case library.

Set up a feature database, and record and store the operations associated with changing the configuration and restarting the service or the time required for the service and processing in the feature database, record and store the process of each service and the process processing time, and record the associated services and services of the service. operation and processing time.

Monitor the execution of target test cases, and make judgments and decisions according to priority according to the monitoring results.

When a request to execute a test case is received, check whether the operation of traversing all users in the system involves performing the equivalent operation of the target test case. If the returned result is that there is an equivalent operation, it will be queued and waited according to the processing time stored in the feature database. Interval polling; when no equivalent operation is detected, it is judged whether there is a process in the service or configuration running, if so, it is queued and polled at intervals according to the processing time stored in the feature database; when no equivalent operation is detected If the service or the process in the configuration is running, it is judged whether there is an associated service to operate. If not, the test case can be directly executed. If so, it is judged whether the urgency and importance of the test case are the highest. Execute the test case directly. If it is not the highest, send an execution request to the associated test user. When the tester agrees to interrupt the test, execute the test case. If they disagree, wait in line.

In response to the above judgment and decision, the result of executing the test case is stored, and the result is returned to all testers whether the test case has been executed at present, the execution operation is recorded, and the user is warned to avoid the relevant operation and perform other tests first. Execute the request of the test case, and decide whether to allow the execution according to the need. You can also see if the user's own actions are affected by the execution of other use cases.

The embodiment of the present invention also discloses a device for preventing test conflicts in software testing, including:

memory for storing computer programs;

The processor is used for executing the computer program to implement the method for preventing test conflict in software testing.

The embodiment of the present invention also discloses a readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the method for preventing test conflicts in software testing is implemented.

The above descriptions are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the protection of the present invention. within the range.

Claims (8)

1. A method for preventing test collision in software testing, the method comprising the operations of:

setting a characteristic database, and recording and storing various services and time required by processing;

when a test case execution request exists, acquiring a target test case and issuing a monitoring command;

traversing whether the operation of all users has the same operation related to executing the target test case, if so, queuing and waiting, and performing interval polling according to the time required by processing stored in the characteristic database;

judging whether a running process or a related process related to the execution of the target test case exists, if so, queuing and waiting, and performing interval polling according to the time required for processing stored in the characteristic database;

judging whether the associated service related to the execution of the target test case exists, if not, directly executing the target test case, otherwise, executing the next step;

and judging whether the emergency degree of the target test case is the highest, if so, directly executing the target test case, otherwise, sending an execution request to a related test user, if the test personnel approve to interrupt the test, executing the target test case, and if not, queuing for waiting.

2. The method of claim 1, wherein the time required for the services and processes comprises: time required for changing configuration and restarting services and processing associated with the services, time required for process and process processing of each service, and time required for associated services and processing of each service.

3. The method of claim 2, wherein when there is an equivalent operation related to executing a target test case, polling is performed at intervals according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.

4. A system for preventing test conflicts in software testing, the system comprising:

the characteristic database is used for setting the characteristic database and recording and storing various services and time required by processing;

the target test case acquisition module is used for acquiring a target test case and issuing a monitoring command when a test case execution request exists;

the monitoring module is used for traversing all the user operations according to the monitoring command to judge whether the same operation related to the execution of the target test case exists, judging whether the running process or the associated process related to the execution of the target test case exists, judging whether the associated service related to the execution of the target test case exists and sending the monitoring result to the judgment decision module;

the judgment decision module is used for processing the monitoring result returned by the monitoring module according to the priority, queuing for waiting when the same operation related to the execution of the target test case exists, and polling at intervals according to the processing time stored in the characteristic database; when a running process or a related process related to the execution of the target test case exists, queuing and waiting are carried out, and interval polling is carried out according to the time required for processing stored in the characteristic database; and when the associated service related to the execution of the target test case exists, determining whether to execute the target test case according to the emergency degree, and directly executing the target test case when the associated service does not exist.

5. The system of claim 4, wherein the time required for the services and processes comprises: time required for changing configuration and restarting services and processing associated with the services, time required for process and process processing of each service, and time required for associated services and processing of each service.

6. The system of claim 5, wherein when there are equivalent operations related to executing target test cases, polling is performed at intervals according to the time required for changing the configuration and restarting the processing of the service associated with the service stored in the feature database; when the running process or the associated process related to the execution of the target test case exists, interval polling is carried out according to the process processing time of the process of each service stored in the characteristic database.

7. An apparatus for preventing test collision in software test, comprising:

a memory for storing a computer program;

a processor for executing the computer program to implement the method for preventing test collision in software testing according to any one of claims 1 to 3.

8. A readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements a method for preventing test collision in a software test according to any one of claims 1 to 3.

Images