CN114817003A

CN114817003A - Test information processing method, device, equipment and storage medium

Info

Publication number: CN114817003A
Application number: CN202210346095.7A
Authority: CN
Inventors: 焦佳成
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-03-31
Filing date: 2022-03-31
Publication date: 2022-07-29

Abstract

The disclosure provides a test information processing method, a test information processing device, test information processing equipment and a storage medium, and relates to the technical field of data processing, in particular to the technical field of software testing. The specific implementation scheme is as follows: acquiring a target relation among all the required information; matching the target relation with the existing relation to obtain target tested software similar to the software to be tested; obtaining target test information used for testing target tested software; and determining test information for testing the software to be tested according to the target test information. By applying the scheme provided by the disclosure, the accuracy of processing the test information can be improved.

Description

Test information processing method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing test information.

Background

After the software developer completes the software development, the software tester tests the software. Before starting the test, the software tester collects the test information related to the software and tests the software according to the collected test information.

Disclosure of Invention

The disclosure provides a test information processing method, a test information processing device, a test information processing apparatus and a storage medium.

According to an aspect of the present disclosure, there is provided a test information processing method including:

obtaining a target relationship among the required information, wherein the required information is as follows: information used for testing the software to be tested;

matching the target relation with an existing relation to obtain target tested software similar to the to-be-tested software, wherein the existing relation comprises: testing information used for testing each tested software and relationship information representing the relationship among all the testing information;

obtaining target test information used for testing the target tested software;

and determining test information for testing the software to be tested according to the target test information.

According to another aspect of the present disclosure, there is provided a test information processing apparatus including:

a relationship obtaining module, configured to obtain a target relationship between pieces of demand information, where the demand information is: information used for testing the software to be tested;

a relationship matching module, configured to match the target relationship with an existing relationship, to obtain target tested software similar to the to-be-tested software, where the existing relationship includes: testing information used for testing each tested software and relationship information representing the relationship among all the testing information;

the information acquisition module is used for acquiring target test information used for testing the target tested software;

and the information determining module is used for determining the test information of the software to be tested according to the target test information.

According to another aspect of the present disclosure, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the test information processing method described above.

According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the above-described test information processing method.

According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the above-described test information processing method.

As can be seen from the above, when the test information is processed by applying the scheme provided by the embodiment of the present disclosure, the target relationship constructed according to each requirement information is obtained first, and then the target relationship is matched with the existing relationship, so that the target tested software similar to the software to be tested is obtained. Because the target tested software is similar to the software to be tested, the test information such as the test environment and the test cases used by the target tested software is similar to the test information such as the test environment and the test cases used by the target tested software, so in the scheme provided by the embodiment of the disclosure, the test information used for testing the software to be tested can be accurately determined according to the target test information used by the target tested software for testing.

On the basis, when testing the software to be tested, the testing user can reuse target testing information used for testing the target tested software, quickly construct a testing environment used when the software to be tested is tested, generate a testing case used when the software to be tested is tested, and the like, so that the software to be tested can be tested, the efficiency of the whole testing process is improved, and the utilization rate of the testing information can be improved.

In addition, if the test case and/or the test environment for testing the target tested software can be applied to the test of the to-be-tested software, the test case and/or the test environment for testing the target tested software can be directly reused, so that the to-be-tested software can be tested, and the efficiency of the whole test process can be further improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1a is a schematic flowchart of a first test information processing method according to an embodiment of the present disclosure;

FIG. 1b is a schematic diagram of a first knowledge-graph structure provided by an embodiment of the present disclosure;

FIG. 1c is a schematic diagram of a second knowledge-graph structure provided by an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a second test information processing method according to an embodiment of the disclosure;

fig. 3 is a schematic flowchart of a third test information processing method according to an embodiment of the disclosure;

fig. 4 is a schematic flowchart of a fourth test information processing method according to an embodiment of the disclosure;

fig. 5 is a schematic structural diagram of a first test information processing apparatus according to an embodiment of the present disclosure;

fig. 6 is a block diagram of an electronic device for implementing the test information processing method of the embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Referring to fig. 1a, fig. 1a is a schematic flowchart of a first test information processing method provided by an embodiment of the present disclosure, where the method includes the following steps S101 to S104.

Step S101: and acquiring a target relation among the required information.

Wherein, the demand information is: and testing the software to be tested. For example, the requirement information may include information such as a name and an identifier of the software, information such as a device and an operating system required for running the software, and information about software and hardware configured to test performance of the software.

The requirement information may include software requirement information required for running the software to be tested, for example, information such as equipment and an operating system required for running the software, and may also include test requirement information required for testing the software to be tested, for example, software and hardware information required to be configured for testing the performance of the software.

The target relationship may include each requirement information and relationship information representing a relationship between each requirement information.

The target relationship may be represented in the form of a knowledge graph, a relational data pair, or other data format.

The above-described knowledge graph is graph data including nodes and edges connecting different nodes. When the target relation is expressed in the form of a knowledge graph, nodes in the knowledge graph express the requirement information included in the target relation, and edges connecting different nodes express the relation information among different requirement information.

The following two implementations exist to achieve the above target relationship:

in a first implementation manner, the requirement information may be obtained first, and then the target relationship may be constructed according to each requirement information.

In an embodiment of the present disclosure, when a target relationship is constructed according to requirement information, semantic analysis may be performed on each requirement information to obtain semantic information of each requirement information, and then relationship information representing a relationship between different requirement information is generated according to the semantic information of each requirement information, so that information including each requirement information and relationship information between each requirement information is obtained as a target relationship.

In the second implementation manner, the target relationship constructed by other devices according to each requirement information can also be directly obtained.

The other devices may also perform semantic analysis on each piece of demand information, and construct a target relationship based on the semantic information of each piece of demand information, which is not described herein again.

Step S102: and matching the target relation with the existing relation to obtain target tested software similar to the software to be tested.

Wherein, the existing relationship comprises: the software testing system comprises various testing information used for testing various tested software and relationship information representing the relationship among all the testing information.

For example, the test information may be information of a container required for testing the tested software, an operating system required for running the tested software, a storage space for storing data generated by the test process, and the like.

Further description of the above test information can be found in the following examples, and will not be detailed here.

The tested software may be software developed based on programming languages such as Java and C + +, may be software developed based on MySQL (relational database management system), and may be software developed based on the ElasticSearch tool.

The target tested software is similar to the software to be tested, the target tested software can be understood as software with functions similar to those of the software to be tested in each tested software, and the target tested software can be understood as software with a software framework similar to that of the software to be tested in each tested software.

Similar to the target relationship, the existing relationship may have a plurality of expressions.

For example, FIG. 1b is a schematic diagram of the structure of a first type of prior relationship in the form of a knowledge graph. In fig. 1b, test information included in the existing relationship, such as test case information, operating environment information, test label information, and tested software information, is represented as a plurality of nodes, and relationship information between different test information is represented as edges between different nodes. For example, the relationship information between the test case information and the test label information is represented as an edge between the test case corresponding node and the test label corresponding node.

In addition, since the tested software is already tested, the information used in the testing process of the tested software can be known in advance, and the existing relationship can be constructed, so that the existing relationship can be constructed in advance.

Specific implementation ways for constructing the existing relations can be referred to in the following embodiments, and are not detailed here for the moment.

Specifically, before the target relationship and the existing relationship are matched, the existing relationship may be obtained first, and the existing relationship may include software information such as a name, an identifier, and a service name provided by the software of the tested software, and then the target relationship and the existing relationship are matched to obtain software information of the target tested software, so that the target tested software corresponding to the software information is determined based on the obtained software information.

In addition, the target relation and the existing relation have multiple expression forms, and the matching modes for matching the target relation and the existing relation in different expression forms are different.

For example, the target relationship and the existing relationship may be represented in the form of a knowledge graph, in which case, the specific implementation manner of matching the target relationship and the existing relationship may be referred to in the following steps S302 to S303 in the embodiment shown in fig. 3.

In addition, the target relationship and the existing relationship may be represented in other data formats, and in this case, the target relationship and the existing relationship may be matched by a conventional data matching method for the other data formats.

Step S103: target test information used for testing the target tested software is obtained.

Specifically, since the target tested software is already tested, the test information of the target tested software can be obtained in advance, so that the test information corresponding to the target tested software can be obtained after the target tested software is determined. As target test information.

Step S104: and determining test information for testing the software to be tested according to the target test information.

In an embodiment of the present invention, the obtained target test information may be directly used as test information for testing the software to be tested, so that the test user may obtain the target test information and test the software to be tested based on the target test information.

In addition, the format of the target test information can be converted into a preset format, and then the target test information in the preset format can be recommended to the test user.

