Test result data verification method and device, equipment and storage medium

Through configuration processing and pre-established case expected result baseline numbers, the test result data is checked, which solves the problem of high data verification in automated tests, and achieves efficient and accurate test result verification and system iterative adaptability.

CN118916291APending Publication Date: 2024-11-08CHINA MERCHANTS BANK
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202411130478.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-16
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

During the automated testing process, the data verification of the test result is difficult, the system logic is complex, and there are many data tables, which leads to increased time and operational difficulty.

Method used

By configuring the test result data and verifying based on pre-established case expectation results baseline numbers, the verification process is simplified using common data comparison components to ensure consistency and applicability of results.

Benefits of technology

It simplifies the difficulty of checking automated test results, reduces time costs, improves work efficiency, ensures the accuracy and consistency of test results, and adapts to system iteration and modified functional stability verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916291A_ABST
    Figure CN118916291A_ABST
Patent Text Reader

Abstract

The invention discloses a test result data verification method and device, equipment and a storage medium, and relates to the technical field of automated test.The method comprises the steps that test result data are obtained through a public data comparison component, configuration processing is conducted on the test result data, and the test result data obtained after configuration is completed are obtained, the automatic verification process is simplified, the data reference entry is unified, and the applicability is enhanced; and on the basis of the pre-established case expected result baseline number, the configured test result data is verified to obtain the verification result, so that the consistency of the cross-iteration test result and the stability of the verification function are ensured, the verification time is greatly shortened, and the test efficiency and the working efficiency are remarkably improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of automated testing technology, and in particular to a test result data verification method, device, equipment and storage medium. Background Art

[0002] Due to the complexity of some system logic, it is difficult to verify the test result data during the automated testing process. To check the logic of each test case one by one is equivalent to duplicating the system implementation logic, and the cost of verifying the automated test result data is extremely high. In addition, the system involves many data tables, and the data tables are frequently read and written during the test result data verification process, which consumes a lot of time. Processing the data table comparison separately for each test case will also increase the difficulty of operating the test case. Summary of the invention

[0003] The main purpose of this application is to provide a test result data verification method, device, equipment and storage medium, aiming to solve the technical problem of how to ensure the test quality while optimizing the test cycle.

[0004] To achieve the above purpose, the present application proposes a test result data verification method, the method comprising:

[0005] Acquire test result data, and perform configuration processing on the test result data to obtain configured test result data;

[0006] Based on the pre-established case expected result baseline number, the configured test result data is verified to obtain a verification result.

[0007] In one embodiment, the step of configuring the test result data includes:

[0008] Get the test data table corresponding to the test result data;

[0009] Based on the type of the test data table, identifying key field information;

[0010] Configure preset verification tags for key fields in the test data table.

[0011] In one embodiment, before the step of verifying the configured test result data based on the pre-established case expected result baseline number to obtain the verification result, the following steps are further included:

[0012] Acquire test case information, wherein the test case information includes a case name and a case expected result baseline number;

[0013] The case name is associated with the case expected result baseline number to obtain a pre-established case expected result baseline number, and the pre-established case expected result baseline number is stored in a test data table.

[0014] In one embodiment, the step of verifying the configured test result data based on the pre-established case expected result baseline number to obtain the verification result includes:

[0015] According to the pre-established case expected result baseline number, determine whether the currently executed test case exists in the test data table;

[0016] If yes, it means that the currently executed test case has been recorded in the test data table;

[0017] If not, then new record information is created in the currently executed test case to store the new case expected result baseline number, wherein the field of the new case expected result baseline number is set to a null value.

[0018] In one embodiment, the step of determining whether the currently executed test case exists in the test data table according to the pre-established case expected result baseline number includes:

[0019] According to the pre-established case expected result baseline number, obtain the case name corresponding to the pre-established case expected result baseline number;

[0020] Determine whether the case name of the currently executed test case is consistent with the case name corresponding to the pre-established case expected result baseline number.

