WO2018188538A1

WO2018188538A1 - Rule verification method, terminal, and storage medium

Info

Publication number: WO2018188538A1
Application number: PCT/CN2018/082228
Authority: WO
Inventors: 曹辉荣; 黄宇
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-04-10
Filing date: 2018-04-09
Publication date: 2018-10-18
Also published as: CN108415823B; CN108415823A

Abstract

Provided by the present application are a rule verification method, terminal, and a storage medium. Said method comprises: acquiring a case set; according to the case set, creating a new task for performing rule verification on a new item; configuring a thread used to execute said task; said thread extracting cases having a case status of non-implemented from said case set and altering the case status of said cases to implemented; said thread respectively implementing all rules by using said cases in the new item and an old item to obtain both a first result and a second result; comparing said first result with the second result to obtain a comparison result.

Description

Rule verification method, terminal and storage medium

This application claims the priority of the Chinese Patent Application, filed on Apr. 10, 2017, the number of which is hereby incorporated by reference. .

Technical field

The present application relates to the field of data processing technologies, and in particular, to a rule verification method, a terminal, and a storage medium.

Background technique

Developers can't guarantee 100% correct changes to the rules involved in the development process (including modifying rules, adding rules, such as the maximum age of 65 can be a rule) and developing code, and find that a rule is problematic. The longer the time (either the problem itself or the problem of developing code), the greater the potential loss. Therefore, there is a need for a method to improve the verification of rules and to find out the rules that are problematic in development.

Summary of the invention

The present application provides a rule verification method, a terminal, and a storage medium, which can use a case set to compare the results obtained by executing all the rules in the new project and the old project, so that the relevant personnel pay attention to the rules with different comparison results, and improve the rule. The efficiency of rule validation.

In a first aspect, the application provides a rule verification method, the method comprising:

Get the case set;

Newly perform the task of verifying rules for new projects based on the case set;

Configuring a thread for performing the task;

The thread extracts the case state into an unexecuted case from the case set and modifies the case state of the case to be executed;

The thread uses the case to execute all rules in the new project to obtain the first result;

The thread uses the case to execute all rules in the old project to obtain a second result;

The first result is compared to the second result to obtain a comparison result.

In a second aspect, the application provides a terminal, where the terminal includes:

An acquisition unit for obtaining a case set;

a task establishing unit, configured to perform a task of performing rule verification on a new item according to the case set;

a configuration unit configured to configure a thread for performing the task;

An extracting unit, configured to extract an unexecuted case from the thread to the case set and modify a case state of the case to be executed;

a first result unit, configured by the thread to execute all rules in the new project to obtain a first result;

a second result unit, configured by the thread to execute all rules in the old project to obtain a second result;

a comparison unit for comparing the first result with the second result to obtain a comparison result.

In a third aspect, the present application further provides a terminal, the terminal comprising: a memory, and a processor connected to the memory; the memory is configured to store program data; and the processor is configured to run the stored in the memory Program data to perform the method described in the first aspect above.

In a fourth aspect, the application further provides a computer readable storage medium storing one or more program data, the one or more program data being executable by one or more processors To achieve the method described in the first aspect above.

The method and the terminal provided by the embodiments of the present application compare the results obtained by executing all the rules in the new project and the old project by using the case set, so as to verify the rules developed in the new project, so that the relevant personnel pay attention to the difference in the comparison results. Rules improve the efficiency of rule validation in new projects.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are some embodiments of the present application, For the ordinary technicians, other drawings can be obtained based on these drawings without any creative work.

1 is a schematic flowchart of a rule verification method provided by an embodiment of the present application;

2 is a schematic diagram of a sub-flow of a rule verification method according to an embodiment of the present application;

3 is a schematic diagram of a sub-flow of a rule verification method according to an embodiment of the present application;

4 is a schematic flowchart of a rule verification method according to another embodiment of the present application;

FIG. 5 is a schematic diagram of a sub-flow of a rule verification method according to an embodiment of the present application;

FIG. 6 is a schematic block diagram of a terminal according to an embodiment of the present disclosure;

FIG. 7 is a schematic block diagram of a configuration unit provided by an embodiment of the present application;

8 is a schematic block diagram of an adjustment unit provided by an embodiment of the present application;

FIG. 9 is a schematic block diagram of a terminal according to another embodiment of the present disclosure;