For example, the preset format may be a YAML (YAML Ain't Markup Language) format.

In another embodiment of the present invention, according to the target test information, a test case and/or a test environment required for testing the software to be tested may be constructed, and the constructed test case and/or test environment may be used as test information for testing the software to be tested.

The construction of the test case or the test environment according to the target test information can be realized by the existing software test technology, and is not detailed here.

As can be seen from the above, in the scheme provided in the embodiment of the present disclosure, the target relationship constructed according to each requirement information is obtained first, and then the target relationship is matched with the existing relationship, so that the target tested software similar to the software to be tested is obtained. Because the target tested software is similar to the software to be tested, the test information such as the test environment and the test cases used by the target tested software is similar to the test information such as the test environment and the test cases used by the target tested software, so in the scheme provided by the embodiment of the disclosure, the test information used for testing the software to be tested can be accurately determined according to the target test information used by the target tested software for testing.

The following is a description of specific implementations for constructing the relationships.

In an embodiment of the present disclosure, a relationship similarity between any two relationships included in the existing relationship is smaller than a preset threshold.

The existing relationship in which the relationship similarity between any two relationships in the included relationships is smaller than the preset threshold value can be constructed in the following two ways.

In a first implementation manner, the preset threshold may be preset, and for each pending relationship to be added to an existing relationship, similarity between the pending relationship and each relationship already existing in the existing relationship is calculated, and if the similarity obtained through calculation is greater than or equal to the similarity of the preset threshold, it is determined that a duplicate relationship identical or similar to the existing relationship exists in the existing relationship, and at this time, the pending relationship is discarded; if all the calculated similarity degrees are not larger than the preset threshold value, the undetermined relationship is considered to be different from all the relationships in the existing relationship, and at the moment, the undetermined relationship is added into the existing relationship. All the undetermined relations are processed by the method, and the similarity of the relations between any two relations contained in the existing relations obtained after processing is smaller than a preset threshold value.

In a second implementation manner, all pending relationships used for constructing an existing relationship may be collected in advance, and on this basis, the similarity between every two pending relationships is calculated, and if the similarity between two pending relationships is greater than or equal to a preset threshold, any one of the two pending relationships may be discarded; and if the similarity between the two undetermined relationships is smaller than the set threshold, reserving the two undetermined relationships. And finally, adding all the remaining undetermined relations into the existing relation.

In addition, the preset threshold may be set by a test user according to experience, may be set according to distribution information of the similarity between each pending relationship, or may be set according to dynamic distribution of the similarity between relationships that are continuously collected in the process of constructing the existing relationship.

As can be seen from the above, in the scheme provided by the embodiment of the present disclosure, the similarity between any two relationships included in the existing relationship is smaller than the preset threshold, so that the identical or similar repeated relationship existing in the existing relationship can be avoided, the data size of the existing relationship is reduced, and the efficiency of processing the test information is improved.

The test information mentioned in step S102 above is further explained below.

In an embodiment of the present disclosure, the test information used for testing each tested software includes: and the environment construction information is used for constructing the test environment used by each tested software in the test.

The testing of the tested software needs to be performed in a test environment, so before the tested software is tested, a test environment for testing the tested software needs to be constructed first, and information for constructing the test environment may be referred to as environment construction information.

For example, the environment construction information may include tester information, environment tags, test tags, startup script information, hardware environment information, software environment information, and the like.

In addition, the test environments used by different tested software during testing may be the same or different, and therefore, the environment construction information for constructing the test environments used by different tested software during testing may be the same or different.

In this scheme, under the condition that the test information includes the environment construction information, the target test information includes environment construction information used for constructing a test environment used when the target tested software is tested, so that after the test information for testing the software to be tested is determined according to the target test information, a test user can refer to the environment construction information corresponding to the target tested software, so as to construct a test environment used for testing the software to be tested, and thus the software to be tested is tested.

In another embodiment of the present disclosure, the test information used for testing each tested software includes: and the case generation information is used for generating the test case used when each tested software is tested.

The test of the tested software requires the use of test cases, so before the tested software is tested, the test cases for testing the tested software need to be generated, and the information for generating the test cases can be understood as case generation information.

For example, the use case generation information may include a test label, a test method, an operation environment, and the like, and in addition, the use case generation information may further include personnel information of a tester, industry information of an industry to which the tested software is applied, personnel information for developing the tested software, and the like.

In addition, the test cases used by different tested software during testing may be the same or different, and for one tested software, multiple test cases may be used to test the tested software, so that the case generation information for generating the test cases used by different tested software during testing may be the same or different.

In this scheme, under the condition that the test information includes the case generation information, the target test information includes case generation information used for generating a test case used when the target tested software is tested, so that after the test information for testing the software to be tested is determined according to the target test information, a test user can refer to the case generation information corresponding to the target tested software to generate the test case used for testing the software to be tested, thereby testing the software to be tested.

In another embodiment of the present disclosure, each piece of test information used for testing each piece of tested software includes two pieces of information, namely, the environment construction information and the case generation information.

In this case, the target test information obtained in step S103 includes environment construction information for constructing a test environment used for testing the target tested software and case generation information for generating a test case used for testing the target tested software, so that after the test information for testing the software to be tested is determined according to the target test information, the user can refer to the environment construction information and the case generation information corresponding to the target tested software to generate the test environment and the test case used for testing the software to be tested. Therefore, the scheme provided by the embodiment of the disclosure can determine richer test information.

Since software can be run in a container, and the software needs to be run when being tested, when a test environment for testing the software is constructed, the test environment is also constructed based on the container.

In view of the above situation, in an embodiment of the present disclosure, the environment construction information may include, in addition to the information mentioned in the above embodiment, further: configuration information for a container running the tested software.

The container can be understood as a virtual machine, the container is arranged on a host machine, and one host machine can be provided with a plurality of containers. For one piece of software, a plurality of containers may be allocated to the software. Each container allocated for the software can independently run the software and provide services corresponding to the software for users; each container allocated for the software can also be matched with at least two containers to run the software together, and provide services corresponding to the software for users together.

The configuration information of the container may include: the number of containers, the arrangement of a plurality of containers, and the like, and the configuration information of the containers may further include: configMap mount information, persistent volume information, network information of the container, and the like.

The configMap mount information is used to record the process of mounting software into the container in the manner of environment variables/file systems.

The persistent volume information is information of a mount point, and the mount point is used for storing information generated inside the container. For example, the mount point may be an emptyDir (empty directory) for storing a temporary file, and the mount point may be a hostPath (host path), a persistent volume, or the like for storing service information.

The network information of the container comprises container port information and node port information, the container port refers to a port for monitoring when the software image is started, and the node port refers to a port on the host.

The configuration information of the container may be understood as the attribute information of the tested software, and since there is a relationship between the attribute information of the tested software and the tested software information, the attribute information of the tested software, the tested software information, and the relationship information between these two kinds of information may constitute a relationship, and this relationship may be expressed in the form of a knowledge graph, the configuration information of the container, the information of the tested software, and the relationship information between these two kinds of information may constitute a relationship, and this relationship may be expressed in the form of a knowledge graph.

For example, fig. 1c is a schematic diagram of a knowledge graph, and the knowledge graph shown in fig. 1c may represent a relationship between information of tested software and attribute information of the tested software. In fig. 1c, the attribute information of the tested software includes the account configuration information of the tested software, and also includes the configuration information of the container, such as configMap mount information, persistent volume information, and network information of the container. Value (key value pair), key0 value0 are two sets of information values of configMap mount information, emptyDir, hostPath, and persistent volume are three different types of persistent volume information, respectively, and container port, node port, ingress controller, and load balancer are different types of network information, respectively.

In one implementation, when obtaining the configuration information, a record document in which a structure of a test environment used by the tested software test is recorded may be first obtained, information required for constructing the test environment based on a container may be extracted from the record document, and the information may be used as configuration information of a container in which the tested software runs.

For example, the method for constructing the test environment based on the container may be an existing K8s method, and in this case, information required for constructing the test environment according to the K8s method may be extracted from the record document.

After the configuration information is obtained, the information format of the configuration information can be converted into a preset information format meeting the condition of constructing the existing relationship, and the existing relationship including the configuration information is constructed based on the converted configuration information.

The aforementioned knowledge maps shown in fig. 1b and fig. 1c may be combined into one knowledge map, or may be provided as two knowledge maps.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, the environment construction information includes configuration information of a container used for running the tested software, in this case, the obtained target test information includes configuration information of the container used for running the target tested software, so that after determining the test information according to the target test information, a test user can know the configuration information of the container running the target tested software, and since the software generally needs to run in the container, the test user can refer to the known configuration information of the container to accurately construct a test environment for testing the software to be tested. Therefore, by applying the scheme provided by the embodiment of the disclosure, the accuracy of test information processing can be improved. In addition, in the scheme, the configuration information of the container may include the arrangement information of the container, and under the condition of heterogeneous hardware, the learning and access cost of arranging the container can be reduced by arranging the container based on the test information determined by the scheme provided by the embodiment of the disclosure.

Testing the tested software requires the use of additional hardware and/or software in addition to the container.

In view of this situation, in an embodiment of the present disclosure, referring to fig. 2, a flow diagram of a second test information processing method is provided, in this embodiment, each existing relationship includes: the node corresponding to the two pieces of test information with the relationship and the relationship information representing the relationship between the two pieces of test information. The above step S103 can be realized by the following steps S203 to S204.

Specifically, the embodiment shown in FIG. 2 includes the following steps S201-S205.

Step S201: and acquiring a target relation among the required information.

Step S202: and matching the target relation with the existing relation to obtain target tested software similar to the software to be tested.

The steps S201 to S202 are the same as the steps S101 to S102 in the embodiment shown in fig. 1a, and are not described again here.

Step S203: and determining a second node which has a relationship with the first node from the existing relationship, and obtaining the configuration information of the container for running the target tested software from the attribute information of the first node.

The existing relation is provided with a plurality of nodes, each node corresponds to one type of information, and the first node corresponds to the identification information of the target tested software.

For example, the first node may correspond to identification information such as a name and a tag of the target tested software.

The second node corresponds to software information and/or hardware information for performing a software test.

For example, the software information may include information of an operating system, a platform, and other software required for running the tested software.

The hardware information may include information of hardware such as a CPU and a GPU required for testing the tested software.

The existing relationship includes software nodes corresponding to each tested software, each software node has its own attribute information, the attribute information includes configuration information of a container of the tested software corresponding to the software node, and in addition, the attribute information may also include information of attributes such as account configuration information of the tested software.

Specifically, after the target measured software is obtained, a first node corresponding to the target measured software may be determined in an existing relationship based on information such as a name and an identifier of the target measured software, so as to determine attribute information of the first node, and then configuration information of a container for running the target measured software may be extracted from the attribute information of the first node. A second node with which a relationship exists can also be found from the first node.

Step S204: and generating target test information for testing the target tested software according to the obtained configuration information and the determined node information of the second node.

The node information of the second node may be understood as software information and/or hardware information that the second node performs a software test.

Specifically, after configuration information of a container for running the target tested software is obtained and the second node is determined, software information and/or hardware information corresponding to the second node may be obtained, and then target test information including the obtained configuration information, software information and/or hardware information is generated.

Step S205: and determining test information for testing the software to be tested according to the target test information.

This step is the same as step S104 described above, and is not described here again.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, the target test information is generated according to the obtained configuration information and the node information of the second node, so that richer test information can be determined according to the target test information.

The following describes a specific implementation manner of matching the target relationship and the existing relationship when the target relationship and the existing relationship are expressed in the form of a knowledge graph.

Referring to fig. 3, a flowchart of a third test information processing method is provided, in this embodiment, a target relationship is represented by a target knowledge graph recording a relationship between pieces of required information, an existing relationship is represented by an existing knowledge graph recording a relationship between pieces of test information used for testing each piece of tested software, and test information used for testing the piece of tested software includes software information of the piece of tested software. The above step S102 can be realized by the following steps S302 to S303.

The software information of the tested software may be the name, identification, etc. of the tested software.

Specifically, the embodiment shown in FIG. 3 includes the following steps S301-S305.

Step S301: and acquiring a target knowledge graph constructed according to the required information.

This step is similar to step S101 described above, and in one case, the demand information may be obtained first, and then the target knowledge graph may be constructed based on each demand information.

In another case, the knowledge graph constructed by other equipment according to each required information can be directly obtained as the target knowledge graph.

In an embodiment of the present disclosure, when constructing the target knowledge graph, the requirement information and the relationship information between the requirement information may be obtained first, the obtained requirement information and relationship information are converted into knowledge, and then the target knowledge graph is constructed according to the converted knowledge.

Step S302: and carrying out map matching on the target knowledge map and the existing knowledge map to obtain target software information recorded in an area, matched with the target knowledge map, in the existing knowledge map.

The existing knowledge graph can be a pre-constructed knowledge graph which records the relationship between the software information of each tested software and each test information.

The implementation of constructing the existing knowledge graph can be seen in the following embodiments, and will not be described in detail here.

Specifically, the existing knowledge graph can comprise the relationship between the software information of a plurality of tested software and a plurality of test information, so that the scale of the existing knowledge graph is large, when the graph matching is carried out, the graph matching can be carried out on the target knowledge graph and partial regions of the existing knowledge graph, the graph matching of the target knowledge graph and the existing knowledge graph is realized by carrying out multiple graph matching on the target knowledge graph and different regions of the existing knowledge graph, the region matched with the target knowledge graph in the existing knowledge graph is determined based on the matching result of the multiple graph matching, and the software information recorded in the determined region is obtained as the target software information.

The atlas matching of the target knowledge-atlas with the partial region of the existing knowledge-atlas can be realized by the existing atlas matching technology, and the detailed description is omitted here.

Step S303: and determining the tested software corresponding to the target software information as the target tested software similar to the software to be tested.

The software information of the tested software can be used for searching the tested software, after the target software information is obtained, the corresponding tested software can be searched by using the target software information, and the searched tested software is the target tested software.

Step S304: target test information used for testing the target tested software is obtained.

Step S305: and determining test information for testing the software to be tested according to the target test information.

The steps S304-S305 are the same as the steps S103-S104 in the embodiment shown in fig. 1a, and are not described again here.

As can be seen from the above, in the scheme provided by the embodiment of the present disclosure, when the target relationship and the existing relationship are expressed in the form of a knowledge graph, the map matching is performed on the target knowledge graph and the existing knowledge graph, and the region matched with the target knowledge graph can be accurately determined in the existing knowledge graph, so as to obtain the target software information recorded in the region, so that the target tested software can be accurately determined based on the target software information, and then the accurate target test information can be obtained, and the test information for testing the software to be tested can be accurately determined according to the target test information.

The following describes a specific implementation of constructing an existing knowledge graph.

In an embodiment of the present disclosure, the software information of each tested software and the relationship information between the software information may be obtained first, and a relationship may be formed by two pieces of software information and the relationship information between the two pieces of software information, where the relationship may also be referred to as knowledge, that is, two pieces of software information and the relationship information between the two pieces of software information may form a piece of knowledge. After the software information and the relationship information are obtained, data preprocessing such as validity check and format conversion can be performed on the obtained information, and then the existing knowledge map is constructed by knowledge formed by the obtained software information and the relationship information.

In another embodiment of the present disclosure, after obtaining the above knowledge, the existing knowledge-graph can be constructed by using either of the following two implementation manners.

In a first implementation, a similarity threshold may be set, for each knowledge, the similarity between the knowledge and each existing knowledge in the existing knowledge graph is calculated, and whether to add the knowledge to the existing knowledge graph is determined by comparing the calculated similarity with the similarity threshold. Thus, the above processing is carried out on each knowledge, and the existing knowledge map is constructed.

In a second implementation manner, after the above knowledge is obtained, the similarity between every two pieces of knowledge may be calculated, and if the similarity between two pieces of knowledge is greater than or equal to the set similarity threshold, any one of the two pieces of knowledge may be discarded; and if the similarity between the two pieces of knowledge is smaller than a similarity threshold value, retaining the two pieces of knowledge, and finally constructing the existing knowledge graph based on all the remaining knowledge.

In addition, the similarity threshold may be set by a test user according to experience, may be set according to distribution information of the similarity between the knowledge, or may be set according to dynamic distribution of the similarity between relationships that are continuously collected in the process of constructing the existing knowledge graph.

In one embodiment of the present disclosure, when calculating the similarity between different pieces of knowledge, the pieces of knowledge may be first converted into vectors, and then the similarity between different vectors may be calculated.

For example, the cosine similarity between different vectors can be calculated as the similarity between the knowledge represented by the different vectors using the following expression:

wherein x and y represent different knowledge, P _x Attribute value, P, representing knowledge x _y Attribute value, vec (P), representing knowledge y _x ) Representing the vector transformed by knowledge x, vec (P) _y ) The vector converted by the knowledge y is represented, and sim (x, y) represents the similarity between different knowledge.

Besides, the similarity between different knowledge can be calculated by using other existing similarity calculation algorithms, which are not described in detail herein.

In an embodiment of the present invention, the test information for testing the software to be tested, which is determined according to the target test information, may be recommended to the test user, and for convenience of description, the test information for testing the software to be tested, which is recommended to the test user, is referred to as recommendation information. According to the description in the above disclosed embodiment, the target test information may include environment construction information for constructing a test environment used by the target tested software for testing, and at this time, the recommendation information may be understood as environment reference information for providing a reference for a test user to construct the test environment used by the test of the software to be tested; the target test information may further include case generation information used for generating a test case used when the target tested software is tested, and at this time, the recommendation information may be understood as case reference information used for providing a reference for a test user to generate the test case used for testing the software to be tested.

The scheme provided by the above-mentioned disclosed embodiment can be understood as that by searching the target tested software, the above-mentioned environment reference information and/or use case reference information are obtained according to the target tested software, the test user can generate the test environment with reference to the environment reference information, and the test user can also generate the test use case with reference to the use case reference information. When obtaining the use case reference information, the use case reference information may be obtained by the method mentioned in the embodiment shown in fig. 2, in addition to the method mentioned in the above disclosed embodiment for obtaining use case reference information by finding target tested software.

Referring to fig. 4, a flowchart of a fourth test information processing method is provided, in the embodiment of the present disclosure, the test information includes use case generation information for generating a test case used when each tested software is tested, the step S102 may be implemented by the following step S402, the step S103 may be implemented by the following step S403, and the step S104 may be implemented by the following step S404.