[0021] In one embodiment, after the step of "if yes, it indicates that the currently executed test case has been recorded in the test data table", the method further includes:

[0022] Identify key fields in the currently executing test case;

[0023] Verify whether the key fields in the currently executed test case are consistent with the key fields configured with preset verification tags in the test data table;

[0024] If they are inconsistent, the key fields in the currently executed test case are deleted.

[0025] In one embodiment, the step of obtaining test result data includes:

[0026] Establish running records to store test result data during the test process;

[0027] Setting a run key value based on the test result data;

[0028] By using the run key value, when the test case is run, the test result data is obtained.

[0029] In addition, to achieve the above-mentioned purpose, the present application also proposes a test result data verification device, the test result data verification device comprising:

[0030] A configuration module, used to obtain test result data, and perform configuration processing on the test result data to obtain configured test result data;

[0031] The verification module is used to verify the configured test result data based on the pre-established case expected result baseline number to obtain a verification result.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a test result data verification device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the test result data verification method described above.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the test result data verification method described above are implemented.

[0034] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the test result data verification method described above are implemented.

[0035] The embodiments of the present application provide a test result data verification method, apparatus, equipment and storage medium, which obtains test result data through a common data comparison component, and performs configuration processing on the test result data to obtain configured test result data. The use of the common data comparison component simplifies the difficulty of automated result verification, and facilitates data reference and subsequent maintenance and unification. The applicability is improved through the configuration processing of data comparison. Based on a pre-established case expected result baseline number, the configured test result data is verified to obtain a verification result. The pre-established case expected result baseline number is used to ensure the consistency of results between different test executions. Even after multiple iterations and modifications, the system can verify the stability and correctness of the function by comparing the old and new results. By verifying the configured test result data based on the case expected result baseline number, the difficulty of verifying the test results in the automated testing process is simplified, the time cost is reduced, and the work efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0038] Figure 1 A flowchart of the first embodiment of the test result data verification method of the present application is provided;

[0039] Figure 2 A flowchart of the second embodiment of the test result data verification method of the present application is provided;

[0040] Figure 3 A flowchart of the third embodiment of the test result data verification method of the present application is provided;

[0041] Figure 4 A brief flowchart of the test result data verification method provided in Example 1 of the present application;

[0042] Figure 5 This is a schematic diagram of the module structure of the test result data verification device of the embodiment of the present application;

[0043] Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the test result data verification method in the embodiment of the present application.

[0044] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0045] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0046] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0047] The main solution of the embodiment of the present application is: to obtain test result data, and to perform configuration processing on the test result data to obtain configured test result data; based on a pre-established case expected result baseline number, to verify the configured test result data to obtain a verification result.

[0048] In this embodiment, for ease of description, the following description is made with the public data comparison component as the execution subject.

[0049] Due to the complexity of some system logic, it is difficult to verify the test result data during the automated testing process. To check the logic of each test case one by one is equivalent to duplicating the system implementation logic, and the cost of verifying the automated test result data is extremely high. In addition, the system involves many data tables, and the data tables are frequently read and written during the test result data verification process, which consumes a lot of time. Processing the data table comparison separately for each test case will also increase the difficulty of operating the test case.

[0050] The present application provides a solution, which obtains test result data through a common data comparison component, and performs configuration processing on the test result data to obtain the configured test result data. The use of the common data comparison component simplifies the difficulty of automated result verification, facilitates data reference and subsequent maintenance and unification, reduces the case data comparison and maintenance costs, and improves applicability through configurable processing of data tables and fields for data comparison; based on the case expected result baseline number, the configured test result data is verified to obtain the verification result; through the case expected result baseline number, the result consistency between different test executions is ensured; even after multiple iterations and modifications, the system can verify the stability and correctness of the function by comparing the old and new results; the data table can be dynamically expanded, and if it is necessary to modify the data table comparison and add business field comparison, it only needs to modify the configuration and re-access the new case expected result baseline, thereby improving flexibility.

