CN113190465B - Test information processing method, device, equipment and storage medium - Google Patents

Test information processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN113190465B
CN113190465B CN202110589653.8A CN202110589653A CN113190465B CN 113190465 B CN113190465 B CN 113190465B CN 202110589653 A CN202110589653 A CN 202110589653A CN 113190465 B CN113190465 B CN 113190465B
Authority
CN
China
Prior art keywords
test
execution result
test case
tested
sub
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110589653.8A
Other languages
Chinese (zh)
Other versions
CN113190465A (en
Inventor
豆春该
马燕
胡少君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Life Insurance Company of China Ltd
Original Assignee
Ping An Life Insurance Company of China Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Life Insurance Company of China Ltd filed Critical Ping An Life Insurance Company of China Ltd
Priority to CN202110589653.8A priority Critical patent/CN113190465B/en
Publication of CN113190465A publication Critical patent/CN113190465A/en
Application granted granted Critical
Publication of CN113190465B publication Critical patent/CN113190465B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3692—Test management for test results analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/242—Query formulation
    • G06F16/2433—Query languages
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application relates to a test information processing method, a device, equipment and a storage medium, wherein the method comprises the following steps: receiving a test information acquisition request of a system to be tested from electronic equipment, wherein the test information acquisition request comprises a first sub-execution result of a first test case in the system to be tested; if the first execution remark information comprises a label of the system to be tested, acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label; if the first execution remark information does not comprise the label of the system to be tested, acquiring a second sub-execution result of the second test case based on the system identifier of the system to be tested; acquiring test information of the first test case based on a first sub-execution result and a second sub-execution result of the first test case; and sending the test information of the first test case to the electronic equipment. By adopting the application, the efficiency and the accuracy of identifying whether the test case fails to test can be improved.

Description

Test information processing method, device, equipment and storage medium
Technical Field
The application relates to the field of testing, and mainly relates to a test information processing method, device, equipment and storage medium.
Background
With the development of computer technology, software testing work is becoming more and more interesting due to the rapid development of software industry, and there may be a case where multiple testers test the same or different test cases in one system to be tested, and there may be a case where the execution of the test cases fails. The test case fails to test, which easily results in failure of the system to be tested. Therefore, identifying test cases that fail the test is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application provides a test information processing method, a device, equipment and a storage medium, which can improve the efficiency and the accuracy of identifying whether a test case fails to be tested.
In a first aspect, an embodiment of the present application provides a test information processing method, in which:
receiving a test information acquisition request from electronic equipment, wherein the test information acquisition request comprises first execution remark information of a first test case in a system to be tested, the first execution remark information comprises a first sub-execution result of the first test case, the test information acquisition request is used for acquiring the test information of the first test case, and the test information of the first test case comprises indication information of whether the first test case is tested successfully or not;
If the first execution remark information further comprises a label of the system to be tested, acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label; or alternatively
If the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
acquiring test information of the first test case based on the first sub-execution result and the second sub-execution result;
and sending the test information of the first test case to the electronic equipment.
In a second aspect, an embodiment of the present application provides a test information processing apparatus, wherein:
the electronic equipment comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a test information acquisition request from the electronic equipment, the test information acquisition request comprises first execution remark information of a first test case in a system to be tested, the first execution remark information comprises a first sub-execution result of the first test case, the test information acquisition request is used for acquiring the test information of the first test case, and the test information of the first test case comprises indication information of whether the first test case is tested successfully or not;
The execution result obtaining unit is used for obtaining a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label if the first execution remark information also comprises the label of the system to be tested; or if the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
the test information acquisition unit is used for acquiring the test information of the first test case based on the first sub-execution result and the second sub-execution result;
and the sending unit is used for sending the test information of the first test case to the electronic equipment.
In a third aspect, an embodiment of the present application provides a test information processing apparatus including a processor, a memory, a communication interface, and one or at least one program, wherein the one or at least one program is stored in the memory and configured to be executed by the processor, the program including instructions for part or all of the steps as described in the first aspect.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium, wherein the computer readable storage medium stores a computer program, wherein the computer program is configured to implement some or all of the steps as described in the first aspect when executed by a computer.
The implementation of the embodiment of the application has the following beneficial effects:
after the test information processing method, the device, the equipment and the storage medium are adopted, if the test information acquisition request received from the electronic equipment comprises the label of the system to be tested, acquiring a second sub-execution result of a second test case associated with the first test case in the system to be tested based on the label. Otherwise, searching second execution remark information of the second test case based on the system identification of the system to be tested, and acquiring a second sub-execution result of the second test case from the second execution remark information. Thus, the efficiency of acquiring the sub-execution results of the associated test cases can be improved through the tag. And then, based on the first sub-execution result and the second sub-execution result included in the test information acquisition request, acquiring the test information of the first test case, and sending the test information of the first test case to the electronic equipment, so that a user corresponding to the electronic equipment can determine whether the first test case is successfully tested, and the accuracy of acquiring the test information of the first test case can be improved, that is, the accuracy of identifying whether the first test case fails to be improved.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Wherein:
FIG. 1 is a system architecture diagram of a test information processing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a test management system according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of a test information processing method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a test information processing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a test information processing device according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the application, are within the scope of the application in accordance with embodiments of the present application.
The terms first, second and the like in the description and in the claims and in the above-described figures are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
Referring to fig. 1, fig. 1 is a system architecture diagram of a test information processing method according to an embodiment of the present application. As shown in fig. 1, the system includes a server 101, an electronic device 102, and a user 103. The electronic device 102 may be a personal computer (personal computer, PC), a notebook computer or a smart phone as shown in fig. 1, or may be an all-in-one machine, a palm computer, a tablet computer (pad), a smart television playing terminal, a vehicle-mounted terminal or a portable device. The operating system of the electronic device at the PC side, such as an all-in-one machine, may include, but is not limited to, linux system, unix system, windows series system (such as Windows xp, windows 7, etc.), mac OS X system (operating system of apple computer), etc. The operating system of the electronic device of the mobile terminal, such as a smart phone, may include, but is not limited to, an android system, an IOS (operating system of an apple phone), a Window system, and other operating systems.
The server 101 is used to provide test services for the electronic device 102. For example, after the electronic device 102 is connected to the server 101, the server 101 tests the test case in the system to be tested, and the sub-execution result obtained by testing the test case is sent to the electronic device 102, so that the user can obtain the sub-execution result of the test case through the electronic device 102. Or, the server determines the test information of the system to be tested based on the sub-execution results of each test case, and sends the test information to the electronic device 102, so that the user determines whether the system to be tested is tested successfully or not through the electronic device 102. For another example, the electronic device 102 sends the sub-execution result of the test case to the server 101, and the server 101 determines whether the test case is tested successfully based on the sub-execution result, and sends test information indicating whether the test case is tested successfully to the electronic device 102, so that the electronic device 102 determines whether the test case is tested successfully.
The present application is not limited to the number of electronic devices 102 and servers 101, and the electronic devices 102 may communicate with at least one server 101. The server 101 may be a single server or may be a server cluster formed by a plurality of servers. The server 101 may provide at least one database service, and the present application is not limited to the type of server of the database service, and may be Mysql, oracle, PGsql or the like.
Optionally, the server 101 is a database server corresponding to the system to be tested. In particular a database server corresponding to the characteristics of the system to be tested and/or the type of execution result. It can be understood that by selecting the database server corresponding to the system to be tested as a testing tool for testing the system to be tested, the testing efficiency and accuracy can be improved.
Server 101 may also include a local server and a remote server that are locally connected to electronic device 102. It should be noted that the remote server supports the database service type using the local server. It will be appreciated that when the local server uses Mysql for data management, the remote server also uses Mysql for data management.
In the embodiment of the application, the label is information named by a tester for a test scene of the system to be tested. It should be noted that, the test scenario corresponding to the tag is usually a fixed scenario, that is, the test scenario of the system to be tested is difficult to change with the update of the version iteration, or is difficult to change with the state change of the data background interaction. The labels may be numbered according to the name and iteration version of the system to be tested, and the like, and are not limited herein.
The tag may be stored in tag information, which may include, in addition to the tag, a name of the system under test, a scene name, an expected execution result, a structured query language (Structured Query Language, SQL) statement, a query variable, and the like. The scene name is used for describing a complete testing flow of the system to be tested. The expected execution result is an execution result expected by the system to be tested, and may include expected sub-execution results of each test case. The SQL statement is used for inquiring the actual execution result corresponding to the test case. The test variables are used to query data records during the test, which may include data involved in the test, as well as execution results, etc.
The embodiment of the application is not limited to the system to be tested, and can be any system. The system to be tested may include a plurality of functional modules for performing different functions, each of which may correspond to a test case. After the test cases of the system to be tested are uploaded by the testers respectively, the system to be tested can be tested to obtain the execution result of the system to be tested or the execution result of each functional module.
The application does not limit the number of the test cases, and one or more test cases can be adopted, that is, a plurality of electronic devices can test the same or different test cases to obtain corresponding test information. In the embodiment of the application, the first test case can be any test case. The second test case is a test case which is influenced by the first test case or is influenced by the test in the system to be tested. The second test case may be tested by using the electronic device when the first test case is tested, or may be tested by using other electronic devices, which is not limited herein.
The first execution remark information may be execution remark information obtained by testing a first test case of the system to be tested by the electronic device, and may include a first sub-execution result of the first test case and a record of test data related in a test process. The first execution remark information may also include a tag or the like of the system to be tested. In one possible example, if the system to be tested has a tag, the electronic device may add the tag and send the tag as first execution remark information to the server while sending the first sub-execution result of the current test case to the server.
The second sub-execution result may be included in second execution remark information of the second test case with reference to the description of the first sub-execution result. If the system to be tested has a label, the second execution remark information may also include the label of the system to be tested, a record of test data related to the test process of the second test case, and the like.
In the embodiment of the application, the system identifier of the system to be tested is used for searching information of the system to be tested, for example, execution remark information of each test case in the system to be tested and the like.
In the embodiment of the application, the label information, the label and the system identification of the system to be tested can be stored in a memory or a local database of the electronic equipment. The method for storing the label information is not limited, and the label information can be stored according to the iteration period of the system, for example, the label information can be maintained every two weeks through the label management module, or a tester can be notified to store before the system is tested.
In the embodiment of the application, the tag information, the tag and the system identifier of the system to be tested can be uploaded to a server or stored in a block created on the blockchain network. Blockchains are novel application modes of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer. Therefore, the data can be stored in a distributed mode through the blockchain, so that the data security is ensured, and meanwhile, the data sharing of information among different platforms can be realized.
The method for judging whether the system to be tested has the label is not limited, and if any executive remark information comprises the label, the system to be tested can be determined to comprise the label. Or searching the label of the system to be tested from the pre-stored information, if the searching is successful, determining that the system to be tested comprises the label, otherwise, determining that the system to be tested does not comprise the label. Or, the test logic of the system to be tested can be determined according to the test code of the system to be tested, and then whether the system to be tested comprises the tag is determined according to the test logic.
The test code may be found from information stored in the test integrated system, and the like, and is not limited herein. Because the labels are used for indicating that the test scene of the system to be tested is difficult to change along with the updating of the version iteration or is difficult to change along with the state change of the data background interaction, the test codes can be analyzed to determine whether the system to be tested meets the requirements of the labels, if so, the system to be tested is determined to have the labels, and otherwise, the system to be tested is determined to have no labels.
A user may write a test case of a system under test in the electronic device 102 and add a tag of the system under test. And testing the test case through the local server to obtain the sub-execution result of the test case. Then, the local server may send the execution result to the remote server, so that the remote server obtains the test information of the system to be tested based on the sub-execution result and the sub-execution result obtained by the associated test case corresponding to the test case, so as to determine whether the test is successful or not and whether the sub-execution result is correct or not.
Specifically, the electronic device 102 may run a test management system, and the server 101 may be a server corresponding to the test management system. The test management system is schematically shown in fig. 2, and may include an execution result management module 201 and a label management module 202. The execution result management module 201 is configured to manage execution results, and may include an execution result query sub-module 203, an execution result download sub-module 204, and the like, which are not limited herein. The execution result querying sub-module 203 is configured to query the execution result, and the execution result downloading sub-module 204 is configured to download the execution result.
For example, a user may test a test case of a system under test through the electronic device 102 to obtain an execution result of the test case. The execution results of the test case may be uploaded to the execution result management module 201. When the execution result of the test case is queried, the server 101 may obtain test information of the test case based on the sub-execution results uploaded by other electronic devices, where the test information may include the execution result of the test case, the sub-execution result of each test case, and indication information about whether the test is successful. After the server 101 obtains the execution result of the system to be tested, the user may download the test information through the execution result download submodule 204 of the electronic device 102.
The tag management module 202 is configured to manage tags of a system under test, and may include, but is not limited to, a tag query sub-module 205 for querying tags, a new tag adding sub-module 206 for adding new tags, a tag deleting sub-module 207 for deleting tags, an upload tag sub-module 208 for uploading tags to the server 101, and a download tag sub-module 209 for downloading tags from the server 101. The application does not limit the format of the uploading and downloading labels, and can store a plurality of labels by adopting an Excel document so as to improve the efficiency of uploading or downloading the labels.
In an embodiment of the present application, a test integration system (e.g., a soldier system, etc.) is used to integrate test cases of all systems and test steps of system testing, as well as test environments, production environment codes, test requirements, and test cases or test data associated with the test cases, etc. The test integrated system can also be used for creating a test plan of the system to be tested, wherein the test plan is preset by a tester and can comprise contents to be tested and test targets in one iteration period.
The user may write the test cases in the test integration system, or may upload the test cases to the test integration system after the writing is completed, etc., without limitation. The test plan and test cases may be uploaded in the test integration system or the test management system, or may be uploaded in other applications, etc., and are not limited herein.
It should be noted that the test management system may be included in the test integrated system, or may be used alone. The test integration system and the test management system may be operated in one electronic device, or may be operated in different electronic devices, which are not limited herein.
The test management system can test the system to be tested according to the test plan of the system to be tested in the test integrated system. For example, a user may write a test case of a system to be tested in the test integrated system, and may add a label and a test plan of the system to be tested in the test management system, and then the local server may test the test case based on the test plan to obtain a sub-execution result. And generating the execution remark information of the test case based on the label and the sub-execution result of the test case, and sending the execution remark information to the remote server so that the remote server obtains the test information of the test system or the test information of the system to be tested based on the execution remark information.
Referring to fig. 3, fig. 3 is a flow chart of a test information processing method according to an embodiment of the application. The method comprises the following steps S301-S305, wherein:
S301: the server receives a test information acquisition request from the electronic device.
In the embodiment of the application, the test information acquisition request includes first execution remark information of a first test case in the system to be tested. The test information acquisition request is used for acquiring test information of the first test case, and the test information comprises indication information of whether the first test case is tested successfully or not. The test information may further include, but is not limited to, data analysis results for analyzing test failures, modification instruction information for modifying the first test case when the first test case fails. The system to be tested can be any system, and the first test case can be any test case.
Step S301 may be performed after the user uploads the test plan of the system to be tested in the electronic device, and executes the first test case based on the test plan to obtain the first sub-execution result, or may be performed after the user tests the first test case of the system to be tested in the electronic device to obtain the first sub-execution result, or may be performed after the user inputs the system name of the system to be tested and the case name of the first test case in the electronic device, etc., which is not limited herein.
S302: if the first execution remark information comprises the label of the system to be tested, the server obtains a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label.
S303: if the first execution remark information does not comprise the label of the system to be tested, the server searches second execution remark information of the second test case based on the system identification of the system to be tested, and the second execution remark information comprises a second sub-execution result.
In the embodiment of the application, the second test case is a test case which is influenced or influenced by the first test case when the test is performed in the system to be tested. The present application is not limited to a method of determining the second test case, and in one possible example, includes the steps of: acquiring a test plan of the system to be tested, wherein the test plan comprises the test requirement of each functional module in the system to be tested; and determining a second test case based on the test requirement of the functional module and the test function of the first test case.
The test plan is used for describing the content and the test target to be tested in one iteration period. The test plan may be information created after uploading the test cases, or may be information created in the test integrated system before sending the test request, etc., without limitation. The test plan may be obtained through a requirement document, or through information stored in the test integration system, etc., without limitation. The requirement document may include a plurality of categories including a requirement background, a requirement target, a feature list, a main logic, a characteristic function point, a characteristic requirement, a performance requirement, a data report, a version number record, and the like, which are not limited herein. The test plan includes test requirements for each functional module, which may be characteristic requirements or performance requirements, etc. It will be appreciated that the test plan contains the main logic of the test, as well as the feature or performance requirements, so that the variables to be tested in the system to be tested, as well as the test logic, can be analyzed by the test plan.
In the embodiment of the application, the pre-stored test plan of the system to be tested can be obtained based on the label, or the test plan of the system to be tested can be obtained based on remark information of each test case, and the test plan uploaded by the user can be obtained from the electronic equipment, and the like, without limitation.
The test function of the test case is used for describing the test object and the test target of the test case. It can be appreciated that in this example, the functional module that needs to be tested in the test plan of the system to be tested can be determined based on the test requirement of each functional module in the test plan of the system to be tested and the test function of the first test case, so that the second test case associated with the first test case can be searched based on the test case corresponding to the functional module, and the accuracy of determining the second test case can be improved.
The method for obtaining the second sub-execution result is not limited in the present application, and if the first execution remark information includes a tag of a system to be tested, in a possible example, the method includes the following steps: acquiring label information of the system to be tested based on the label, wherein the label information comprises a structured query statement; and acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the structured query statement.
The structured query statement is used for querying the actual execution result corresponding to the test case as described above. And the second sub-execution result is an actual execution result obtained when the second test case is tested, and after the second test case is determined, the second sub-execution result of the second test case can be obtained based on the structured query statement.
If the first execution remark information does not include the label of the system to be tested, the first execution remark information can be expressed as that the label information of the system to be tested is not stored in the server, or the first execution remark information can be expressed as that the system to be tested has no label. Therefore, in this example, the second execution remark information of the second test case that has completed the test in the system to be tested can be searched, so that the second sub-execution result can be obtained from the second execution remark information, and the effectiveness of the execution result query can be improved conveniently.
S304: the server acquires the test information of the first test case based on the first sub-execution result and the second sub-execution result.
The method for acquiring the test information of the first test case is not limited in the present application, and in one possible example, the step S304 includes the following steps: determining an expected sub-execution result of the first test case based on the second sub-execution result; if the first sub-execution result and the expected sub-execution result are failed to be matched, generating indication information for indicating that the first test case fails to be tested; or if the first sub-execution result and the expected sub-execution result are successfully matched, generating indication information for indicating that the first test case is successfully tested.
The expected sub-execution result is a result expected when the first test case is expected to be executed. The present application is not limited to a method of determining the expected sub-execution result, and in one possible example, includes the steps of: determining an association relationship between the first test case and the second test case; and determining the expected sub-execution result of the first test case based on the association relation and the second sub-execution result.
The association relationship is a mapping relationship of data between the first test case and the second test case, and can be understood as an influence on the data of the first test case when the second test case is executed. It can be understood that after the association relationship between the first test case and the second test case is determined, the expected sub-execution result of the first test case can be obtained based on the second sub-execution result obtained by the second test case, so that the accuracy of obtaining the expected sub-execution result is improved. And then based on whether the first sub-execution result is successfully matched with the expected sub-execution result, generating indication information of whether the first test case is successfully tested, so that the accuracy of judging the success of the test case can be improved.
S305: and the server sends the test information of the first test case to the electronic equipment.
In the method shown in fig. 3, if the test information acquisition request received from the electronic device includes a tag of the system to be tested, a second sub-execution result of a second test case associated with the first test case in the system to be tested is acquired based on the tag. Otherwise, searching second execution remark information of the second test case based on the system identification of the system to be tested, and acquiring a second sub-execution result of the second test case from the second execution remark information. Thus, the efficiency of acquiring the sub-execution results of the associated test cases can be improved through the tag. And then, based on the first sub-execution result and the second sub-execution result included in the test information acquisition request, acquiring the test information of the first test case, and sending the test information of the first test case to the electronic equipment, so that a user corresponding to the electronic equipment determines whether the first test case is successfully tested, and the accuracy of acquiring the test information of the first test case can be improved, that is, the accuracy of identifying whether the first test case fails to be improved.
In a possible example, the tag information further includes an expected execution result of the system to be tested, and after step S302, the method further includes the steps of: acquiring a target execution result of the system to be tested based on the first sub-execution result and the second sub-execution result; if the target execution result is failed to be matched with the expected execution result, generating indication information for indicating the test failure of the system to be tested; or if the target execution result is successfully matched with the expected execution result, generating indication information for indicating the success of the system to be tested.
The target execution result is an actual execution result obtained by integrating the first sub-execution result and the second sub-execution result. The expected execution result is the execution result obtained by the expected execution of the system to be tested as described above.
It can be understood that when the server stores the label information of the system to be tested, the target execution result can be determined according to the expected execution result in the label information of the system to be tested, so that the system to be tested is determined to be tested successfully. That is, when the target execution result matches the expected execution result successfully, indicating that the system to be tested is tested successfully, the indication information for indicating that the system to be tested is tested successfully may be generated. When the target execution result fails to match with the expected execution result, the system to be tested fails to be tested, and indication information for indicating the system to be tested fails to be tested can be generated.
In addition, test information of each test case, for example, indication information of whether the second test case is tested successfully, records of test data, and the like, can be generated. In a possible example, the tag information further includes a test variable, and if the matching between the target execution result and the expected execution result fails, the data records corresponding to the first test case and the second test case are obtained based on the test variable; and acquiring modification indication information of the test case failing to test in the system to be tested based on the data record.
The modification indication information is used for indicating modification suggestions of the test cases which can be tested for failure. The test variables are used to query data records during the test, which may include data involved in the test, as well as execution results, etc., as previously described. It can be understood that after the data records corresponding to the first test case and the second test case are respectively obtained based on the test variables, the data records can be analyzed to obtain the modification indication information of the test case failing to be tested in the system to be tested, so that the success rate of the test is improved.
In one possible example, after the server receives the test information of the electronic device for the system to be tested, the test information of the system to be tested may be sent to the electronic device. Therefore, the user can conveniently determine the test result of the system to be tested and the test result of each test case, and the user can conveniently modify the test cases which fail to be tested, so that the success rate of the test is improved.
In one possible example, after step S304, further includes: the server sends prompt information of the test information to the electronic equipment; if a view instruction of the electronic device is received, step S305 is executed.
In the embodiment of the present application, the prompting information is used for prompting that the test information of the system to be tested has been obtained, and may include an execution result, a storage location of the execution result, a download link of the execution result, a data record, and the like, which are not limited herein.
The query instruction is for requesting to receive test information from the server. The present application is not limited to the viewing instruction, and may be an instruction generated by performing a confirmation operation on the prompt message, for example, clicking a confirmation button corresponding to the prompt message.
It can be understood that after the server obtains the test information of the first test case, the prompt information of the test information of the first test case is sent to the electronic device. After receiving the viewing instruction of the electronic equipment, the user hopes to view the test information corresponding to the prompt information, and the test information can be sent to the electronic equipment. Therefore, the test information of the first test case is not directly displayed, information leakage can be avoided, and the safety of data is improved.
The foregoing details of the method according to the embodiments of the present application and the apparatus according to the embodiments of the present application are provided below.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a test information processing apparatus according to the present application, and as shown in fig. 4, the test information processing apparatus 400 includes:
A receiving unit 401, configured to receive a test information acquisition request from an electronic device, where the test information acquisition request includes first execution remark information of a first test case in a system to be tested, the first execution remark information includes a first sub-execution result of the first test case, the test information acquisition request is used to acquire test information of the first test case, and the test information of the first test case includes information indicating whether the first test case is tested successfully;
an execution result obtaining unit 402, configured to obtain, if the first execution remark information further includes a tag of the system to be tested, a second sub-execution result of a second test case associated with the first test case in the system to be tested based on the tag; or if the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
a test information obtaining unit 403, configured to obtain test information of the first test case based on the first sub-execution result and the second sub-execution result;
And the sending unit 404 is configured to send the test information of the first test case to the electronic device.
In one possible example, the execution result obtaining unit 402 is specifically configured to obtain the tag information based on the tag, where the tag information includes a structured query statement; and acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the structured query statement.
In a possible example, the tag information further includes an expected execution result of the system to be tested, and the test information obtaining unit 403 is further configured to obtain a target execution result of the system to be tested based on the first sub-execution result and the second sub-execution result; if the target execution result is failed to be matched with the expected execution result, generating indication information for indicating the test failure of the system to be tested; or if the target execution result is successfully matched with the expected execution result, generating indication information for indicating that the system to be tested is successfully tested.
In a possible example, the tag information further includes a test variable, and if the matching between the target execution result and the expected execution result fails, the test information obtaining unit 403 is further configured to obtain data records corresponding to the first test case and the second test case based on the test variable; and acquiring modification indication information of the test case failing to test in the system to be tested based on the data record.
In one possible example, the test information obtaining unit 403 is specifically configured to determine an expected sub-execution result of the first test case based on the second sub-execution result; if the first sub-execution result and the expected sub-execution result are failed to be matched, generating indication information for indicating that the first test case fails to be tested; or if the first sub-execution result and the expected sub-execution result are successfully matched, generating indication information for indicating that the first test case is successfully tested.
In one possible example, the test information obtaining unit 403 is specifically configured to determine an association relationship between the first test case and the second test case; and determining an expected sub-execution result of the first test case based on the association relation and the second sub-execution result.
In one possible example, the test information obtaining unit 403 is specifically configured to obtain a test plan of the system under test, where the test plan includes a test requirement of each functional module in the system under test; and determining the association relation between the first test case and the second test case based on the test requirement of the functional module and the test function of the test case.
The detailed process performed by each unit in the test information processing apparatus 400 may refer to the performing steps in the foregoing method embodiment, which is not described herein.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a test information processing apparatus according to an embodiment of the present application. As shown in fig. 5, the test information processing device 500 includes a processor 510, a memory 520, a communication interface 530, and one or more programs 540. Processor 510, memory 520, and communication interface 530 are coupled to each other by bus 550. The related functions implemented by the receiving unit 401 and the transmitting unit 404 shown in fig. 4 may be implemented through the communication interface 530, and the related functions implemented by the execution result acquiring unit 402 and the test information acquiring unit 403 shown in fig. 4 may be implemented through the processor 510.
The one or more programs 540 are stored in the memory 520 and configured to be executed by the processor 510, the program 540 including instructions for:
receiving a test information acquisition request from electronic equipment, wherein the test information acquisition request comprises first execution remark information of a first test case in a system to be tested, the first execution remark information comprises a first sub-execution result of the first test case, the test information acquisition request is used for acquiring the test information of the first test case, and the test information of the first test case comprises indication information of whether the first test case is tested successfully or not;
If the first execution remark information further comprises a label of the system to be tested, acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label; or alternatively
If the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
acquiring test information of the first test case based on the first sub-execution result and the second sub-execution result;
and sending the test information of the first test case to the electronic equipment.
In one possible example, in the aspect of obtaining, based on the tag, a second sub-execution result of a second test case associated with the first test case in the system to be tested, the program 540 is specifically configured to execute instructions for:
acquiring label information of the system to be tested based on the label, wherein the label information comprises a structured query statement;
and acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the structured query statement.
In one possible example, the tag information further includes an expected execution result of the system to be tested, and the program 540 is further configured to execute instructions for:
acquiring a target execution result of the system to be tested based on the first sub-execution result and the second sub-execution result;
if the target execution result is failed to be matched with the expected execution result, generating indication information for indicating the test failure of the system to be tested; or alternatively
And if the target execution result is successfully matched with the expected execution result, generating indication information for indicating that the system to be tested is successfully tested.
In one possible example, the tag information further includes a test variable, and if the target execution result fails to match the expected execution result, the program 540 is further configured to execute instructions for:
acquiring data records corresponding to the first test case and the second test case based on the test variables;
and acquiring modification indication information of the test case failing to test in the system to be tested based on the data record.
In one possible example, in terms of the acquiring the test information of the first test case based on the first sub-execution result and the second sub-execution result, the program 540 is specifically configured to execute instructions for:
Determining an expected sub-execution result of the first test case based on the second sub-execution result;
if the first sub-execution result and the expected sub-execution result are failed to be matched, generating indication information for indicating that the first test case fails to be tested; or alternatively
And if the first sub-execution result and the expected sub-execution result are successfully matched, generating indication information for indicating that the first test case is successfully tested.
In one possible example, in determining the expected sub-execution result of the first test case based on the second sub-execution result, the program 540 is specifically configured to execute instructions for:
determining an association relationship between the first test case and the second test case;
and determining an expected sub-execution result of the first test case based on the association relation and the second sub-execution result.
In one possible example, in the aspect of determining the association relationship between the first test case and the second test case, the program 540 is specifically configured to execute the following instructions:
acquiring a test plan of the system to be tested, wherein the test plan comprises the test requirement of each functional module in the system to be tested;
And determining the association relation between the first test case and the second test case based on the test requirement of the functional module and the test function of the test case.
The present application also provides a computer-readable storage medium storing a computer program configured to implement some or all of the steps of any one of the methods described in the method embodiments when executed by a computer, the computer including an electronic device or a server.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to execute to perform some or all of the steps of any one of the methods recited in the method embodiments. The computer program product may be a software installation package, the computer comprising an electronic device or a server.
It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present application. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts and modes of operation are not necessarily required for the present application.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements, merely a logical division of functionality, and there may be additional divisions of actual implementation, e.g., at least one element or component may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, or may be in electrical or other forms.
The elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over at least one network element. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units described above may be implemented either in hardware or in software program mode.
The integrated units, if implemented in the form of software program modules and sold or used as stand-alone products, may be stored in a computer readable memory. In view of such understanding, the technical solution of the present application may be embodied in essence or in a part contributing to the prior art or in whole or in part in the form of a software product stored in a memory, comprising instructions for causing a computer (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the application. And the aforementioned memory includes: a U-disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing has outlined rather broadly the more detailed description of embodiments of the application, wherein the principles and embodiments of the application are explained in detail using specific examples, the above examples being provided solely to facilitate the understanding of the method and core concepts of the application; meanwhile, as those skilled in the art will vary in the specific embodiments and application scope according to the idea of the present application, the present disclosure should not be construed as limiting the present application in summary.

Claims (6)

1. A test information processing method applied to a server, comprising:
receiving a test information acquisition request from electronic equipment, wherein the test information acquisition request comprises first execution remark information of a first test case in a system to be tested, the first execution remark information comprises a first sub-execution result of the first test case, the test information acquisition request is used for acquiring the test information of the first test case, and the test information of the first test case comprises indication information of whether the first test case is tested successfully or not;
if the first execution remark information further comprises a label of the system to be tested, acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label; or alternatively
If the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
acquiring test information of the first test case based on the first sub-execution result and the second sub-execution result;
sending the test information of the first test case to the electronic equipment;
the obtaining, based on the tag, a second sub-execution result of a second test case associated with the first test case in the system to be tested, includes:
acquiring label information of the system to be tested based on the label, wherein the label information comprises a structured query statement;
acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the structured query statement;
wherein the tag information further includes an expected execution result of the system to be tested, the method further comprising:
acquiring a target execution result of the system to be tested based on the first sub-execution result and the second sub-execution result;
If the target execution result is failed to be matched with the expected execution result, generating indication information for indicating the test failure of the system to be tested; or alternatively
If the target execution result is successfully matched with the expected execution result, generating indication information for indicating that the system to be tested is successfully tested;
wherein the tag information further includes a test variable, and if the target execution result fails to match the expected execution result, the method further includes:
acquiring data records corresponding to the first test case and the second test case based on the test variables;
acquiring modification indication information of a test case failing to test in the system to be tested based on the data record;
the obtaining the test information of the first test case based on the first sub-execution result and the second sub-execution result includes:
determining an expected sub-execution result of the first test case based on the second sub-execution result;
if the first sub-execution result and the expected sub-execution result are failed to be matched, generating indication information for indicating that the first test case fails to be tested; or alternatively
And if the first sub-execution result and the expected sub-execution result are successfully matched, generating indication information for indicating that the first test case is successfully tested.
2. The method of claim 1, wherein the determining the expected sub-execution result of the first test case based on the second sub-execution result comprises:
determining an association relationship between the first test case and the second test case;
and determining an expected sub-execution result of the first test case based on the association relation and the second sub-execution result.
3. The method of claim 2, wherein the determining the association between the first test case and the second test case comprises:
acquiring a test plan of the system to be tested, wherein the test plan comprises the test requirement of each functional module in the system to be tested;
and determining the association relation between the first test case and the second test case based on the test requirement of the functional module and the test function of the test case.
4. A test information processing apparatus, characterized by comprising:
the electronic equipment comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a test information acquisition request from the electronic equipment, the test information acquisition request comprises first execution remark information of a first test case in a system to be tested, the first execution remark information comprises a first sub-execution result of the first test case, the test information acquisition request is used for acquiring the test information of the first test case, and the test information of the first test case comprises indication information of whether the first test case is tested successfully or not;
The execution result obtaining unit is used for obtaining a second sub-execution result of a second test case related to the first test case in the system to be tested based on the label if the first execution remark information also comprises the label of the system to be tested; or if the first execution remark information does not comprise the label of the system to be tested, searching second execution remark information of the second test case based on the system identifier of the system to be tested, wherein the second execution remark information comprises a second sub-execution result of the second test case;
the test information acquisition unit is used for acquiring the test information of the first test case based on the first sub-execution result and the second sub-execution result;
the sending unit is used for sending the test information of the first test case to the electronic equipment;
the execution result obtaining unit is specifically configured to obtain tag information based on the tag, where the tag information includes a structured query statement; acquiring a second sub-execution result of a second test case related to the first test case in the system to be tested based on the structured query statement;
the label information further comprises an expected execution result of the system to be tested, and the test information acquisition unit is further used for acquiring a target execution result of the system to be tested based on the first sub-execution result and the second sub-execution result; if the target execution result is failed to be matched with the expected execution result, generating indication information for indicating the test failure of the system to be tested; or if the target execution result is successfully matched with the expected execution result, generating indication information for indicating that the system to be tested is successfully tested;
The label information further comprises a test variable, and if the target execution result fails to match with the expected execution result, the test information acquisition unit is further used for acquiring data records corresponding to the first test case and the second test case based on the test variable; acquiring modification indication information of a test case failing to test in the system to be tested based on the data record;
the test information acquisition unit is specifically configured to determine an expected sub-execution result of the first test case based on the second sub-execution result; if the first sub-execution result and the expected sub-execution result are failed to be matched, generating indication information for indicating that the first test case fails to be tested; or if the first sub-execution result and the expected sub-execution result are successfully matched, generating indication information for indicating that the first test case is successfully tested.
5. A test information processing device, comprising a processor, a memory, wherein the memory has stored therein a computer program configured to implement the method of any of claims 1-3 when executed by the processor.
6. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program configured to implement the method of any one of claims 1-3 when executed by a computer.
CN202110589653.8A 2021-05-27 2021-05-27 Test information processing method, device, equipment and storage medium Active CN113190465B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110589653.8A CN113190465B (en) 2021-05-27 2021-05-27 Test information processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110589653.8A CN113190465B (en) 2021-05-27 2021-05-27 Test information processing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113190465A CN113190465A (en) 2021-07-30
CN113190465B true CN113190465B (en) 2023-08-18

Family

ID=76985706

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110589653.8A Active CN113190465B (en) 2021-05-27 2021-05-27 Test information processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113190465B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109086196A (en) * 2018-08-16 2018-12-25 郑州云海信息技术有限公司 A kind of calculator room equipment test case management system
CN111752850A (en) * 2020-07-13 2020-10-09 腾讯科技（深圳）有限公司 Method and related equipment for testing block chain system
CN112732587A (en) * 2021-01-21 2021-04-30 腾讯科技（深圳）有限公司 Method and device for acquiring automatic test log, electronic equipment and storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9672029B2 (en) * 2014-08-01 2017-06-06 Vmware, Inc. Determining test case priorities based on tagged execution paths
US9710364B2 (en) * 2015-09-04 2017-07-18 Micron Technology Licensing, Llc Method of detecting false test alarms using test step failure analysis
US20190294531A1 (en) * 2018-03-26 2019-09-26 Ca, Inc. Automated software deployment and testing based on code modification and test failure correlation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109086196A (en) * 2018-08-16 2018-12-25 郑州云海信息技术有限公司 A kind of calculator room equipment test case management system
CN111752850A (en) * 2020-07-13 2020-10-09 腾讯科技（深圳）有限公司 Method and related equipment for testing block chain system
CN112732587A (en) * 2021-01-21 2021-04-30 腾讯科技（深圳）有限公司 Method and device for acquiring automatic test log, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN113190465A (en) 2021-07-30

Similar Documents

Publication Publication Date Title
CN109474578B (en) Message checking method, device, computer equipment and storage medium
US8151248B1 (en) Method and system for software defect management
CN106844730B (en) Method and device for displaying file content
CN109543462A (en) Device identification determines method, apparatus, server and storage medium
CN106843947B (en) Method and device for processing code defects
CN112256318B (en) Construction method and equipment for dependent product
CN111460394A (en) Copyright file verification method and device and computer readable storage medium
CN111078481A (en) Method and device for acquiring configuration check list, electronic equipment and storage medium
CN110928770A (en) Software testing method, device, system, storage medium and electronic equipment
CN111654495B (en) Method, apparatus, device and storage medium for determining traffic generation source
CN112631924A (en) Automatic testing method and device, computer equipment and storage medium
CN111045893A (en) Method, device and system for executing monitoring task, storage medium and electronic device
CN113157315A (en) Method, device, equipment and medium for identifying difference information of different versions of software
CN112925757A (en) Method, equipment and storage medium for tracking operation log of intelligent equipment
CN111506358A (en) Method and device for updating container configuration
CN113434254B (en) Client deployment method, client deployment apparatus, computer device, and storage medium
CN113190465B (en) Test information processing method, device, equipment and storage medium
CN112685077A (en) Data modification method, system, computer device and computer readable storage medium
CN108647139B (en) System test method, device, storage medium and electronic device
CN112306973A (en) Picture importing system and method
CN109672608B (en) Method for transmitting messages according to time
CN113704120A (en) Data transmission method, device, equipment and storage medium
CN113934758A (en) Vehicle fault repairing method and device, vehicle-mounted terminal, server and storage medium
CN114143308A (en) File uploading information processing method and device, computer equipment and storage medium
CN113672514A (en) Test method, test device, server and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant