Non-coded page automatic testing method and device, electronic equipment and medium

Abstract

The present disclosure provides a non-coding page automatic testing method and device, electronic equipment and medium. The above method and device can be used in the field of computer testing technology. The non-coding page automatic testing method comprises: obtaining a test case corresponding to a test point, wherein the test case comprises a page element and a test step; obtaining test data corresponding to the page element; testing the page element and the test data according to the test step to obtain a test result; generating a test report according to the test result; and configuring a case weight value of the test case and a data weight value of the test data according to the test result.

Description

Technical Field

[0001] This disclosure relates to the field of computer testing technology, and more specifically, to a method, apparatus, electronic device, and medium for automatic page testing without coding. Background Technology

[0002] In existing technologies, user interface automation testing tools primarily drive system events by running scripts to manipulate user interface elements (such as menus, buttons, icons, text boxes, lists, and dialog boxes). Based on the system's performance, mainly the page's performance (e.g., screen verification, changes in page element size and position, text arrangement, usability conditions, and data integrity), they determine whether the expected results have been achieved, thus completing automated test case verification. Currently, mainstream interface testing tools include Selenium and QTP. Summary of the Invention

[0003] In view of this, this disclosure provides a code-free automatic page testing method, apparatus, electronic device, and computer-readable storage medium that is easy to maintain, low in cost, readable, and reusable.

[0004] One aspect of this disclosure provides a no-coding automatic page testing method, comprising: acquiring test cases corresponding to test points, wherein the test cases include page elements and test steps; acquiring test data corresponding to the page elements; testing the page elements and the test data according to the test steps to obtain test results; generating a test report based on the test results; and configuring case weight values ​​for the test cases and data weight values ​​for the test data based on the test results.

[0005] According to the no-coding automatic page testing method of this disclosure, after acquiring test cases and test data, the page elements of the test cases and the test data can be tested according to the testing steps to obtain test results. On the one hand, based on the test results, a test report can be generated. Through the test report, testers can understand the operation status of the test and the validity of the test cases and test data. In addition, the test report can also be stored as experience information for subsequent tests. On the other hand, based on the test results, the case weight value of the test cases and the data weight value of the test data can be configured. By configuring the case weight value and the data weight value, the test cases and test data can be automatically maintained, reducing maintenance costs, and improving the readability and reusability of the test cases and test data.

[0006] In some embodiments, obtaining test cases corresponding to test points includes: in response to the transaction name and test points input by the tester, searching a first database for test cases corresponding to the transaction name and the test points; and when a test case corresponding to the transaction name and the test points is found, selecting a test case based on the case weight value.

[0007] In some embodiments, obtaining test data corresponding to the page element includes: searching a second database for test data corresponding to the page element of the selected test case; and when test data corresponding to the page element is found, selecting the test data according to the data weight value.

[0008] In some embodiments, the test result includes whether the test case runs successfully or fails. When the test result is that the test case runs successfully, configuring the test case weight value and the test data weight value according to the test result includes: increasing the test case weight value and updating it to the first database; and increasing the test data weight value and updating it to the second database.

[0009] When the test result is a case execution error, the method further includes: analyzing the cause of the case execution error and obtaining an error classification result. The step of configuring the case weight value of the test case and the data weight value of the test data according to the test result includes: configuring the case weight value of the test case and the data weight value of the test data according to the error classification result.

[0010] In some embodiments, the error classification result includes environmental problems, data problems, or program problems. When the error classification result is an environmental problem, the test steps are repeated m times to test the page elements and the test data, where m is an integer greater than or equal to 1. If the test result is still a case execution error each time, and the error classification result is an environmental problem, the step of configuring the case weight value of the test case and the data weight value of the test data according to the error classification result includes: keeping the case weight value of the test case in the first database unchanged; and keeping the data weight value of the test data in the second database unchanged.

[0011] When the error classification result is a data problem, configuring the case weight value of the test case and the data weight value of the test data according to the error classification result includes: increasing the case weight value of the test case and updating it to the first database; and decreasing the data weight value of the test data and updating it to the second database. When the error classification result is a program problem, configuring the case weight value of the test case and the data weight value of the test data according to the error classification result includes: increasing the case weight value of the test case and updating it to the first database; and increasing the data weight value of the test data and updating it to the second database.

[0012] In some embodiments, the test result includes either a test case running successfully or a test case running incorrectly. When the test result is a test case running incorrectly, the method further includes: analyzing the cause of the test case running error to obtain an error classification result, the error classification result including environmental problems, data problems, or program problems; when the test case runs successfully, configuring the test case weight value and the test data weight value according to the test result, including: calculating and updating the test case weight value based on the total number of times the test case runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time; and calculating and updating the test data weight value based on the total number of times the test data runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time, wherein a test case running successfully includes a test result of "test case running successfully" and a test result of "test case running incorrectly" where the error classification result includes data problems or program problems.

[0013] In some embodiments, the test result includes whether the test case runs successfully or fails. When the test result is that the test case runs successfully, the test report includes information indicating that the test case runs successfully; when the test result is that the test case runs incorrectly, the test report includes information indicating that the test case runs incorrectly.

[0014] Another aspect of this disclosure provides a code-free automatic page testing device, comprising: a first acquisition module, configured to acquire test cases corresponding to test points, wherein the test cases include page elements and test steps; a second acquisition module, configured to acquire test data corresponding to the page elements; a testing module, configured to perform tests on the page elements and the test data according to the test steps to obtain test results; a generation module, configured to generate a test report based on the test results; and a configuration module, configured to configure the case weight values ​​of the test cases and the data weight values ​​of the test data based on the test results.

[0015] Another aspect of this disclosure provides an electronic device including one or more processors and one or more memories, wherein the memories are used to store executable instructions that, when executed by the processor, implement the method described above.

[0016] Another aspect of this disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are used to implement the method described above. Attached Figure Description

[0017] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0018] Figure 1 This illustration schematically shows an exemplary system architecture to which methods and apparatus can be applied according to embodiments of the present disclosure;

[0019] Figure 2 A flowchart illustrating an automatic page testing method without coding according to an embodiment of the present disclosure is shown schematically;

[0020] Figure 3 A flowchart illustrating the acquisition of test cases corresponding to test points according to embodiments of this disclosure is shown in the illustration.

[0021] Figure 4 A flowchart illustrating the acquisition of test cases corresponding to test points according to embodiments of this disclosure is shown in the illustration.

[0022] Figure 5 This schematically illustrates a flowchart of obtaining test data corresponding to page elements according to an embodiment of the present disclosure;

[0023] Figure 6 This schematically illustrates a flowchart of obtaining test data corresponding to page elements according to an embodiment of the present disclosure;

[0024] Figure 7 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on test results, according to an embodiment of the present disclosure.

[0025] Figure 8 A flowchart illustrating an automatic page testing method without coding according to an embodiment of the present disclosure is shown schematically;

[0026] Figure 9 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on test results, according to an embodiment of the present disclosure.

[0027] Figure 10 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on error classification results, according to an embodiment of the present disclosure.

[0028] Figure 11 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on error classification results, according to an embodiment of the present disclosure.

[0029] Figure 12 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on error classification results, according to an embodiment of the present disclosure.

[0030] Figure 13 This schematically illustrates a flowchart of configuring case weight values ​​for test cases and data weight values ​​for test data based on test results, according to an embodiment of the present disclosure.

[0031] Figure 14 A block diagram of a codeless automatic page testing system according to an embodiment of the present disclosure is shown schematically;

[0032] Figure 15 A schematic diagram illustrating the structure of an automated page testing apparatus without coding according to an embodiment of the present disclosure is shown.

[0033] Figure 16 This schematically illustrates a structural block diagram of a first acquisition module according to an embodiment of the present disclosure;

[0034] Figure 17 A schematic diagram illustrating the structure of a second acquisition module according to an embodiment of the present disclosure is shown.

[0035] Figure 18 A schematic diagram illustrating the structure of a configuration module according to an embodiment of the present disclosure is shown.

[0036] Figure 19A schematic diagram illustrating the structure of an automated page testing apparatus without coding according to an embodiment of the present disclosure is shown.

[0037] Figure 20 A schematic diagram illustrating the structure of a configuration unit according to an embodiment of the present disclosure is shown.

[0038] Figure 21 A schematic diagram illustrating the structure of a configuration unit according to an embodiment of the present disclosure is shown.

[0039] Figure 22 A block diagram of an electronic device according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0040] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0041] In the technical solution disclosed herein, the acquisition, storage, and application of user personal information all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals. In the technical solution disclosed herein, the acquisition, collection, storage, use, processing, transmission, provision, disclosure, and application of data all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals.

[0042] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0043] When using expressions such as "at least one of A, B, or C," it should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, features defined with "first" or "second" may explicitly or implicitly include one or more of the stated features.

[0044] In existing technologies, user interface automation testing tools primarily drive system events by running scripts to manipulate user interface elements (such as menus, buttons, icons, text boxes, lists, and dialog boxes). Based on the system's performance, mainly the page's performance (e.g., screen verification, changes in page element size and position, text arrangement, usability conditions, and data integrity), they determine whether the expected results have been achieved, thus completing automated test case verification. Currently, mainstream interface testing tools include Selenium and QTP. Existing page automation testing frameworks have significant drawbacks: test data requires manual maintenance by testers, resulting in high maintenance costs; the learning curve for testers writing automated test cases is steep; and the readability and reusability of test cases are poor.

[0045] This disclosure provides a no-coding automatic page testing method, apparatus, electronic device, computer-readable storage medium, and computer program product. The no-coding automatic page testing method includes: acquiring test cases corresponding to test points, wherein the test cases include page elements and test steps; acquiring test data corresponding to the page elements; testing the page elements and test data according to the test steps to obtain test results; generating a test report based on the test results; and configuring case weight values ​​for the test cases and data weight values ​​for the test data based on the test results.

[0046] It should be noted that the codeless automatic page testing method, apparatus, electronic device, computer-readable storage medium and computer program product disclosed herein can be used in the field of testing technology, and can also be used in any field other than the field of testing technology, such as the financial field. The field of this disclosure is not limited here.

[0047] Figure 1 This illustration schematically depicts an exemplary system architecture 100 to which a no-coding automatic page testing method, apparatus, electronic device, computer-readable storage medium, and computer program product can be applied according to embodiments of this disclosure. It should be noted that... Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0048] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, and 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the terminal devices 101, 102, and 103 and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0049] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0050] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0051] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0052] It should be noted that the codeless automatic page testing method provided in this disclosure embodiment can generally be executed by server 105. Correspondingly, the codeless automatic page testing device provided in this disclosure embodiment can generally be located in server 105. The codeless automatic page testing method provided in this disclosure embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the codeless automatic page testing device provided in this disclosure embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0053] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0054] The following will be based on Figure 1 The described scene, through Figures 2 to 13 The method for automatic page testing without coding according to embodiments of this disclosure will be described in detail.

[0055] Figure 2 A flowchart illustrating an automatic page testing method without coding according to an embodiment of the present disclosure is shown.

[0056] like Figure 2 As shown, the uncoded automatic page testing method of this embodiment includes operations S210 to S250.

[0057] In operation S210, obtain test cases corresponding to the test points, where test cases include page elements and test steps.

[0058] As one possible way to achieve this, such as Figure 3 As shown, operation S210 obtains test cases corresponding to the test points, including operation S211 and operation S212.

[0059] In operation S211, in response to the transaction name and test points entered by the tester, the system searches the first database for test cases corresponding to the transaction name and test points. Taking a bank transfer as an example, the transaction name can be understood as "bank transfer," and the test points can be understood as including sequential redirects from the login page to the transfer success page, from the login page to the transfer failure page, and from the login page to the "retry later" page. The above test points are merely illustrative; other test points may exist under the transaction name "bank transfer," which will not be listed here.

[0060] Taking bank wealth management business as an example, the transaction name can be understood as bank wealth management. The test points can be understood as including the sequential jump from the login page to the successful purchase page, the sequential jump from the login page to the failed purchase page, and the sequential jump from the login page to the retry page. The above test points are only examples. There may be other test points under the transaction name of bank wealth management, which will not be listed here.

[0061] The aforementioned bank transfer and wealth management services are merely illustrative examples. This disclosure can also be applied to other services, and the transaction names and test points can be assigned different characteristic attributes according to different services. Specifically, for each test point of each transaction name, there can be corresponding test cases. Each test case can include k pages, each page can include Si page elements, and each test case can also include test steps to connect the Si page elements of each page. k and Si are both integers greater than or equal to 1, and i is an integer greater than or equal to 1 and less than or equal to k.

[0062] The following explanation uses bank transfer as an example, but it should not be construed as a limitation of this disclosure.

[0063] For example, a login page may include at least one of the following elements: an account input field, a password input field, a verification code input field, and an "OK" button. Similarly, a transfer amount settings page may include a receiving account input field, a paying account input field, a transfer amount input field, and an "OK" button. Furthermore, a receipt page may include a dropdown menu. Accordingly, the testing steps may include entering test data (account, password, verification code) on the login page, clicking "OK," and if the test data is available, redirecting to the transfer amount settings page, entering the receiving account, paying account, and transfer amount, clicking "OK," and if the test data is available, redirecting to the receipt page, and displaying a dropdown menu on the receipt page. If the dropdown menu is available, the receipt page will scroll.

[0064] The first database is used to store test cases.

[0065] In operation S212, when test cases corresponding to the transaction name and test points are found, test cases are selected based on their weight values. It should be noted that in the first database, there can be g test cases corresponding to the transaction name and test points, where g is an integer greater than or equal to 1. Each test case has a weight value. In some examples, when g is greater than 1, the top h test cases can be selected based on their weight values, sorted from largest to smallest, where h is an integer greater than or equal to 1 and less than g.

[0066] By operating S211 and S212, it is easy to obtain test cases corresponding to the test points.

[0067] As one possible way to achieve this, such as Figure 4 As shown, operation S210 obtains test cases corresponding to the test points, and also includes operations S213 and S214.

[0068] In operation S213, when no test case corresponding to the transaction name and test point is found, the test case entered by the tester is obtained and stored in the first database.

[0069] In operation S214, test cases input by testers are retrieved from the first database. Operations S213 and S214 allow for the retrieval of test cases corresponding to the transaction name and test points even when no such test case exists in the first database.

[0070] In operation S220, test data corresponding to page elements is obtained.

[0071] As one possible way to achieve this, such as Figure 5 As shown, operation S220, which obtains test data corresponding to page elements, includes operations S221 and S222.

[0072] In operation S221, the test data corresponding to the page elements of the selected test case is searched in the second database. The second database can be understood as the database that stores the test data. Taking the page elements of the login page—account input box, password input box, verification code input box, and OK button—as an example, the test data corresponding to these page elements can be the account, password, and verification code. The test data types corresponding to the page elements of the transfer amount setting page and the page elements of the receipt page are similar, and will not be elaborated further here.

[0073] In operation S222, when test data corresponding to page elements is found, test data is selected based on the data weight value. It should be noted that in the second database, there can be r test data corresponding to page elements, where r is an integer greater than or equal to 1. Each test data has a data weight value. In some examples, when r is greater than 1, the top v test cases can be selected based on the data weight values ​​sorted from largest to smallest, where v is an integer greater than or equal to 1 and less than r.

[0074] By operating S221 and S222, it is easy to obtain test data corresponding to page elements.

[0075] As one possible way to achieve this, such as Figure 6 As shown, operation S220 obtains test data corresponding to page elements, and also includes operations S223 and S224.

[0076] In operation S223, when no test data corresponding to the page element is found, the test data entered by the tester is obtained and stored in the second database.

[0077] In operation S224, test data input by the tester is extracted from the second database. Operations S223 and S224 allow for the retrieval of test data corresponding to page elements even when no such data exists in the second database.

[0078] When operating S230, the page elements and test data are tested according to the test steps to obtain the test results.

[0079] When operating S240, a test report is generated based on the test results.

[0080] As an feasible approach, test results can include whether the test case runs successfully or fails.

[0081] When the test result indicates that the test case has passed, the test report may include information indicating that the test case has passed.

[0082] When the test result indicates a test case execution error, the test report can include test case execution error information.

[0083] Therefore, through test reports, testers can understand the execution status of the test, as well as the validity of the test cases and the test data. Furthermore, test reports can be stored as valuable experience for future testing.

[0084] When operating the S250, based on the test results, configure the case weight values ​​of the test cases and the data weight values ​​of the test data.

[0085] As an example of what can be implemented, test results may include whether the test case runs successfully or fails.

[0086] like Figure 7 As shown, when the test result is that the test case runs successfully, operation S250 configures the test case weight value and the test data weight value according to the test result, including operation S251 and operation S252.

[0087] In operation S251, the case weight value of the test case is increased and updated to the first database.

[0088] In operation S252, the data weight value of the test data is increased and updated to the second database.

[0089] Understandably, when the test result shows that the test case passes, it means that both the test case and the test data are valid. Therefore, the case weight value of the test case can be increased and updated to the first database, and the data weight value of the test data can be increased and updated to the second database. This will ensure that valid cases and valid data are selected with a high probability in the next test, thereby improving testing efficiency and saving testing costs.

[0090] like Figure 8 As shown, when the test result is a test case execution error, the no-code page automatic testing method also includes operation S260: analyze the cause of the test case execution error and obtain the error classification result.

[0091] like Figure 9 As shown, operation S250 configures the case weight value of the test case and the data weight value of the test data according to the test results, including operation S253: configure the case weight value of the test case and the data weight value of the test data according to the error classification results.

[0092] As specific examples, error classification results can include environmental issues, data issues, or program issues. Environmental issues can be understood as both hardware and software environments. The hardware environment refers to the necessary testing equipment, including servers, clients, network connection devices, and auxiliary hardware such as printers / scanners. The software environment refers to the operating system, database, and other application software running the software under test. Under special conditions, the network environment, such as network bandwidth and IP address settings, should also be considered. Data issues can be understood as problems with the test data. Program issues can be understood as problems with the program to which the page belongs.

[0093] like Figure 10 As shown, when the error classification result is an environmental problem, the page elements and test data are tested m times according to the test steps, where m is an integer greater than or equal to 1. If the test result is still a case execution error each time, and the error classification result is an environmental problem, operation S253 configures the case weight value of the test case and the data weight value of the test data according to the error classification result, including operation S2531 and operation S2532.

[0094] In operation S2531, the case weight values ​​of the test cases in the first database remain unchanged.

[0095] In operation S2532, the data weight values ​​of the test data in the second database are kept unchanged.

[0096] Understandably, when the test steps are repeated m times to test the page elements and test data, and the test result is still a test case execution error each time, and the error classification result is an environmental problem, it means that there is indeed a problem with the environment. The test cases and test data, whether valid or invalid, cannot play a testing role. Therefore, it is impossible to verify the validity of the test cases and test data used. Thus, the test case weight values ​​in the first database and the data weight values ​​in the second database can be kept unchanged.

[0097] When the error classification result is an environmental issue, and the test steps are repeated m times to test page elements and test data, and each test result still indicates a test case execution error and the error classification result is an environmental issue, operations S2531 and S2532 can facilitate configuring the test case weight value and the test data data weight value based on the error classification result. Configuring the test case weight value and data weight value can automatically maintain the test cases and test data, reducing maintenance costs, and also improving the readability and reusability of the test cases and test data.

[0098] like Figure 11As shown, when the error classification result is a data problem, operation S253 configures the case weight value of the test case and the data weight value of the test data according to the error classification result, including operation S2533 and operation S2534.

[0099] In operation S2533, the case weight value of the test case is increased and updated to the first database.

[0100] In operation S2534, the data weight value of the test data is reduced and updated to the second database.

[0101] Understandably, when the misclassification result is a data problem, it indicates that the validity of the test data is relatively low. However, if the test cases can detect data problems, it indicates that the validity of the test cases is relatively high. Therefore, the case weight value of the test cases can be increased and updated in the first database, while the data weight value of the test data can be decreased and updated in the second database.

[0102] When the misclassification result indicates a data problem, operations S2533 and S2534 facilitate configuring the test case weight values ​​and the test data weight values ​​based on the misclassification result. Configuring these weight values ​​allows for automatic maintenance of test cases and test data, reducing maintenance costs and improving the readability and reusability of both.

[0103] like Figure 12 As shown, when the error classification result is a program problem, operation S253 configures the case weight value of the test case and the data weight value of the test data according to the error classification result, including operation S2535 and operation S2536.

[0104] In operation S2535, the case weight value of the test case is increased and updated to the first database.

[0105] In operation S2536, the data weight value of the test data is increased and updated to the second database.

[0106] It is understandable that when the error classification result is a program problem, it means that the test cases and test data can be used to determine that it is a program problem. This indicates that the effectiveness of the test cases and test data is relatively high. Therefore, the case weight value of the test cases can be increased and updated to the first database, and the data weight value of the test data can be increased and updated to the second database.

[0107] When the error classification result is a program problem, operations S2535 and S2536 facilitate configuring the test case weight values ​​and test data weight values ​​based on the error classification result. Configuring these weight values ​​allows for automatic maintenance of test cases and test data, reducing maintenance costs and improving the readability and reusability of both.

[0108] According to some embodiments of this disclosure, the test result may include whether the test case runs successfully or fails. When the test result is a test case error, the no-code automatic page testing method further includes: analyzing the cause of the test case error to obtain an error classification result, which may include environmental problems, data problems, or program problems.

[0109] like Figure 13 As shown, when the test case runs successfully, operation S250 configures the case weight value of the test case and the data weight value of the test data according to the test results, including operation S001 and operation S002.

[0110] In operation S001, the test case weight value is calculated and updated based on the total number of test case runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time.

[0111] In some specific examples, the case weight value ETC can be calculated using formula (1).

[0112]

[0113] Where T represents the total number of times the test case was run; PT represents the number of times the test case was run successfully; LPD represents the date the test case was last run successfully; LPT represents the time the test case was last run; RD represents the current date the test case was run; and RT represents the current time the test case was run.

[0114] In operation S002, the data weight value of the test data is calculated and updated based on the total number of runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time.

[0115] In some specific examples, the case weight value ETD can be calculated using formula (2).

[0116]

[0117] Where T represents the total number of times the test data was run; PT represents the number of times the test data was run successfully; LPD represents the date of the last successful run of the test data; LPT represents the time of the last run of the test data; RD represents the current date of the test data run; and RT represents the current time of the test data run.

[0118] Successful test case execution includes a test result indicating that the test case has passed, and a test result indicating that the test case has an error and the error classification includes data problems or program problems.

[0119] By operating S001 and S002, it is easy to configure the case weight value of test cases and the data weight value of test data based on the test results.

[0120] According to the no-coding automatic page testing method of this disclosure, after acquiring test cases and test data, the page elements of the test cases and the test data can be tested according to the testing steps to obtain test results. On the one hand, based on the test results, a test report can be generated. Through the test report, testers can understand the operation status of the test and the validity of the test cases and test data. In addition, the test report can also be stored as experience information for subsequent tests. On the other hand, based on the test results, the case weight value of the test cases and the data weight value of the test data can be configured. By configuring the case weight value and the data weight value, the test cases and test data can be automatically maintained, reducing maintenance costs, and improving the readability and reusability of the test cases and test data.

[0121] The following reference Figure 14 This document describes in detail a no-coding automatic page testing method according to embodiments of the present disclosure. It is important to understand that the following description is merely illustrative and not intended to limit the scope of this disclosure.

[0122] This disclosure proposes a no-code automated page testing method and system. The method first establishes a basic test database based on data entered by testers when writing automated test cases and keywords in the test points. Then, a basic case database is formed based on the test pages, test points, test steps, and expected results entered by the testers. When automated test cases are executed, the method extracts the latest and most valid test data from the test data database according to the keywords in the test points and sends it to the case execution module. After the automated test is completed, the validity weights of the cases and data in the database are updated based on the test results. This method effectively improves the reusability of automated test cases and data, and reduces the cost of manually maintaining existing automated test cases.

[0123] The no-coding automatic page testing method proposed in this disclosure is as follows.

[0124] Step 1.0 Testers use the "transaction name + test points" criteria in the case entry module's search function to search for existing successfully run cases in the case database. The case bank algorithm will display available cases to testers in descending order of case validity weight. Testers then select cases with high validity weights to run.

[0125] Step 1.1.1 If testers fail to find a successfully executed case in the case database using the "Transaction Name + Test Points" search function in the case entry module, they need to complete the case recording. In the test page entry module, testers will fill in the case page URL and click the "Extract Page Elements" button to obtain the XPath of all page elements. After obtaining the XPath, click "Complete" to enter the case recording module. If the case involves multiple pages, testers need to obtain the page elements page by page. After obtaining the XPath, click "Complete" to enter the test step entry module.

[0126] Step 1.1.2 After entering the test steps, the tester first needs to input the test points, test steps and expected results in the test case. The test steps require selecting the pages to be operated on and the page elements to be operated on each page, and specifying the actions to be performed on the page elements.

[0127] Step 2: After the test cases are confirmed by the testers, they are stored in the case database and sent to the server-side case preprocessing module via the client.

[0128] Step 3, the test case preprocessing module, filters the test cases written by the testers using keywords, captures the types of data required for the test cases, and searches the test data database.

[0129] Step 4: If the required data cannot be found in the test database, the data bank module will return an empty result set, and the test runner will directly use the test data entered by the tester to run the test case. If the required data is found in the test database, the data bank module will return the optimal result set according to the data validity weight, and the request receiver will reassemble the message after receiving the dataset and initiate the interface call.

[0130] Step 7: After the test case is completed, compare it with the expected results entered by the tester to determine whether the test case has been successfully executed.

[0131] Step 8.0 If the case validation passes, increase the validity weight of the case and the validity weight of the data used in the case bank algorithm according to the case validity weight calculation method and the test data validity weight calculation method. If the case validation fails, the error information needs to be sent to the error set (Fail List) for judgment.

[0132] Step 8.1 If the problem is environmental, do not update the case validity weight and test data validity weight. Rerun the case. If the case still fails due to environmental issues after three reruns, do not update the case validity weight and test data validity weight. The case verification result is recorded as a failure in the test report.

[0133] Step 8.2 If the problem is with the data, increase the validity weight of the case and decrease the validity weight of the data used in the case bank algorithm according to the case validity weight calculation method and the test data validity weight calculation method.

[0134] Step 8.3 If the problem is a program issue, increase the validity weight of the case and the validity weight of the data used in the case bank algorithm according to the case validity weight calculation method and the test data validity weight calculation method.

[0135] Step 9 generates a test report.

[0136] The following section details a no-code automated page testing system, such as... Figure 14 As shown.

[0137] Test case generation

[0138] The test case generation module in this disclosure is divided into three sub-modules: test page entry, test step entry, and test case search. Testers first search in the search module using "tested transaction + test points" as the criteria. If no results are found or re-entry is required, the tester proceeds to the test page entry module. In this module, testers enter the test page URL and click the "Extract Page Elements" button to obtain the XPath of all page elements. After obtaining the XPath, they click "Complete" to enter the test step entry module. If the test involves multiple pages, testers need to obtain the page elements page by page. After obtaining the XPath, they click "Complete" to enter the test case recording module. In the test case entry module, testers first need to input the test points, test steps, and expected results for the test case. The test steps require selecting the pages to be operated on and the page elements to be operated on for each page, and specifying the actions to be performed on each page element.

[0139] Case preprocessing

[0140] The case preprocessing in this disclosure is mainly divided into two sub-modules: test data search and natural language parsing.

[0141] Natural language processing uses the open-source software LTP (Language Technology Platform) for Chinese semantic analysis and extracts key information from the test data. Search criteria for test data are generated based on the key information extracted from the test points entered by the testers.

[0142] Case Execution

[0143] In this disclosure, the test case execution module is divided into three sub-modules: test case execution, result judgment, and error classification. Test case execution uses Selenium + Testng for test case scheduling and execution. The execution results of failed test cases are sent to the error judgment module for comparison with error set keywords pre-entered by the testers to determine the cause of the test case failure.

[0144] Case Bank

[0145] In this disclosure, the case bank is divided into test case screening, test data screening, test case validity weight update, and test data validity weight update. Test case screening is to filter the case library according to the "transaction + test points" input by the testers and sort the test results case validity weights from high to low and return them. Test data screening is to filter the test database according to the keywords obtained by the natural language parsing module and obtain the data with the highest validity weight to generate the test data result set. The test case validity weight (Effectiveness of TestCase, ETC) is based on the number of test runs T (Times) and the number of successful runs PT (Passed Times). Case verification is considered successful if the case fails due to data or program problems. Case verification failure due to environmental problems does not update the case validity weight. The last successful run date LPD (Last Passed Date), last run time LPT (Last Passed Time), current date (Run Date), and current time RT (Run Time) are used. When the case is run for the first time, LPD = RD and LPT = RT, and it is calculated according to formula (1).

[0146]

[0147] The Effectiveness of Test Data (ETD) is calculated based on the number of times the test data has been used (T), the number of times the test case has been verified (PT), the last successful run date (LPD), the last successful run time (LPT), the current run date (Run Date), and the current run time (RT). When the data is used for the first time, LPD = RD and LPT = RT. The calculation is performed according to formula (2). However, the Effectiveness of Test Data is not updated if the test case fails to run due to environmental issues.

[0148]

[0149] Based on the above-described no-coding automatic page testing method, this disclosure also provides a no-coding automatic page testing device 10. The following will be combined with... Figures 15-21 The automatic page testing device 10 without encoding is described in detail.

[0150] Figure 15 A schematic block diagram of a codeless automatic page testing apparatus 10 according to an embodiment of the present disclosure is shown.

[0151] The uncoded automatic page testing device 10 includes a first acquisition module 1, a second acquisition module 2, a testing module 3, a generation module 4, and a configuration module 5.

[0152] First acquisition module 1 is used to perform operation S210: acquire test cases corresponding to the test points, wherein the test cases include page elements and test steps.

[0153] The second acquisition module 2 is used to perform operation S220: acquire test data corresponding to the page element.

[0154] Test module 3 is used to perform operation S230: test page elements and test data according to the test steps, and obtain test results.

[0155] Generation module 4 is used to perform operation S240: generate a test report based on the test results.

[0156] Configuration module 5 is used to perform operation S250: based on the test results, configure the case weight value of the test case and the data weight value of the test data.

[0157] Figure 16 A schematic block diagram of a first acquisition module 1 according to an embodiment of the present disclosure is shown. The first acquisition module 1 includes a first search unit 11 and a first selection unit 12.

[0158] The first search unit 11 is used to search the first database for test cases corresponding to the transaction name and test points in response to the transaction name and test points entered by the tester.

[0159] The first selection unit 12 is used to select a test case based on the case weight value when a test case corresponding to the transaction name and test point is found.

[0160] Figure 17 A schematic block diagram of the second acquisition module 2 according to an embodiment of the present disclosure is shown. The second acquisition module 2 includes a second search unit 21 and a second selection unit 22.

[0161] The second search unit 21 is used to search the second database for test data corresponding to the page elements of the selected test case.

[0162] The second selection unit 22 is used to select test data according to the data weight value when test data corresponding to the page element is found.

[0163] Figure 18 A schematic block diagram of the configuration module 5 according to an embodiment of the present disclosure is shown. Test results include whether the test case runs successfully or fails. The configuration module 5 may include an update unit 51 or a configuration unit 52.

[0164] When the test result indicates that the test case has passed, the update unit 51 increases the case weight value of the test case and updates it to the first database; and increases the data weight value of the test data and updates it to the second database.

[0165] When the test result indicates a test case execution error, such as Figure 19 As shown, the uncoded automatic page testing device 10 also includes an analysis device 6, which is used to analyze the reasons for the test case running errors and obtain the error classification results. The configuration unit 52 is used to configure the test case weight value and the test data weight value according to the error classification results.

[0166] Figure 20 A schematic block diagram of a configuration unit 52 according to an embodiment of the present disclosure is shown. Error classification results include environmental problems, data problems, or program problems. The configuration unit 52 includes an update element 521.

[0167] When the error classification result is an environmental problem, the page elements and test data are tested m times according to the test steps, where m is an integer greater than or equal to 1. If the test result is still a case execution error each time and the error classification result is an environmental problem, the update element 521 is used to keep the case weight value of the test cases in the first database unchanged; and to keep the data weight value of the test data in the second database unchanged.

[0168] When the misclassification result is a data problem, the update element 521 is used to increase the case weight value of the test case and update it to the first database; and to decrease the data weight value of the test data and update it to the second database.

[0169] When the error classification result is a program problem, the update element 521 is used to increase the case weight value of the test case and update it to the first database; and to increase the data weight value of the test data and update it to the second database.

[0170] Figure 21 A schematic block diagram of the configuration unit 52 according to an embodiment of the present disclosure is shown. Test results include whether the test case runs successfully or fails. When the test result is a test case error, the method further includes: analyzing the cause of the test case error to obtain an error classification result, which may include environmental problems, data problems, or program problems. The configuration unit 52 includes a computing element 522.

[0171] When a test case runs successfully, the calculation element 522 calculates and updates the test case weight value based on the total number of test case runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time; and calculates and updates the test data weight value based on the total number of test data runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time. A successful test case run includes a test result indicating that the test case runs successfully, and a test result indicating that the test case runs incorrectly and the error classification result includes data problems or program problems.

[0172] According to the codeless automatic page testing device 10 of this disclosure, after acquiring test cases and test data, it can test the page elements of the test cases and the test data according to the test steps to obtain test results. On the one hand, based on the test results, a test report can be generated. Through the test report, testers can know the operation status of the test and the validity of the test cases and the test data. In addition, the test report can also be stored as experience information for subsequent tests. On the other hand, based on the test results, the case weight value of the test cases and the data weight value of the test data can be configured. By configuring the case weight value and the data weight value, the test cases and test data can be automatically maintained, reducing maintenance costs, and improving the readability and reusability of the test cases and test data.

[0173] Furthermore, according to embodiments of this disclosure, any multiple modules among the first acquisition module 1, the second acquisition module 2, the testing module 3, the generation module 4, and the configuration module 5 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functionality of one or more of these modules can be combined with at least some of the functionality of other modules and implemented in one module.

[0174] According to embodiments of this disclosure, at least one of the first acquisition module 1, the second acquisition module 2, the test module 3, the generation module 4, and the configuration module 5 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these.

[0175] Alternatively, at least one of the first acquisition module 1, the second acquisition module 2, the test module 3, the generation module 4, and the configuration module 5 can be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0176] Figure 22 A block diagram schematically illustrates an electronic device suitable for implementing the above-described method according to an embodiment of the present disclosure.