FIG. 10 is a schematic block diagram of a thread number obtaining unit according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a terminal according to another embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

The use of the terms "comprising", "comprising", "","," The presence or addition of a plurality of other features, integers, steps, operations, elements, components, and/or collections thereof. It is also to be understood that the term "and/or" used in the specification and the appended claims are intended to mean any combination and all possible combinations of one or more of the associated listed items.

FIG. 1 is a schematic flowchart diagram of a rule verification method according to an embodiment of the present application. The method includes S101 to S108.

S101, obtaining a case set. A case set includes multiple cases. For example, in the insurance industry, a case corresponds to a policy, and a policy includes all information about the insured, such as height, weight, and historical insurance information.

S102: Perform a task of performing rule verification on the new item according to the case set. After the new task is created, the task is executed. S103-S108 is the content of the task.

S103. Configure a thread for performing the task. The number of threads of the task is saved in the preset configuration file. The initial value of the task is the default value. You can modify the number of threads of the task by modifying the corresponding configuration item in the preset configuration file. Specifically, as shown in FIG. 2, S103 includes S201-S202. S201. Obtain a thread number in a preset configuration file. Get the number of threads in the preset configuration file by obtaining the value of the corresponding configuration item in the preset configuration file. S202. Adjust the current number of threads of the task so that the number of threads is equal to the number of threads in the preset configuration file. Understandably, the current number of threads of the task is zero when the task begins execution. Specifically, as shown in FIG. 3, S202 includes S301-303. S301. Determine whether the number of threads in the preset configuration file is greater than the current number of threads in the task. If the number of threads in the preset configuration file is greater than the current number of threads in the task, S302 is performed; if the number of threads in the preset configuration file is less than the current number of threads in the task, S303 is performed. S302. Create a new thread, where the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task. S303. Close the thread after the thread execution case ends, where the number of closed threads is the difference between the current number of threads of the task and the number of threads in the preset configuration file. Closing a thread sets the state of the thread to false.

S104. The thread to the case set extracts a case state that is not executed and modifies the case state of the case to be executed. The thread of the task goes to the case set to extract the case state as unexecuted. Preferably, the case state is unexecuted in a preset order in the case set. If the case status is unexecuted according to the number order of the cases in the case set or other suitable order. For example, if the task is configured with 10 threads, then the 10 threads will extract the cases from the case set, and extract them according to the number sequence of the case set cases. When a thread extracts the case status as an unexecuted case, the case of the case is immediately taken. The state is modified to execute to prevent other threads from fetching the same case. At the same time, multiple threads execute in parallel, which improves the efficiency of rule verification. After each thread extracts the case, the case state of the case is modified to execute, and the efficiency and accuracy are improved.

S105. The thread uses the case to execute all the rules in the new project to obtain the first result. After a thread extracts the case, it uses the case to execute all the rules in the new project to get the first result.

S106. The thread uses the case to execute all rules in the old project to obtain a second result. Among them, new projects and old projects refer to projects that can solve different periods of at least one of the same basic problems, and can also refer to new and old versions of a project.

S107. Compare the first result with the second result to obtain a comparison result. The thread compares the first and second results of the new project and the execution of all the rules in the project, and compares the results so that the developer pays attention to the rules of the differences in the comparison results.

In addition, in the process of executing a task, if a thread executes a case for more than a preset time, the case state of the case is modified to an exception, and then returns to the thread to the case set to extract the case state as unexecuted case. And modify the case status of the case as the step of execution. The abnormal case of timeout can be excluded, and the execution of the task will not be stopped due to the abnormal case, that is, the thread then executes other cases whose status is unexecuted, further improving the efficiency of the rule verification. In addition, when a task is interrupted, the situation when an interrupt occurs is saved, such as when the interrupt occurs. When the task is executed again, the thread will then execute from the case when the interrupt occurs, that is, the case saved by the thread extraction interrupt will modify the case state of the case to execution, and the thread uses the case to the new project and the old project respectively. Execute all the rules to get the first result and the second result, and compare the first result with the second result to obtain the comparison result until there is no case case of the unexecuted case, and improve the efficiency of the rule verification again to avoid the interruption The impact of task execution. For example, because the test environment often needs to restart the environment due to the deployment operation, after the restart, the unfinished tasks will not be interrupted and will continue to be executed. For example: a task has 1000 cases. When the execution reaches 500, the server restarts. After restarting, the program will continue to execute the remaining 500 cases until it is completed.

FIG. 4 is a schematic flowchart diagram of a rule verification method according to another embodiment of the present application. The method includes S401 to S409. The difference from the embodiment of Fig. 1 is that steps S408-S409 are added.

S401, obtaining a case set. A case set includes multiple cases.

S402: Perform a task of performing rule verification on the new item according to the case set. After the new task is created, the task is executed. S403-S409 is the content of the task performed.

S403. Configure a thread for performing the task. The number of threads of the task is saved in the preset configuration file. The initial value of the task is the default value. You can modify the number of threads of the task by modifying the corresponding configuration item in the preset configuration file. Specifically, as shown in FIG. 2, S403 includes S201-S202. S201. Obtain a thread number in a preset configuration file. Get the number of threads in the preset configuration file by obtaining the value of the corresponding configuration item in the preset configuration file. S202. Adjust the current number of threads of the task so that the number of threads is equal to the number of threads in the preset configuration file. Understandably, the current number of threads of the task is zero when the task begins execution. As shown in FIG. 3, S202 includes S301-303. For details, refer to the content described in the embodiment of FIG. 3.

S404. The thread to the case set extracts a case state that is not executed, and modifies the case state of the case to be executed. The thread of the task goes to the case set to extract the case state as unexecuted. Preferably, the case state is extracted to the unexecuted case in order. For example, if the task has 10 threads configured, then the 10 threads will extract the cases from the case set, and extract them according to the order in which the cases are concentrated. When a thread extracts the case status as an unexecuted case, the case of the case is immediately taken. The state is modified to execute to prevent other threads from fetching the same case. At the same time, multiple threads execute in parallel, which improves the efficiency of rule verification. After each thread extracts the case, the case state of the case is modified to execute, and the efficiency and accuracy are improved.

S405. The thread uses the case to execute all rules in a new project to obtain a first result.

S406. The thread uses the case to execute all rules in the old project to obtain a second result. Among them, new projects and old projects refer to projects that can solve different periods of at least one of the same basic problems, and can also refer to new and old versions of a project.

S407. Compare the first result with the second result to obtain a comparison result. The thread compares the first and second results of the new project and the execution of all the rules in the project, and obtains the comparison results, so that the developer can pay attention to the rules of the differences in the comparison results and improve the efficiency of the rule verification.

S408. Determine whether there is a case in which the case status is unexecuted in the case set. If there is a case with an unexecuted case, execute S409; if there is no case with an unexecuted case, end.

S409, determining whether the preset time is reached. Preferably, the preset time is 5 minutes. If the preset time is reached, S403 is performed; if the preset time is not reached, S404 is executed. It can be understood that, when the task starts executing, configuring a thread for the user to execute the task; in the process of executing the subsequent task, performing the step of configuring the thread for executing the task by the user every preset time, that is, executing in the subsequent task. During the process, the number of threads in the preset configuration file is obtained every preset time, and the current number of threads of the task is adjusted so that the number of threads is equal to the number of threads in the preset configuration file. This embodiment can dynamically adjust the number of threads of the task to better utilize terminal resources and improve the efficiency of rule verification.

In addition, this embodiment can also eliminate the abnormal case of timeout, and the execution of the task will not stop due to the abnormal case; in this embodiment, when the task is interrupted, the situation when the interrupt occurs will be saved, for example, when the interruption occurs. When the task is executed again, the thread of the task will then execute from the case when the interrupt occurred.

In other embodiments, the setting of the number of threads in the preset configuration file is related to the current time. Specifically, as shown in FIG. 5, S201 includes S401-S402. S401, obtaining the current time. S402. Obtain a number of threads corresponding to the current time set in the preset configuration file. For example, during 9:00-19:00 during the daytime, the number of corresponding threads set in the preset configuration file is one. At other times, the number of corresponding threads set in the preset configuration file is 10. Understandably, during the daytime work, the number of threads set is small, and there is no need to occupy too much memory resources of the terminal; at night, during non-working hours, the terminal is almost useless, and the number of threads is set, and the resources of the terminal are fully utilized to improve the rule verification. effectiveness.

FIG. 6 is a schematic block diagram of a terminal according to an embodiment of the present application. The terminal 60 includes an obtaining unit 601, a task establishing unit 602, a configuration unit 603, an extracting unit 604, a first result unit 605, a second result unit 606, and a comparing unit 607.

The obtaining unit 601 is configured to acquire a case set. A case set includes multiple cases. For example, in the insurance industry, a case corresponds to a policy, and a policy includes all information about the insured, such as height, weight, and historical insurance information.

The task establishing unit 602 is configured to newly create a task for performing rule verification on the new item according to the case set.

The configuration unit 603 is configured to configure a thread for performing the task. The number of threads of the task is saved in the preset configuration file, and the number of threads of the task can be modified by modifying the corresponding configuration item in the preset configuration file. Specifically, as shown in FIG. 7, the configuration unit 603 includes a thread number acquisition unit 701 and an adjustment unit 702. The thread number obtaining unit 701 is configured to obtain the number of threads in the preset configuration file. Get the number of threads in the preset configuration file by obtaining the value of the corresponding configuration item in the preset configuration file. The adjusting unit 702 is configured to adjust the current number of threads of the task so that the number of threads is equal to the number of threads in the preset configuration file. Understandably, the current number of threads of the task is zero when the task begins execution. Specifically, as shown in FIG. 8, the adjustment unit 702 includes a thread number determination unit 801, a thread establishment unit 802, and a thread closure unit 803. The thread number determining unit 801 is configured to determine whether the number of threads in the preset configuration file is greater than the current number of threads of the task. The thread establishing unit 802, if the number of threads in the preset configuration file is greater than the current number of threads of the task, creates a new thread, wherein the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task. The thread close unit 803, if the number of threads in the preset configuration file is less than the current number of threads of the task, the thread is closed after the thread execution case ends, wherein the number of closed threads is the current number of threads of the task and the preset configuration file. The difference in the number of threads. Closing a thread sets the state of the thread to false.

The extracting unit 604 is configured to extract an unexecuted case from the thread to the case set and modify a case state of the case to be executed. The thread of the task goes to the case set to extract the case state as unexecuted. Preferably, the case state is unexecuted in a preset order in the case set. If the case status is unexecuted according to the number order of the cases in the case set or other suitable order. For example, if the task has 10 threads configured, then the 10 threads will extract the cases from the case set, and extract them according to the number sequence of the case set cases. After a thread extracts the case status as an unexecuted case, the case is immediately taken. The case status is modified to execute to prevent other threads from fetching the same case. At the same time, multiple threads execute in parallel, which improves the efficiency of rule verification. After each thread extracts the case, the case state of the case is modified to execute, and the efficiency and accuracy are improved.

The first result unit 605 is configured to obtain, by the thread, the first result by using the case to execute all rules in the new item. After a thread extracts the case, it uses the case to execute all the rules in the new project to get the first result.

The second result unit 606 is configured to obtain a second result by the thread using the case to execute all rules in the old item. Among them, new projects and old projects refer to projects that can solve different periods of at least one of the same basic problems, and can also refer to new and old versions of a project.

The comparing unit 607 is configured to compare the first result with the second result to obtain a comparison result, so that the developer pays attention to the rule of the difference in the comparison result.

In addition, in the process of executing a task, if a thread executes a case for more than a preset time, the case state of the case is modified to an exception, and then returns to the thread to the case set to extract the case state as unexecuted case. And modify the case status of the case as the step of execution. The abnormal case of timeout can be excluded, and the execution of the task will not be stopped due to the abnormal case, that is, the thread then executes the case where the other case status is not executed, further improving the efficiency of the rule verification. In addition, when a task is interrupted, the situation when an interrupt occurs is saved, such as when the interrupt occurs. When the task is executed again, the thread will then execute from the case when the interrupt occurs, that is, the case saved by the thread extraction interrupt will modify the case state of the case to execution, and the thread uses the case to the new project and the old project respectively. Execute all the rules to get the first result and the second result, and compare the first result with the second result to obtain the comparison result until there is no case case of the unexecuted case, and improve the efficiency of the rule verification again to avoid the interruption The impact of task execution. For example, because the test environment often needs to restart the environment due to the deployment operation, after the restart, the unfinished tasks will not be interrupted and will continue to be executed. For example: a task has 1000 cases. When the execution reaches 500, the server restarts. After restarting, the program will continue to execute the remaining 500 cases until it is completed.