[0051] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes a mobile phone as an example to illustrate this embodiment and the following embodiments.

[0052] Based on this, the present application embodiment provides a test result data verification method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the test result data verification method of the present application.

[0053] In this embodiment, the test result data verification method includes steps S10 to S20:

[0054] Step S10, obtaining test result data, and performing configuration processing on the test result data to obtain configured test result data;

[0055] It is understandable that since the test framework needs to flexibly adjust the scope and details of data comparison according to different business scenarios and requirements, performing step S10 can avoid test rigidity and maintenance difficulties caused by hard coding, thereby improving the applicability and flexibility of the test framework.

[0056] In a feasible implementation, step S10 may include steps A11 to A13:

[0057] Step A11, establishing a running record for storing test result data during the test process;

[0058] Optionally, an automated operation record is established, which is used to store test result data during the automated test operation, that is, detailed information of the test process, including but not limited to the ID and name of the test case, environment configuration information, business number, cluster, etc.

[0059] Establish a running record to save the test result data, ensure that the history of each test execution can be tracked and analyzed, and provide a basis for subsequent test result verification.

[0060] Step A12, setting a run key value based on the test result data;

[0061] It should be noted that the run key value is used as an index or identifier to uniquely identify the result of a test execution.

[0062] By setting the run key value, even if the test case is executed multiple times, the detailed results of a specific execution can be quickly located through the run key value, which is crucial for quickly comparing different test results in a complex test environment.

[0063] Step A13, obtaining test result data through the running key value when the test case is running.

[0064] Optionally, when the test case is run again, the previously stored test result data can be immediately obtained by running the key value, which is convenient for comparing the current test results with historical results. For example, in regression testing, test engineers may need to compare the performance of the new and old versions of the software under the same test case. Running the key value makes the comparison process simple and quick. In addition, when a test fails, searching for previous test records by running the key value can help quickly locate the problem and improve debugging efficiency.

[0065] In this implementation, by setting the running key value corresponding to the test result data, the test result data generated during the test process can be obtained, and the organization, efficiency and reliability of the test process can be significantly improved.

[0066] In another feasible implementation, step S10 may include steps B11 to B13:

[0067] Step B11, obtaining a test data table corresponding to the test result data;

[0068] Optionally, the test result data is obtained by accessing a database storing the test result data, wherein the test result data includes but is not limited to a test case ID, a test execution time, a test result, a test environment information, and the like.

[0069] Then, the test result data is classified, and for different categories of test result data, the corresponding test data tables are queried, and these test data tables are used to store the test result data of the corresponding categories. For example, the test result data can be classified into functional test result data, performance test result data, safety test result data, etc., then the corresponding data lists are functional test result data tables, performance test result data tables, and safety test result data tables. Among them, each data table contains enough fields to store the test result data related to the classification.

[0070] Step B12, identifying key fields based on the type of the test data table;

[0071] Optionally, key field information is identified according to the type of test data, wherein key fields are usually fields that have a significant impact on test results, such as test case ID, input name, case name, case steps, cluster, configuration environment and other information.

[0072] Step B13, configuring preset verification tags for key fields in the test data table.

[0073] After identifying the key field information in various test data tables, determine the preset verification labels. It should be noted that in this embodiment, the preset verification labels are used to distinguish which key fields need to be verified and which key fields do not need to be verified. The "key fields that need to be verified" are used as preset verification labels and are marked on the key fields. In the subsequent test result data verification process, the system can automatically identify the key fields that need to be verified according to these preset verification labels and perform automatic verification. This method can improve the efficiency and accuracy of verification and ensure the validity of the test results.

[0074] Through the above steps, the test result data is obtained by running key values, which enables rapid retrieval and automated processing of test data, helping to improve the response speed and decision-making efficiency of the test. By verifying the tags, data that does not meet the preset rules can be automatically identified and marked to ensure data accuracy and consistency during the verification process.

[0075] Step S20, based on the pre-established case expected result baseline number, the configured test result data is verified to obtain a verification result.

[0076] It can be understood that in order to ensure that the execution results of the test case are consistent with the predefined expected results, and while ensuring the test quality, simplify the operational difficulty of processing the test results and improve the accuracy and efficiency of data verification, therefore, in this embodiment, a common data comparison component is used to compare the configured test result data with the expected results pointed to by the pre-established case expected result baseline number item by item, and generate a verification result based on the results of the data comparison.

[0077] In a feasible implementation, step S20 may include steps S21 to S23:

[0078] Step S21, judging whether the currently executed test case exists in the test data table according to the pre-established case expected result baseline number;

[0079] It should be noted that the baseline of the expected results of the test case represents the correct results that the test case is expected to produce under specific conditions. These expected results will be recorded in the test data table or test case document.

[0080] In addition, it should be noted that before this step, the case expected result baseline number has been associated with the case name of the successfully executed test case. Therefore, in this step, you only need to use the case name associated with the case expected result baseline number to check whether the case name of the currently executed test case is recorded in the test data table.

[0081] Specifically, in a feasible implementation manner, step S21 may include steps C11 to C12:

[0082] Step C11, based on the previously established case expected result baseline number, obtain the corresponding case name;

[0083] Optionally, the public data comparison component uses the case expected result baseline number as an index to find the case name associated with it in the test data table, where the test data table stores detailed information of all test cases, including the test case name and the baseline number of the case expected result.

[0084] Specifically, first, the public data comparison component identifies the case expected result baseline number of the currently executed test case. Then, by querying the database storing the test case information, the public data comparison component retrieves the corresponding case name according to the baseline number.

[0085] Step C12, determining whether the case name of the currently executed test case is consistent with the case name of the test case.

[0086] Optionally, after completing step C11, the public data comparison component obtains the case name of the test case expected to be executed, that is, the case name of the test case associated with the case expected result baseline number. In this step, the public data comparison component compares the case name of the test case associated with the case expected result baseline number with the case name of the test case currently being executed to verify whether the two are completely matched.

[0087] Step S22: If yes, it means that the currently executed test case has been recorded in the test data table;

[0088] Optionally, if the case name of the test case currently being executed is consistent with the case name of the test case associated with the case expected result baseline number, then it means that the expected results and related information of the test case currently being executed have been previously recorded and saved, and the subsequent test process can continue, including verifying the test results and recording the status of the test execution.

[0089] Step S23: If not, then create new record information in the currently executed test case to save the new case expected result baseline number, wherein the field of the new case expected result baseline number is set to a null value.

[0090] Optionally, if the case name of the test case currently being executed is inconsistent with the case name of the test case associated with the case expected result baseline number, it means that there is no record of the currently executed test case in the test data table, and then a new record is created, wherein the new record entry contains basic information of the test case, such as the case name. For the case expected result baseline number field, since there is no expected result at present, it is set to a null value or a default value. The new record is saved in the test data table so that it can be referenced during subsequent test execution and result verification.

[0091] Through the above steps, by using public data comparison components for automated verification, the difficulty of verifying test results is simplified, the time and labor cost of manual verification are reduced, the efficiency of the testing process is improved, and the verification based on the baseline number of the expected case results ensures the accuracy of the test results. Even after multiple iterations and modifications of the system, the stability and correctness of the function can be verified by comparing the old and new results.

[0092] Through the above-mentioned embodiment method, the test result data is obtained through the common data comparison component, and the test result data is configured to obtain the configured test result data, which simplifies the automated verification process, unifies the data reference entry, and enhances applicability; establishes and stores the case expected result baseline number to ensure the consistency of cross-iteration test results and verify functional stability; based on the case expected result baseline number, the configured test result data is verified to obtain the verification result, which greatly reduces the verification time and significantly improves the test efficiency and work effectiveness.

[0093] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 Before step S20, the test result data verification method further includes steps S201 to S202:

[0094] Step S201, obtaining test case information, wherein the test case information includes a case name and a case expected result baseline number;

[0095] It should be noted that the case expected result baseline number is an identifier used to uniquely identify a set of predefined, expected test results, usually pointing to a data set that contains the results that the test case should produce under specific conditions.

[0096] Optionally, automated case information is established, wherein the automated case information includes but is not limited to information such as a test case ID, a case name, a case expected result baseline number, etc., and the automated case information is stored in a database.

[0097] Step S202, associating the case name with the case expected result baseline number to obtain a pre-established case expected result baseline number, and storing the pre-established case expected result baseline number in a test data table.

[0098] After the case name and the case expected result baseline number are obtained through step S201, ensure that the case name corresponds to the case expected result baseline number, that is, each test case has a specific case expected result baseline number. Then, create a record in the database, which contains the case name and the associated case expected result baseline number. Once the case name is associated with the case expected result baseline number, the pre-established case expected result baseline number can be obtained, and then the pre-established case expected result baseline number is stored in the test data table.

[0099] Through the above-mentioned embodiment method, the case name is associated with the case expected result baseline number and stored in the test data table, ensuring that each test case has a clear expected result, which facilitates the public data comparison component to automatically compare the actual result with the expected result after execution, thereby quickly determining whether the test result passes.

[0100] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 3 After step S22, the test result data verification method further includes steps S221 to S223:

[0101] Step S221, identifying key fields in the currently executed test case;

[0102] Optionally, when determining that the current test case exists in the test data standard, the public data comparison component re-identifies whether the index position on the key field information in the current test case is marked with a preset verification tag to facilitate subsequent field comparison work.

[0103] Step S222, verifying whether the key fields in the currently executed test case are consistent with the key fields in the test data table that are configured with preset verification tags;

[0104] Optionally, the key field configured with a preset verification tag obtained in step B13 refers to the key field marked with "need to be verified" field information in the test data table. Once the key field in the currently executed test case is identified, it is checked whether the key field in the currently executed test case matches the key field marked with the preset verification tag in the test data table, that is, whether the key field index position of the currently executed test case is marked with "need to be verified" field information.

[0105] Step S223: If there is inconsistency, the key fields in the currently executed test case are deleted.

[0106] Optionally, if the verification result is that the key fields of the currently executed test case are inconsistent with the key fields marked with preset verification tags in the test data table, the key fields that do not meet the conditions in the currently executed test case are deleted or ignored to obtain the remaining, consistent key field information, and a new case expected result baseline number is generated based on these remaining, consistent key field information. Finally, the test result data is re-verified using the newly generated case expected result baseline number. This verification will be based on the updated test case and case expected results, with the purpose of confirming that all modifications have been correctly reflected in the test process and no new inconsistencies have been introduced.

[0107] Through the above-mentioned embodiment method, when the key fields of the test case change or need to be updated, it is only necessary to modify the configuration and re-access the new expected result baseline to ensure that the test can adapt to the latest requirements or changes. Ignoring or deleting key fields that do not meet the conditions can reduce unnecessary test runs, save resources and time, and make the testing process more efficient. By continuously verifying and updating the expected result baseline, it can be ensured that the test cases cover all necessary scenarios and that the expected results in each case are accurate.

[0108] For example, in order to help understand the implementation process of the test result data verification method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 4 , Figure 4 A brief flow chart of a test result data verification method is provided, specifically:

[0109] In the automated test case, the public data comparison component is called to automatically compare the test result data. The component logic is as follows:

[0110] First, input the test case to be verified into the public data comparison component, obtain the test result data to be verified in the test case, which includes but is not limited to cluster, configuration environment, business number, case name and case steps, and perform configuration processing on this information, and store the source information of the test result data to be verified, which can be changed with system changes. In the configuration processing process, the test result data to be verified in the test case is marked with the field information of "need to be verified".