Specifically, the embodiment shown in FIG. 4 includes the following steps S401-S404.

Step S401: and obtaining the target relation among the required information.

This step is the same as step S101 in the embodiment shown in fig. 1a, and is not described again here.

Step S402: and matching the target relation with the existing relation to obtain target tested software similar to the software to be tested and first information of the test case indicated by the target matching relation.

When the tested software is tested, the tested software can be tested by using a plurality of test cases, and when a plurality of test cases are generated, the test cases can be generated based on case generation information corresponding to the test cases.

The target matching relationship is a relationship which is included in the existing relationship and is matched with the target relationship.

Specifically, the existing relationship may include a relationship between software information of the tested software and case generation information of the test case, the target relationship and the existing relationship are matched, the software information of the target tested software may be determined in the existing relationship, the target tested software is determined according to the software information of the target tested software, case generation information of the target test case related to the software information of the target tested software is obtained according to the relationship between the software information of the target tested software and the information of the test case, and the case generation information of the target test case is used as the first information.

For example, if the test case a is a test case used when the tested software a is tested, the tested software a is related to the test case a, a relationship between the tested software a and the case generation information of the test case a may be established, and if it is determined that the tested software a is the target tested software after the relationship matching, the case generation information of the test case a may be obtained according to the established relationship, as the first information.