FIG. 9 is a schematic block diagram of a terminal according to another embodiment of the present application. The terminal 90 includes an obtaining unit 901, a task establishing unit 902, a configuration unit 903, an extracting unit 904, a first result unit 905, a second result unit 906, a comparing unit 907, and a determining unit 908. The terminal 90 differs from the terminal 60 in a determination unit 908.

The determining unit 908 is configured to determine whether there is a case in the case set that is not executed. The determining unit 908 is further configured to determine whether the preset time is reached if there is a case in which the case status is not executed. If the preset time is reached, the content of the configuration unit is executed; if the preset time is not reached, the extraction unit is triggered. Preferably, the preset time is 5 minutes. It can be understood that, when the task starts executing, configuring a thread for the user to execute the task; in the process of executing the subsequent task, performing the step of configuring the thread for executing the task by the user every preset time, that is, executing in the subsequent task. During the process, the number of threads in the preset configuration file is obtained every preset time, and the current number of threads of the task is adjusted so that the number of threads is equal to the number of threads in the preset configuration file. This embodiment can dynamically adjust the number of threads of the task to better utilize terminal resources and improve the efficiency of rule verification.

In other embodiments, the setting of the number of threads in the preset configuration file is related to the current time. Specifically, as shown in FIG. 10, the thread number acquisition unit 701 includes a time acquisition unit 101 and a file thread number acquisition unit 102. The time obtaining unit 101 is configured to acquire a current time. The file thread number obtaining unit 102 is configured to obtain the number of threads corresponding to the current time set in the preset configuration file. For example, during 9:00-19:00 during the daytime, the number of corresponding threads set in the preset configuration file is one. At other times, the number of corresponding threads set in the preset configuration file is 10. Understandably, during the daytime work, the number of threads set is small, and there is no need to occupy too much memory resources of the terminal; at night, during non-working hours, the terminal is almost useless, and the number of threads is set, and the resources of the terminal are fully utilized to improve the rule verification. effectiveness.

The above terminal can be implemented in the form of a computer program data which can be run on a terminal as shown in FIG.

FIG. 11 is a schematic block diagram of a terminal according to a fourth embodiment of the present application. The terminal 110 includes a memory 111 and a processor 112, and the memory 111 and the processor 112 are connected by a bus 113. among them:

The memory 111 is for storing program data with various functions. The data stored in the memory 111 in the embodiment of the present application includes a case set, a preset configuration file, a first result, a second result, a comparison result, and the like, and other program data that can be called and run. In a specific implementation, the memory 111 of the embodiment of the present application may be a system memory, such as a non-volatile (such as a ROM, a flash memory, etc.), or a combination of the two. In a specific implementation, the memory 111 of the embodiment of the present application may also be an external memory outside the system, such as a magnetic disk, an optical disk, a magnetic tape, or the like. The memory 111 provides an environment for the execution of program data that, when executed by the processor 112, causes the processor 112 to perform the above-described rule verification method.

The processor 112 is configured to run program data stored in the memory 111 and perform the following operations:

Obtaining a case set; creating a task for performing rule verification on the new item according to the case set; configuring a thread for executing the task; and the thread extracting a case in which the case status is not executed and modifying the case of the case to the case set The state is execution; the thread uses the case to execute all rules in the new project to obtain a first result; the thread uses the case to execute all rules in the old project to obtain a second result; the first result is The second results are compared for comparison results. The thread extracts the case state into an unexecuted case in the order of the case and modifies the case state of the case as execution.

The processor 112 also performs the following operations:

Determine whether there is a case in which the case status is unexecuted; if yes, return the thread to the case set to extract the case status as unexecuted case and modify the case status of the case as the execution step.

The processor 112 also performs the following operations:

Obtaining the number of threads in the preset configuration file; adjusting the current number of threads of the task so that the number of threads is equal to the number of threads in the preset configuration file.

The processor 112 also performs the following operations:

Determining whether the number of threads in the preset configuration file is greater than the current number of threads of the task; if the number of threads in the current task is greater than the current number of threads of the task, creating a new thread, wherein the number of newly created threads is the number of threads in the configuration file and the current thread of the task If the number of threads is less than the current number of threads of the task, the thread is closed after the thread execution case ends, wherein the number of closed threads is the difference between the current number of threads of the task and the number of threads in the preset configuration file. value.

The processor 112 also performs the following operations:

Get the current time; get the number of threads corresponding to the current time set in the preset configuration file.