[0111] Then, obtain the test result data of the successfully executed test case, identify the information of its key fields, where the information of the key fields includes but is not limited to case ID, case name, and case expected result baseline number, and associate the case name and case expected result baseline number.

[0112] Next, the test result data to be verified in the currently executed test case is compared with the test result data of the successfully executed test case to check whether the test result data in the test case to be verified meets the expected result, that is, whether the test result data in the test case to be verified exists in the database. Among them, by using the case expected result baseline number of the test result data of the successfully executed test case as the basis for comparison, it can be judged whether the test result data in the test case to be verified meets the expected test result.

[0113] If the test result data to be verified does not meet the baseline number of the expected result of the case, a new record is created, wherein the new record entry contains the basic information of the test case, such as the case name. For the expected result baseline number field of the case, since there is no expected result at present, it is set to a null value or a default value. And based on the new record entry, a new batch of test result data to be verified is obtained from the database, and the showDictDiff (display dictionary difference) function is used to compare the difference between the new and old data batches. Then, according to the new batch of test result data to be verified, the corresponding business SQL (Structured Query Language, database language) configuration is obtained, and then, the simulated SQL statement is used to query the test data source to be verified in the cluster, and the test data to be verified is obtained for comparison, and the data that is not marked with "need to be verified" on the fields in the test data to be verified is eliminated and ignored. After completing the data processing, a new batch of test result data is generated. Finally, the new batch of test result data is inserted into the specified MongoDB (distributed file storage database) table.

[0114] Similarly, if the test result data to be verified meets the expected result baseline number of the case, the data configuration processing is completed directly according to the case name and key field information of the test result data to be verified, and then the simulated SQL statement is used to query the test data source to be verified in the cluster, obtain the test data to be verified for comparison, and exclude the data that is not marked with "need to be verified" on the fields in the test data to be verified. After completing the data processing, a new batch of test result data is generated. Finally, the new batch of test result data is inserted into the specified MongoDB (distributed file storage database) table.

[0115] Through the above-mentioned implementation scheme, a common method for complex logic processing is provided, which is suitable for automated data comparison of each test case in the system. By extracting common data comparison components, maintenance and management are facilitated, thereby reducing the maintenance cost of case data comparison. By simply updating the configuration and re-storing the benchmark data (i.e., the "baseline"), changes in data comparison requirements caused by system changes can be easily responded to, ensuring that the test cases can continue to reflect the latest business logic and data structure, thereby maintaining the effectiveness and accuracy of the test.

[0116] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the test result data verification method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0117] This application also provides a test result data verification device, please refer to Figure 5 , the test result data verification device comprises:

[0118] The configuration module 10 is used to obtain test result data and perform configuration processing on the test result data to obtain configured test result data;

[0119] The verification module 20 is used to verify the configured test result data based on the pre-established case expected result baseline number to obtain a verification result.

[0120] The test result data verification device provided by the present application adopts the test result data verification method in the above-mentioned embodiment, which can solve the technical problem of how to ensure the test quality while optimizing the test cycle. Compared with the prior art, the beneficial effects of the test result data verification device provided by the present application are the same as the beneficial effects of the test result data verification method provided by the above-mentioned embodiment, and the other technical features in the test result data verification device are the same as the features disclosed in the above-mentioned embodiment method, which will not be repeated here.

[0121] The present application provides a test result data verification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the test result data verification method in the above-mentioned embodiment one.

[0122] Reference below Figure 6 , which shows a schematic diagram of the structure of a test result data verification device suitable for implementing the embodiment of the present application. The test result data verification device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The test result data verification device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0123] like Figure 6As shown, the test result data verification device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the test result data verification device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the test result data verification device to communicate wirelessly or wired with other devices to exchange data. Although the test result data verification device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided alternatively.