[0177] like Figure 22As shown, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0178] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0179] According to embodiments of this disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0180] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0181] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0182] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods of the embodiments of this disclosure.

[0183] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0184] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0185] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0186] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0187] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0188] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0189] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A no-coding automatic page testing method, characterized in that, include: Obtain test cases corresponding to the test points, wherein the test cases include page elements and test steps; Obtain the test data corresponding to the page element; The page elements and the test data are tested according to the test steps described above to obtain test results. Based on the test results, generate a test report; and Based on the test results, configure the case weight value of the test case and the data weight value of the test data. The test results include whether the test case runs successfully or fails. When the test result is a test case error, the method further includes: analyzing the cause of the test case error to obtain an error classification result, which includes environmental issues, data issues, or program issues. The step of configuring the test case weight value and the test data weight value based on the test results includes: configuring the test case weight value and the test data weight value based on the error classification result. When the error classification result is an environmental problem, the test steps for the page elements and the test data are repeated m times, where m is an integer greater than or equal to 1. If the test result is still a case execution error each time, and the error classification result is an environmental problem, the case weight value of the test case and the data weight value of the test data are configured according to the error classification result, including: Keep the case weight values ​​of the test cases in the first database unchanged; and Keep the data weight values ​​of the test data in the second database unchanged. When the misclassification result indicates a data problem, configuring the case weight value of the test case and the data weight value of the test data based on the misclassification result includes: Increase the case weight value of the test cases and update it in the first database; and Reduce the data weight value of the test data and update it in the second database. When the error classification result is a program problem, configuring the case weight value of the test case and the data weight value of the test data according to the error classification result includes: Increase the case weight value of the test cases and update it in the first database; and Increase the data weight value of the test data and update it to the second database.

2. The method according to claim 1, characterized in that, The test cases corresponding to the acquisition and testing points include: In response to the transaction name and test points entered by the tester, search the first database for test cases corresponding to the transaction name and test points; and When a test case corresponding to the transaction name and the test point is found, the test case is selected according to the case weight value.

3. The method according to claim 2, characterized in that, The process of obtaining the test data corresponding to the page element includes: Search the second database for test data corresponding to the page element of the selected test case; and When test data corresponding to the page element is found, the test data is selected based on the data weight value.

4. The method according to claim 3, characterized in that, When the test result indicates that the test case has passed, the step of configuring the test case weight value and the test data weight value based on the test result includes: Increase the case weight value of the test cases and update it in the first database; and Increase the data weight value of the test data and update it to the second database.

5. The method according to claim 1, characterized in that, When the test case runs successfully, based on the test results, configure the case weight value of the test case and the data weight value of the test data, including: The test case weight value is calculated and updated based on the total number of runs, the number of successful runs, the last successful run date, the last run time, the current date, and the current time; and The data weight value of the test data is calculated and updated based on the total number of runs, the number of successful runs, the date of the last successful run, the time of the last run, the current date, and the current time. The successful execution of the test case includes a test result indicating that the test case has passed, and a test result indicating that the test case has an error and the error classification result includes data problems or program problems.

6. The method according to claim 1, characterized in that, When the test result indicates that the test case has passed, the test report includes information indicating that the test case has passed. When the test result indicates a test case execution error, the test report includes test case execution error information.

7. A code-free automatic page testing device, characterized in that, include: The first acquisition module is used to acquire test cases corresponding to the test points, wherein the test cases include page elements and test steps; The second acquisition module is used to acquire test data corresponding to the page element. The testing module is used to perform tests on the page elements and the test data according to the test steps, and obtain test results; A generation module, configured to generate a test report based on the test results; and The configuration module is used to configure the case weight values ​​of the test cases and the data weight values ​​of the test data based on the test results. The test results include whether the test case runs successfully or fails. When the test result is a test case error, the cause of the error is analyzed to obtain an error classification result. The error classification result includes environmental issues, data issues, or program issues. The step of configuring the test case weight value and the test data weight value based on the test results includes: configuring the test case weight value and the test data weight value based on the error classification result. When the error classification result is an environmental problem, the test steps for the page elements and the test data are repeated m times, where m is an integer greater than or equal to 1. If the test result is still a case execution error each time, and the error classification result is an environmental problem, the case weight value of the test case and the data weight value of the test data are configured according to the error classification result, including: Keep the case weight values ​​of the test cases in the first database unchanged; and Keep the data weight values ​​of the test data in the second database unchanged. When the misclassification result indicates a data problem, configuring the case weight value of the test case and the data weight value of the test data based on the misclassification result includes: Increase the case weight value of the test cases and update it in the first database; and Reduce the data weight value of the test data and update it in the second database. When the error classification result is a program problem, configuring the case weight value of the test case and the data weight value of the test data according to the error classification result includes: Increase the case weight value of the test cases and update it in the first database; and Increase the data weight value of the test data and update it to the second database.

8. An electronic device, characterized in that, include: One or more processors; One or more memories are provided for storing executable instructions that, when executed by the processor, implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores executable instructions that, when executed by a processor, implement the method according to any one of claims 1 to 6.

Images