The application further provides a computer readable storage medium storing one or more program data, the one or more program data being executable by one or more processors, when All of the embodiments of the above rule verification method can be implemented when one or more program data is executed by one or more processors.

The computer readable storage medium may be an internal storage unit of the terminal, such as a hard disk or memory of the terminal. The computer readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk equipped with the terminal, a smart memory card (SMC), a Secure Digital (SD) card, or the like. Further, the computer readable storage medium may also include both an internal storage unit of the terminal and an external storage device.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the terminal and the unit described above can be referred to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed terminal and method may be implemented in other manners. For example, the terminal embodiment described above is only illustrative. For example, the division of the unit is only a logical function division, and the actual implementation may have another division manner. The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

A rule verification method, the method comprising:

Get the case set;

Newly perform the task of verifying rules for new projects based on the case set;

Configuring a thread for performing the task;

The thread extracts the case state into an unexecuted case from the case set and modifies the case state of the case to be executed;

The thread uses the case to execute all rules in the new project to obtain the first result;

The thread uses the case to execute all rules in the old project to obtain a second result;

The first result is compared to the second result to obtain a comparison result.
The method of claim 1 wherein the method further comprises:

Determine whether there is a case in which the case status is unexecuted;

If there is a case in which the case status is unexecuted, it is judged whether the preset time is reached;

If the preset time is reached, returning to the step of configuring a thread for executing the task; if the preset time is not reached, returning the thread to the case set to extract the case state as an unexecuted case and modifying the case state of the case is The steps performed.
The method of claim 1 wherein configuring a thread for performing the task comprises:

Get the number of threads in the default configuration file;

The current number of threads of the task is adjusted such that the number of threads is equal to the number of threads in the preset configuration file.
The method of claim 3, wherein the current number of threads of the task is adjusted such that the number of threads is equal to the number of threads in the preset configuration file, including:

Determining whether the number of threads in the preset configuration file is greater than the current number of threads of the task;

If it is greater than the current number of threads of the task, create a new thread, wherein the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task;

If the number of threads of the task is less than the current number of threads of the task, the thread is closed after the thread execution case ends, wherein the number of closed threads is the difference between the current number of threads of the task and the number of threads in the preset configuration file.
The method of claim 3, wherein the setting of the number of threads in the preset configuration file is related to the current time, and the number of threads in the preset configuration file is obtained, including:

Get the current time;

Gets the number of threads corresponding to the current time set in the default configuration file.
A terminal, wherein the terminal comprises:

An acquisition unit for obtaining a case set;

a task establishing unit, configured to perform a task of performing rule verification on a new item according to the case set;

a configuration unit configured to configure a thread for performing the task;

An extracting unit, configured to extract an unexecuted case from the thread to the case set and modify a case state of the case to be executed;

a first result unit, configured by the thread to execute all rules in the new project to obtain a first result;

a second result unit, configured by the thread to execute all rules in the old project to obtain a second result;

a comparison unit for comparing the first result with the second result to obtain a comparison result.
The terminal according to claim 6, wherein the terminal further comprises a judging unit, wherein the judging unit is configured to determine whether the case status is an unexecuted case in the case set; if the case status is unexecuted in the case set The case is also used to determine whether the preset time is reached; if the preset time is reached, the configuration unit is triggered, and if the preset time is not reached, the extraction unit is triggered.
The terminal according to claim 6, wherein the configuration unit comprises a thread number acquisition unit and an adjustment unit;

The thread number obtaining unit is configured to obtain the number of threads in the preset configuration file;

The adjusting unit is configured to adjust a current thread number of the task such that the number of threads is equal to the number of threads in the preset configuration file.
The terminal according to claim 8, wherein the adjustment unit comprises a thread number determination unit, a thread establishment unit, and a thread closure unit;

The thread number determining unit is configured to determine whether the number of threads in the preset configuration file is greater than the current number of threads of the task;

The thread establishing unit is configured to: if the number of threads in the preset configuration file is greater than the current number of threads of the task, create a new thread, wherein the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task;

The thread closing unit is configured to: if the number of threads in the preset configuration file is less than the current number of threads of the task, close the thread after the thread execution case ends, wherein the number of closed threads is the current number of threads and the pre-task of the task Set the difference in the number of threads in the configuration file.
The terminal according to claim 8, wherein the number of threads in the preset configuration file is related to a current time, and the thread number obtaining unit includes a time acquiring unit and a file thread number acquiring unit;

The time acquiring unit is configured to acquire a current time;

The file thread number obtaining unit is configured to obtain the number of threads corresponding to the current time set in the preset configuration file.
A terminal, comprising: a memory, and a processor connected to the memory; the memory is configured to store program data; the processor is configured to execute program data stored in the memory to execute The following steps:

Get the case set;

Newly perform the task of verifying rules for new projects based on the case set;

Configuring a thread for performing the task;

The thread extracts the case state into an unexecuted case from the case set and modifies the case state of the case to be executed;

The thread uses the case to execute all rules in the new project to obtain the first result;

The thread uses the case to execute all rules in the old project to obtain a second result;

The first result is compared to the second result to obtain a comparison result.
The terminal according to claim 11, wherein said processor further performs the following steps:

Determine whether there is a case in which the case status is unexecuted;

If there is a case in which the case status is unexecuted, it is judged whether the preset time is reached;

If the preset time is reached, returning to the step of configuring a thread for executing the task; if the preset time is not reached, returning the thread to the case set to extract the case state as an unexecuted case and modifying the case state of the case is The steps performed.
The terminal according to claim 11, wherein the processor performs the following steps when executing the thread configured to execute the task:

Get the number of threads in the default configuration file;

The current number of threads of the task is adjusted such that the number of threads is equal to the number of threads in the preset configuration file.
The terminal according to claim 13, wherein the processor performs the following steps when performing the adjustment of the current number of threads of the task such that the number of threads is equal to the number of threads in the preset configuration file. :

Determining whether the number of threads in the preset configuration file is greater than the current number of threads of the task;

If the number of threads of the task is greater than the current number of threads of the task, a new thread is created, wherein the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task;

If the number of threads of the task is less than the current number of threads of the task, the thread is closed after the thread execution case ends, wherein the number of closed threads is the difference between the current number of threads of the task and the number of threads in the preset configuration file.
The terminal according to claim 13, wherein the setting of the number of threads in the preset configuration file is related to a current time, and when the processor executes the acquiring the number of threads in the preset configuration file, the specific Perform the following steps:

Get the current time;

Gets the number of threads corresponding to the current time set in the default configuration file.
A computer readable storage medium, characterized in that the computer readable storage medium stores one or more program data, the one or more program data being executable by one or more processors to implement the following steps:

Get the case set;

Newly perform the task of verifying rules for new projects based on the case set;

Configuring a thread for performing the task;

The thread extracts the case state into an unexecuted case from the case set and modifies the case state of the case to be executed;

The thread uses the case to execute all rules in the new project to obtain the first result;

The thread uses the case to execute all rules in the old project to obtain a second result;

The first result is compared to the second result to obtain a comparison result.
The computer readable storage medium of claim 16 wherein said step further comprises:

Determine whether there is a case in which the case status is unexecuted;

If there is a case in which the case status is unexecuted, it is judged whether the preset time is reached;

If the preset time is reached, returning to the step of configuring a thread for executing the task; if the preset time is not reached, returning the thread to the case set to extract the case state as an unexecuted case and modifying the case state of the case is The steps performed.
The computer readable storage medium according to claim 16, wherein the processor specifically implements the following steps when executing the thread configured to perform the task:

Get the number of threads in the default configuration file;

The current number of threads of the task is adjusted such that the number of threads is equal to the number of threads in the preset configuration file.
The computer readable storage medium of claim 18, wherein the processor is performing the adjusting the current number of threads of the task such that the number of threads is equal to the number of threads in the preset configuration file, The specific steps are as follows:

Determining whether the number of threads in the preset configuration file is greater than the current number of threads of the task;

If it is greater than the current number of threads of the task, create a new thread, wherein the number of newly created threads is the difference between the number of threads in the configuration file and the current number of threads of the task;

If the number of threads of the task is less than the current number of threads of the task, the thread is closed after the thread execution case ends, wherein the number of closed threads is the difference between the current number of threads of the task and the number of threads in the preset configuration file.
The computer readable storage medium according to claim 18, wherein the setting of the number of threads in the preset configuration file is related to a current time, and the processor is executing the thread in the acquiring a preset configuration file When the number is counted, the specific steps are as follows:

Get the current time;

Gets the number of threads corresponding to the current time set in the default configuration file.