[0124] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0125] The test result data verification device provided by the present application adopts the test result data verification method in the above embodiment, which can solve the technical problem of how to ensure the test quality while optimizing the test cycle. Compared with the prior art, the beneficial effects of the test result data verification device provided by the present application are the same as the beneficial effects of the test result data verification method provided by the above embodiment, and the other technical features in the test result data verification device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0126] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0127] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0128] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the test result data verification method in the above-mentioned embodiment.

[0129] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer 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. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0130] The computer-readable storage medium may be included in the test result data verification device; or may exist independently without being assembled into the test result data verification device.

[0131] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the test result data verification device, the test result data verification device: obtains test result data, and performs configuration processing on the test result data to obtain configured test result data; establishes and stores a case expected result baseline number; based on the case expected result baseline number, verifies the configured test result data to obtain a verification result.

[0132] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0133] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0134] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0135] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned test result data verification method, and can solve the technical problem of how to optimize the test cycle while ensuring the test quality. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the test result data verification method provided by the above-mentioned embodiment, and will not be repeated here.

[0136] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned test result data verification method when executed by a processor.

[0137] The computer program product provided by the present application can solve the technical problem of how to ensure the test quality while optimizing the test cycle. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the test result data verification method provided by the above embodiment, which will not be repeated here.

[0138] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A test result data verification method, characterized in that: The method is applied to a public data comparison component, and the method comprises: Acquire test result data, and perform configuration processing on the test result data to obtain configured test result data; Based on the pre-established case expected result baseline number, the configured test result data is verified to obtain a verification result.

2. The method according to claim 1, characterized in that The step of configuring the test result data comprises: Get the test data table corresponding to the test result data; Based on the type of the test data table, identifying key fields; Configure preset verification tags for key fields in the test data table.

3. The method according to claim 1, characterized in that Before the step of verifying the configured test result data based on the pre-established case expected result baseline number to obtain the verification result, the method further includes: Acquire test case information, wherein the test case information includes a case name and a case expected result baseline number; The case name is associated with the case expected result baseline number to obtain a pre-established case expected result baseline number, and the pre-established case expected result baseline number is stored in a test data table.

4. The method according to any one of claims 2 to 3, characterized in that The step of verifying the configured test result data based on the pre-established case expected result baseline number to obtain the verification result includes: According to the pre-established case expected result baseline number, determine whether the currently executed test case exists in the test data table; If yes, it means that the currently executed test case has been recorded in the test data table; If not, then new record information is created in the currently executed test case to store the new case expected result baseline number, wherein the field of the new case expected result baseline number is set to a null value.

5. The method according to claim 4, characterized in that The step of judging whether the currently executed test case exists in the test data table according to the pre-established case expected result baseline number includes: According to the pre-established case expected result baseline number, obtain the case name corresponding to the pre-established case expected result baseline number; Determine whether the case name of the currently executed test case is consistent with the case name corresponding to the pre-established case expected result baseline number.

6. The method according to claim 4, characterized in that If yes, it means that the currently executed test case has been recorded in the test data table, and further includes: Identify key fields in the currently executing test case; Verify whether the key fields in the currently executed test case are consistent with the key fields configured with preset verification tags in the test data table; If they are inconsistent, the key fields in the currently executed test case are deleted.

7. The method according to claim 6, characterized in that The step of obtaining test result data comprises: Establish running records to store test result data during the test process; Setting a run key value based on the test result data; By using the run key value, when the test case is run, the test result data is obtained.

8. A test result data verification device, characterized in that: The test result data verification device comprises: A configuration module, used to obtain test result data, and perform configuration processing on the test result data to obtain configured test result data; The verification module is used to verify the configured test result data based on the pre-established case expected result baseline number to obtain a verification result.

9. A test result data verification device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the test result data verification method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the test result data verification method according to any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Multi-line pattern result matching method and chip testing machine

    CN121522418A

  • Multi-row pattern pin result matching method and chip testing machine

    CN121522419A

  • Site result matching method of multi-row pattern and chip testing machine

    CN121559277A