In addition, since the existing relationship may also include a case relationship between the identification information of the tested software and the information of the test case, after the target relationship and the existing relationship are matched to obtain the target tested software, the case relationships where the identification information of the target tested software in the target relationship and the existing relationship are located may be secondarily matched to obtain a case relationship with the highest similarity to the target relationship in the existing relationship as the relationship matched to the target relationship, and the case generation information of the test case recorded in the obtained case relationship is the first information.

Step S403: and obtaining second information used for constructing a test environment when the target tested software is tested.

Specifically, the information for constructing the test environment can be obtained in advance when each tested software is tested. After the target tested software is determined, information for constructing a test environment when the target tested software is tested can be found from information corresponding to a plurality of pieces of tested software obtained in advance and used as second information.

Step S404: and determining the obtained first information and the second information as test information for testing the software to be tested.

As can be seen from the above, in the scheme provided by the embodiment of the present disclosure, the target relationship is matched with the existing relationship, and the first information of the test case indicated by the relationship matched with the target relationship and the target tested software can be obtained, where the first information is the information of the test case indicated by the relationship matched with the target relationship, and the accuracy of the first information is ensured. Because the information for constructing the test environment can be obtained in advance when each tested software is tested, after the target tested software is obtained, the second information corresponding to the target tested software can be obtained, and finally the first information and the second information are determined as the test information for testing the software to be tested. Therefore, in the scheme provided by the embodiment of the disclosure, the finally obtained test information includes the first information and the second information, so that test information with richer contents is provided for the test user.

Corresponding to the test information processing method, the embodiment of the disclosure also provides a test information processing device.

Referring to fig. 5, there is provided a schematic structural diagram of a first test information processing apparatus, the apparatus including:

a relationship obtaining module 501, configured to obtain a target relationship between pieces of requirement information, where the requirement information is: information used for testing the software to be tested;

a relationship matching module 502, configured to match the target relationship with an existing relationship to obtain target tested software similar to the to-be-tested software, where the existing relationship includes: testing information used for testing each tested software and relationship information representing the relationship among all the testing information;

an information obtaining module 503, configured to obtain target test information used for testing the target tested software;

an information determining module 504, configured to determine, according to the target test information, test information for testing the software to be tested.

As can be seen from the above, in the scheme provided in the embodiment of the present disclosure, under the condition that the test information includes the environment construction information, the target test information includes environment construction information used for constructing a test environment used when the target tested software is tested, so that after the test information for testing the to-be-tested software is determined according to the target test information, a test user can refer to the environment construction information corresponding to the target tested software, thereby constructing the test environment used for testing the to-be-tested software, and thus testing the to-be-tested software.

In an embodiment of the present disclosure, the test information used for testing each tested software includes: and the case generation information is used for generating the test case used when each tested software is tested.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, under the condition that the test information includes the case generation information, the target test information includes case generation information used for generating a test case used when the target tested software is tested, so that after the test information for testing the to-be-tested software is determined according to the target test information, a test user can refer to the case generation information corresponding to the target tested software, so as to generate the test case used for testing the to-be-tested software, thereby implementing the test on the to-be-tested software.

In an embodiment of the present disclosure, the test information used for testing each tested software includes: the environment construction information is used for constructing the test environment used by each tested software for testing, and the case generation information is used for generating the test case used by each tested software for testing.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, the target test information obtained in step S103 includes environment construction information for constructing a test environment used by the target tested software for testing and case generation information for generating a test case used by the target tested software for testing, so that after determining the test information for testing the software to be tested according to the target test information, a user can refer to the environment construction information and the case generation information corresponding to the target tested software to generate the test environment and the test case used for testing the software to be tested. Therefore, the scheme provided by the embodiment of the disclosure can determine richer test information.

In one embodiment of the present disclosure, the environment construction information includes: configuration information for a container running the tested software.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, the obtained target test information includes configuration information of a container for running the target tested software, so that after determining the test information according to the target test information, the test user can know the configuration information of the container for running the target tested software. Therefore, by applying the scheme provided by the embodiment of the disclosure, the accuracy of test information processing can be improved.

In one embodiment of the present disclosure, each existing relationship includes: the node corresponding to the two pieces of test information with the relationship and the relationship information representing the relationship between the two pieces of test information;

the information obtaining module 503 is specifically configured to:

determining a second node which has a relationship with the first node from the existing relationship, and obtaining configuration information of a container for running the target tested software from attribute information of the first node, wherein the first node corresponds to identification information of the target tested software, and the second node corresponds to software information and/or hardware information for performing software testing;

and generating target test information for testing the target tested software according to the obtained configuration information and the determined node information of the second node.

In an embodiment of the present disclosure, the target relationship is represented by a target knowledge graph that records a relationship between the pieces of required information, the existing relationship is represented by an existing knowledge graph that records a relationship between pieces of test information used for testing the pieces of tested software, and the test information used for testing the pieces of tested software includes software information of the pieces of tested software;

the relationship matching module 502 is specifically configured to:

performing map matching on the target knowledge map and the existing knowledge map to obtain target software information recorded in an area, matched with the target knowledge map, in the existing knowledge map;

and determining the tested software corresponding to the target software information as the target tested software similar to the software to be tested.

As can be seen from the above, in the scheme provided by the embodiment of the present disclosure, the similarity between any two relationships included in the existing relationship is smaller than the preset threshold, so that the identical or similar repeated relationship in the existing relationship can be avoided, the data size of the existing relationship is reduced, and the efficiency of processing the test information is improved.

In an embodiment of the present disclosure, the test information includes use case generation information used for generating a test case used when each tested software is tested;

the relationship matching module 502 is specifically configured to:

matching the target relation with the existing relation to obtain target tested software similar to the software to be tested and first information of a test case indicated by the target matching relation, wherein the target matching relation is a relation which is included in the existing relation and is matched with the target relation;

the information obtaining module 503 is specifically configured to:

obtaining second information used for constructing a test environment when the target tested software is tested;

the information determining module 504 is specifically configured to:

and determining the obtained first information and second information as test information for testing the software to be tested.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

In one embodiment of the present disclosure, there is provided an electronic device, as a server, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any of the test information processing methods of the preceding method embodiments.

In one embodiment of the present disclosure, a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of application file configuration in any of the preceding method embodiments is provided.

In one embodiment of the present disclosure, a computer program product is provided, comprising a computer program which, when executed by a processor, implements any of the test information processing methods of the preceding method embodiments.

FIG. 6 illustrates a schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the apparatus 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 601 executes the respective methods and processes described above, such as the test information processing method. For example, in some embodiments, the test information processing method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the test information processing method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the test information processing method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A test information processing method, comprising:

obtaining target test information used for testing the target tested software;

2. The method of claim 1, wherein each piece of test information used for testing each piece of tested software comprises:

the environment construction information is used for constructing the test environment used by each tested software during testing;

and/or

And the case generation information is used for generating the test case used when each tested software is tested.

3. The method of claim 2, wherein,

the environment construction information includes: configuration information for a container running the tested software.

4. The method of claim 3, wherein each existing relationship comprises: the node corresponding to the two pieces of test information with the relationship and the relationship information representing the relationship between the two pieces of test information;

the obtaining target test information used for testing the target tested software includes:

5. The method according to any one of claims 1-4, wherein the target relationship is represented by a target knowledge graph recording the relationship between the required information, the existing relationship is represented by an existing knowledge graph recording the relationship between the test information used for testing the tested software, and the test information used for testing the tested software comprises the software information of the tested software;

the matching of the target relation and the existing relation to obtain the target tested software similar to the software to be tested comprises the following steps:

6. The method of any one of claims 1-4,

and the relationship similarity between any two relationships in the existing relationship is smaller than a preset threshold value.

7. The method according to claim 1, wherein the test information includes use case generation information for generating a test case used when each tested software is tested;

the determining test information for testing the software to be tested according to the target test information includes:

8. A test information processing apparatus comprising:

and the information determining module is used for determining test information for testing the software to be tested according to the target test information.

9. The apparatus of claim 8, wherein each piece of test information used for testing each piece of tested software comprises:

and/or

10. The apparatus of claim 9, wherein,

11. The apparatus of claim 10, wherein each existing relationship comprises: the node corresponding to the two pieces of test information with the relationship and the relationship information representing the relationship between the two pieces of test information;

the information obtaining module is specifically configured to:

12. The apparatus according to any one of claims 8-11, wherein the target relationship is represented by a target knowledge graph recording a relationship between the pieces of requirement information, the existing relationship is represented by an existing knowledge graph recording a relationship between pieces of test information used for testing the pieces of tested software, and the software information of the tested software is included in the test information used for testing the pieces of tested software;

the relationship matching module is specifically configured to:

13. The apparatus of any one of claims 8-11,

14. The device of claim 8, wherein the test information includes use case generation information for generating test cases used when each tested software is tested;

the relationship matching module is specifically configured to match the target relationship with an existing relationship to obtain target tested software similar to the software to be tested and first information of a test case indicated by the target matching relationship, where the target matching relationship is a relationship, included in the existing relationship, matching the target relationship;

the information obtaining module is specifically used for obtaining second information used for constructing a test environment when the target tested software is tested;

the information determining module is specifically configured to determine the obtained first information and the second information as test information for testing the software to be tested.

15. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the test information processing method of any one of claims 1-7.

16. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the test information processing method according to any one of claims 1 to 7.

17. A computer program product comprising a computer program which, when executed by a processor, implements a test information processing method according to any one of claims 1 to 7.