Method and device for improving effectiveness of interface automatic recall under dynamic rule configuration

Abstract

The invention relates to the technical field related to script testing, in particular to an interface automatic recall effectiveness improving method and device under dynamic rule configuration. The method comprises the following steps: providing a preset interface for personnel corresponding to each sub-module of a system, so that the corresponding personnel submit defect creation rule information based on the interface; obtaining the defect creation rule information, and generating a defect creation rule; performing global management on the defect creation rule; controlling the system to execute a preset test script; and if the execution fails, creating the defect based on the managed defect creation rule. Through the setting, the rule can be created based on the actual demand of the user, so that the effectiveness of the automatic recall of the interface under the dynamic rule configuration is improved.

Description

Technical Field

[0001] The present application relates to the technical field related to script testing, and in particular to a method and device for improving the effectiveness of interface automatic recall under dynamic rule configuration. Background Art

[0002] The following is the background technical content about this technology generated for you: In the financial industry, with the continuous promotion of interface automation test coverage, the number of interface automation scripts is increasing. However, a large number of script execution failure results need to be analyzed by testers, which leads to a huge workload. In order to improve the efficiency and accuracy of testing, the automatic analysis of interface automation case failure results has become an inevitable trend. At present, common methods for automated result analysis in the industry include interface test result modeling and interface test error result classification analysis methods. Interface test result modeling is to extract model data from the communication level to the application level during the interface test process, including modeled information such as result flags, error codes, error messages, and return information. The interface test error result classification analysis method is based on the interface test result modeling, error code library, and non-defect knowledge base to classify and analyze the interface test results. However, in actual applications, there are many systems in the financial industry, and the commonality between the systems is poor. The causes of false alarms are different and the regularity is poor. This makes the existing technology have certain limitations in dealing with the problem of false alarms in interface automation testing in the financial industry, and cannot meet the needs of the industry. Summary of the invention

[0003] In view of this, the embodiments of the present application are dedicated to providing a method and device for improving the effectiveness of interface automatic recall under dynamic rule configuration, so as to perform script test analysis more comprehensively and effectively.

[0004] This application provides a method for improving the effectiveness of interface automatic recall under dynamic rule configuration, including:

[0005] Providing a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel can submit defect creation rule information based on the interface;

[0006] Obtaining the defect creation rule information and generating a defect creation rule;

[0007] Performing global management on the defect creation rules;

[0008] Controlling the system to execute a preset test script;

[0009] If the execution fails, a defect is created based on the managed defect creation rules.

[0010] In some embodiments, the global management of the defect creation rules includes:

[0011] The defect creation rules corresponding to the various sub-modules are integrated and managed so that different sub-modules share some defect creation rules.

[0012] In some embodiments, it also includes:

[0013] Set up deduplication rules to avoid creating duplicate bug reports.

[0014] In some embodiments, the defect creation rules include rules set based on response results in interface testing;

[0015] The supported conditions for setting rules based on the response results in the interface test include:

[0016] Equal: The response result is exactly the same as the expected result;

[0017] Not equal to: the response result is inconsistent with the expected result;

[0018] Contains: The response contains specific content or patterns;

[0019] Does not contain: The response does not contain the specified content or pattern.

[0020] In some embodiments, the global management of the defect creation rules includes: controlling whether each of the defect creation rules is activated.

[0021] In some embodiments, the controlling the system executes a preset test script;

[0022] Automatically add and execute scripts based on preset interfaces.

[0023] The present application provides a device for improving the effectiveness of interface automatic recall under dynamic rule configuration, including:

[0024] An interface module is used to provide a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel can submit defect creation rule information based on the interface;

[0025] An acquisition module, used to acquire the defect creation rule information and generate a defect creation rule;

[0026] A management module, used for global management of the defect creation rules;

[0027] A control module, used to control the system to execute a preset test script;

[0028] The creation module is used to create defects based on the managed defect creation rules if the execution fails.

[0029] The present application provides an electronic device, including:

[0030] A processor, and a memory for storing a program executable by the processor;

[0031] The processor is used to implement the method for improving the effectiveness of interface automatic recall under the dynamic rule configuration as described above by running the program in the memory.

[0032] The present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the processor is enabled to execute the method for improving the effectiveness of automatic interface recall under the dynamic rule configuration as described above.

[0033] The present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above-mentioned method for improving the effectiveness of interface automatic recall under dynamic rule configuration.

[0034] The present application provides a method for improving the effectiveness of interface automation recall under dynamic rule configuration, including: providing a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel submit defect creation rule information based on the interface; obtaining the defect creation rule information and generating defect creation rules; managing the defect creation rules globally; controlling the system to execute a preset test script; if the execution fails, creating defects based on the managed defect creation rules. In this way, the scheme provided by the present application provides a preset interface to the personnel corresponding to each submodule, so that they can conveniently submit defect creation rule information, reduce the time and cost of information collection, and improve work efficiency. Generate rules based on the acquired defect creation rule information and perform global management, which can ensure the accuracy and consistency of the rules. When the system fails to execute the test script, it can accurately create defects according to the managed rules, which improves the accuracy of defect creation. Personnel of different submodules can submit defect creation rule information according to their own needs, meet the personalized needs of each submodule, and make the system more flexible and adaptable. In this way, the problem of false positives in interface automation testing in the financial industry can be better handled, and the actual needs of various departments in the industry can be met. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] By describing the embodiments of the present application in more detail in conjunction with the accompanying drawings, the above and other purposes, features and advantages of the present application will become more apparent. The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the present application and do not constitute a limitation of the present application. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0036] Figure 1 It is a flow chart of a method for improving the effectiveness of interface automated recall under dynamic rule configuration provided by an embodiment of the present application.

[0037] Figure 2 It is a flowchart of automatically creating defect rules according to a method provided by an embodiment of the present application.

[0038] Figure 3 It is a flowchart of automatically creating defects according to an embodiment of the present application.

[0039] Figure 4 It is a structural diagram of a device for improving the effectiveness of interface automated recall under dynamic rule configuration provided by an embodiment of the present application.

[0040] Figure 5 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] Application Overview

[0043] False positives in automated testing refer to the situation where the system under test returns results that are inconsistent with expectations during the test process. These results may be caused by improper test case design, unstable test environment, unreliable test tools, etc. False positives refer to problems that do not actually exist in the code, but are mistakenly marked as problems that need to be fixed. There are many systems in the financial industry, and the commonality between the systems is poor. The causes of false positives are different and the regularity is poor. The present invention provides a solution to the problem that the causes of false positives of defects in various projects are different, and the false positive rate of defects automatically submitted by the interface automation platform is high. Testers are no longer required to manually analyze and classify defects. They only need to analyze and refine the causes of defects that have been triggered to form false positive configurations. When the interface automation script fails again for the same reason, the defect will no longer be triggered. At the same time, the false positive configuration of defects in each project is closed-loop within the project, and will not affect other projects.

[0044] Furthermore, the interface automation platform is managed by project. The defect types of each project group are different, so the rules for creating defects are also different. The project team registers the corresponding defect creation rules in the rule library based on the experience accumulated in daily life. Script execution is batch executed according to the iteration dimension. The corresponding iteration execution plan is established, and the scripts to be executed are added. Then, during the execution process, the system determines whether to automatically create defects based on the rules set in the project.

[0045] After introducing the basic principles of the present application, various non-limiting embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0046] Exemplary Methods

[0047] Figure 1 FIG. 1 is a flow chart of a method for improving the effectiveness of interface automatic recall under dynamic rule configuration provided by an embodiment of the present application. Figure 1 As shown, the method includes the following contents.

[0048] Step S110, providing a preset interface to personnel corresponding to each submodule of the system, so that the corresponding personnel submit defect creation rule information based on the interface;

[0049] Specifically, the system has designed a special preset interface, which corresponds to each submodule. The relevant personnel of the submodule can operate through this interface to submit information related to the defect creation rules. This interface is designed to facilitate personnel input and ensure that they can accurately convey the specific requirements and conditions of the defect creation rules.

[0050] Step S120, obtaining the defect creation rule information and generating a defect creation rule;

[0051] The system will receive and obtain the defect creation rule information submitted by the personnel on the preset interface. Then, based on this information, the system will process and integrate it to generate the corresponding defect creation rules. The generated rules will serve as the basis for subsequent judgment and handling of defects.

[0052] Step S130, globally managing the defect creation rules;

[0053] The system manages the generated defect creation rules globally, that is, the rules are not limited to a certain submodule or local scope. Global management can ensure the uniformity and coordination of rules and avoid rule conflicts between different submodules. At the same time, it is also convenient for centralized monitoring, adjustment and optimization of rules.

[0054] Step S140, controlling the system to execute a preset test script;

[0055] The system will control the execution of the corresponding test scripts according to the preset arrangements and settings. These test scripts are used to detect the functions and performance of the system to find possible problems. During the execution of the test scripts, the system will closely monitor the execution of the scripts.

[0056] Step S150: If the execution fails, a defect is created based on the managed defect creation rule.

[0057] When the test script fails to execute, the system will determine whether a defect needs to be created based on the previously managed defect creation rules. If the rules meet the conditions for creating a defect, the system will automatically create a defect record. This allows problems in the system to be discovered and recorded in a timely manner, providing a basis for subsequent repairs and improvements.

[0058] Furthermore, the global management of the defect creation rules includes:

[0059] The defect creation rules corresponding to the various sub-modules are integrated and managed so that different sub-modules share some defect creation rules.

[0060] Specifically, the specific contents of the global management of defect creation rules include: Integration management: Unify and summarize the defect creation rules corresponding to each sub-module. Sharing some rules: Through integration, different sub-modules can use some defect creation rules together. The advantage of doing so is that it can avoid the repeated formulation of the same or similar rules and improve the utilization and consistency of the rules. Unified coordination: Global management helps to unify, coordinate and optimize the defect creation rules at the system level to ensure the rationality and effectiveness of the rules. Improve efficiency: Sharing some rules can reduce the redundancy of rules, reduce management costs, and improve management efficiency. Enhance consistency: Ensure that different sub-modules follow the same standards and specifications when handling defect creation, which enhances the consistency and stability of the system.

[0061] In some embodiments, it further includes: setting deduplication rules to avoid creating duplicate defect reports. Specifically, setting deduplication rules is an important part of the defect management process, which aims to avoid creating multiple duplicate defect reports due to multiple triggers of the same problem. The following are the steps and considerations for setting deduplication rules:

[0062] First, you need to collect key information: determine what information will be used to identify duplicate defects, such as error messages, stack traces, failed test cases, etc. Develop deduplication logic: design logical rules to compare new defect reports with existing defect reports to determine whether they are the same or similar. Set similarity threshold: define a similarity threshold. When the similarity between new defects and existing defects exceeds this threshold, they are considered duplicates. Implement deduplication algorithm: develop or select an algorithm to perform deduplication logic, such as text comparison algorithm, hash matching, etc. Integrate deduplication rules and algorithms into the defect tracking system to ensure that deduplication checks are automatically performed before creating new defects. Allow users to configure the parameters of deduplication rules as needed, such as similarity threshold, compared fields, etc. Test deduplication rules on actual data to ensure their accuracy and effectiveness.

[0063] In some embodiments, the defect creation rules include rules set based on response results in interface testing;

[0064] The supported conditions for setting rules based on the response results in the interface test include:

[0065] Equals: The response result is exactly the same as the expected result; specifically, it is used when the response result of the interface must match the expected exact result. If the response result is exactly the same as the expected result, the test is considered passed and no defect is created. Example: If the test expects the return status code to be 200, then set an equals rule to check whether the status code of the response result is 200. If the status code is 200, no defect is created.

[0066] Not equal to: The response result is inconsistent with the expected result; specifically, it is used when the response result of the interface does not match the expected result. If the response result is inconsistent with the expected result, it may indicate a problem, which will trigger the creation of a defect. Example: If a successful payment interface is expected to return a status code of 200, but it actually returns 500, since 500 indicates a server error, this will trigger the not equal to rule and create a defect report.

[0067] Contains: The response result contains specific content or patterns. Specifically, it is used when you need to check whether the response result contains specific content or patterns. If the response result contains the expected specific text or pattern, whether to create a defect is determined based on the rule configuration.

[0068] Example: If the response should contain a "transaction successful" message, you can set an inclusion rule to check for this message. If the message exists, a defect may not be created according to the business logic; if it does not exist, a defect will be created.

[0069] Does not contain: The response result does not contain specific content or patterns. This rule is used when you need to ensure that the response result does not contain certain specific content or patterns. If these contents are missing from the response result, it may indicate a defect, which will trigger the creation of a defect. Example: In the user registration interface, if the response result should contain a "registration successful" message, but the actual response does not contain it, you can set a does not contain rule to check for this situation. If the message is found to be missing, the does not contain rule will be triggered and a defect report will be created.

[0070] In some embodiments, the global management of the defect creation rules includes: controlling whether each of the defect creation rules is activated.

[0071] Global management of defect creation rules includes controlling whether each defect creation rule is enabled. Specifically, this means that the system has the ability to uniformly manage and regulate all defect creation rules. Through this management method, you can flexibly decide which rules should be enabled, which rules should be suspended or disabled according to actual needs and situations.

[0072] For example, in some cases, you may want to enable certain specific defect creation rules to detect and catch certain types of defects; in other cases, you may want to turn off some rules to avoid unnecessary false positives or noise.

[0073] This global management approach can improve the flexibility and adaptability of the system, enabling it to better meet the needs of defect detection and management in different scenarios. At the same time, it also helps to ensure the effective application of defect creation rules and improve the stability and reliability of the system.

[0074] The solution provided by this application is described below in conjunction with specific scenarios:

[0075] Scenario 1: At a certain moment, multiple interface responses are encountered during the script execution process: the layout service response times out. After investigation, it is found that the layout service is being deployed, which takes about 10 minutes. In daily situations, similar environment deployment often leads to batch failure of automated scripts. If defects are directly triggered to be automatically created, such defects are invalid defects, which increases the workload of testers to troubleshoot problems. Therefore, in the rule settings, a rule containing "service response timeout" is set, named "Rule 1". When the script encounters problems with environment deployment during execution, multiple invalid defects will not be created. These batch failed scripts are executed again after the environment is stable by setting failure retry rules.

[0076] Scenario 2: The user table of the backend system rolled back for some reason, causing a large amount of test data in the test data pool to become invalid. When executing the automated scripts, multiple scripts reported "Fund account does not exist" at the login step, and subsequent steps could not be executed. Therefore, a rule whose response includes "Fund account does not exist" is set in the rule settings and named "Rule 2".

[0077] "Rule 1" and "Rule 2" can be set to an "or" relationship, because these two scenarios occur frequently and do not conflict. Similarly, summarize the scenarios of accidental defect triggering encountered during the interface automation execution, and configure the corresponding false alarm rules. In the false alarm scenario described above, we do not want to trigger the automatic creation of defects, and at the same time hope to deduplicate the defects, so we need to check "Do not meet the above rules", "Automatically create defects", "Do not create defects repeatedly", and save.

[0078] In summary, refer to Figure 2 In the solution provided by this application, the process of automatically creating defect rules is as follows: the interface automation platform is managed by project, and the defect types of each project group are different, so the rules for creating defects are also different. The project team registers the corresponding defect creation rules in the rule library based on the experience accumulated in daily life. Script execution is executed in batches according to the iteration dimension, and the corresponding iteration execution plan is established. The scripts to be executed are added, and then during the execution process, the system determines whether to automatically create defects according to the rules set in the project.

[0079] Rule Management:

[0080] Rules are based on response results Response content management settings

[0081] Single conditions support: equal to, not equal to, contain, not contain, these single conditions support and or realize multiple condition combinations.

[0082] Rules are managed in the corresponding projects. After the corresponding rules are enabled in the project, defects will be automatically created when the rules are triggered by the failure of the use case execution in the plan.

[0083] Global rule setting: There are many related defect creation rules in the enterprise. In order to avoid repeated creation of defect rules, project management rules can select global rules.

[0084] 4) Deduplication rule setting: During the execution of scripts, it is found that similar errors are caused by the same problem. If duplicates are not removed, multiple defects will be automatically created, which will increase the time for testers to identify them. Therefore, deduplication rule settings are added. The project team summarizes the rules that need to be deduplicated based on experience.

[0085] Further, see Figure 3 , the steps for automatically creating rules include:

[0086] 1. The project team creates the rules, sets the defect creation rules, and starts the rules. If the rules are enabled, a defect will be created according to the set rules if the script fails to execute. If the rules are not enabled, the script will not be created if it fails to execute.

[0087] 2. The project team adds the interface automation script to the execution plan and executes the script

[0088] 3. If a script in the script set fails to execute, the defect creation mechanism will be triggered if the defect creation rule has been set to enable.

[0089] 4. Before creating a defect, first determine whether the deduplication rule switch is turned on. If it is turned on, first determine whether the same defect already exists. If it already exists, do not create it. If it does not exist, create a defect. If the deduplication switch is not turned on, the script execution fails and a defect is created according to the defect creation rule.

[0090] Exemplary Devices

[0091] The device embodiments of the present application can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0092] Figure 4 The block diagram of the device for improving the effectiveness of interface automatic recall under dynamic rule configuration provided by one embodiment of the present application is shown. Figure 4 As shown, the device comprises:

[0093] The interface module 41 is used to provide a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel can submit defect creation rule information based on the interface;

[0094] An acquisition module 42, used to acquire the defect creation rule information and generate a defect creation rule;

[0095] A management module 43, used for global management of the defect creation rules;

[0096] A control module 44, used to control the system to execute a preset test script;

[0097] The creation module 45 is used to create a defect based on the managed defect creation rules if the execution fails.

[0098] Exemplary Electronic Devices

[0099] Below, reference Figure 5 To describe an electronic device according to an embodiment of the present application. Figure 5 A block diagram of an electronic device according to an embodiment of the present application is illustrated.

[0100] like Figure 5 As shown, electronic device 500 includes one or more processors 510 and memory 520 .

[0101] The processor 510 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 500 to perform desired functions.

[0102] The memory 520 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 510 may run the program instructions to implement the interface automation recall effectiveness improvement method under the dynamic rule configuration of each embodiment of the present application described above and / or other desired functions. Various contents such as category correspondences may also be stored in the computer-readable storage medium.

[0103] In one example, the electronic device 500 may further include: an input device 530 and an output device 540 , and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0104] In addition, the input device 530 may also include, for example, a keyboard, a mouse, an interface, etc. The output device 540 may output various information to the outside, including analysis results, etc. The output device 540 may include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, etc.

[0105] Of course, to simplify, Figure 5 Only some of the components in the electronic device related to the present application are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, the electronic device may further include any other appropriate components according to specific application conditions.

[0106] Exemplary computer program products and computer-readable storage media

[0107] In addition to the above-mentioned methods and devices, an embodiment of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the method for improving the effectiveness of interface automation recall under dynamic rule configuration according to various embodiments of the present application described in the above "Exemplary Method" section of this specification.

[0108] The computer program product may be written in any combination of one or more programming languages ​​to write program codes for performing the operations of the embodiments of the present application, including object-oriented programming languages, such as Java, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0109] In addition, an embodiment of the present application may also be a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, enables the processor to execute the steps of the method for improving the effectiveness of interface automation recall under dynamic rule configuration according to various embodiments of the present application as described in the above “Exemplary Method” section of this specification.

[0110] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0111] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present application to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A method for improving the effectiveness of interface automatic recall under dynamic rule configuration, characterized in that: include: Providing a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel can submit defect creation rule information based on the interface; Obtaining the defect creation rule information and generating a defect creation rule; Performing global management on the defect creation rules; Controlling the system to execute a preset test script; If the execution fails, a defect is created based on the managed defect creation rules.

2. The method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to claim 1 is characterized in that: The global management of the defect creation rules includes: The defect creation rules corresponding to the various sub-modules are integrated and managed so that different sub-modules share some defect creation rules.

3. The method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to claim 1 is characterized in that: Also includes: Set up deduplication rules to avoid creating duplicate bug reports.

4. The method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to claim 1 is characterized in that: The defect creation rules include rules set based on response results in interface testing; The supported conditions for setting rules based on the response results in the interface test include: Equal: The response result is exactly the same as the expected result; Not equal to: the response result is inconsistent with the expected result; Contains: The response contains specific content or patterns; Does not contain: The response does not contain the specified content or pattern.

5. The method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to claim 1 is characterized in that: The global management of the defect creation rules includes: controlling whether each of the defect creation rules is activated.

6. The method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to claim 1 is characterized in that: The controlling the system to execute a preset test script; Automatically add and execute scripts based on preset interfaces.

7. A device for improving the effectiveness of interface automatic recall under dynamic rule configuration, characterized in that: include: An interface module is used to provide a preset interface to the personnel corresponding to each submodule of the system, so that the corresponding personnel can submit defect creation rule information based on the interface; An acquisition module, used to acquire the defect creation rule information and generate a defect creation rule; A management module, used for global management of the defect creation rules; A control module, used to control the system to execute a preset test script; The creation module is used to create defects based on the managed defect creation rules if the execution fails.

8. An electronic device, characterized in that: include: A processor, and a memory for storing a program executable by the processor; The processor is used to implement the method for improving the effectiveness of interface automatic recall under the dynamic rule configuration according to any one of claims 1 to 6 by running the program in the memory.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, enables the processor to execute the method for improving the effectiveness of interface automation recall under the dynamic rule configuration as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method for improving the effectiveness of interface automatic recall under dynamic rule configuration according to any one of claims 1 to 6 is implemented.

Images