Test information query method, device and electronic equipment

Abstract

The present invention discloses a test information query method, device and electronic device. The method comprises: receiving a test information query instruction, wherein the test information query instruction carries a test object; in response to the test information query instruction, determining multiple test tasks corresponding to the test object; determining test case information corresponding to the multiple test tasks, wherein the corresponding test case information includes the case execution progress of the corresponding test case item; determining the test information corresponding to the test object based on the test case information corresponding to the multiple test tasks, wherein the test information includes the test progress. The present invention solves the technical problem in the related art that the division of labor is scattered during the software testing process, resulting in low query efficiency when querying the relevant information of the software test.

Description

Technical Field

[0001] The present invention relates to the field of data processing, and in particular to a test information query method, device and electronic equipment. Background Art

[0002] In the related technology, during the software testing process, depending on the different testing tasks, the entire testing division of labor is often scattered, resulting in a large amount of cost to search, screen and integrate relevant information from different data and reports when querying relevant information of the software testing, resulting in a technical problem of low query efficiency.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present invention provide a test information query method, device and electronic device to at least solve the technical problem in the related art that, during the software testing process, the division of labor is scattered, resulting in low query efficiency when querying relevant information of the software test.

[0005] According to one aspect of an embodiment of the present invention, a test information query method is provided, comprising: receiving a test information query instruction, wherein the test information query instruction carries a test object; determining a plurality of test tasks corresponding to the test object in response to the test information query instruction; determining test case information respectively corresponding to the plurality of test tasks, wherein the corresponding test case information includes a case execution progress of a corresponding test case item; and determining test information corresponding to the test object based on the test case information respectively corresponding to the plurality of test tasks, wherein the test information includes a test progress.

[0006] Optionally, determining the test information corresponding to the test object based on the test case information respectively corresponding to the multiple test tasks includes: when the test information includes a target indicator index, determining multiple evaluation items corresponding to the target indicator item; determining evaluation parameters respectively corresponding to the multiple evaluation items from the test case information respectively corresponding to the multiple test tasks; and determining the target indicator index based on multiple evaluation parameters.

[0007] Optionally, determining the test case information corresponding to the multiple test tasks respectively includes: when the test case information includes test case results, determining the object deployment stages corresponding to the multiple test tasks respectively; determining the target codes corresponding to the multiple object deployment stages respectively from the multiple version codes corresponding to the test object, wherein the multiple version codes correspond one-to-one to the multiple deployment stages of the test object; and testing the corresponding target codes according to corresponding test case parameters to obtain corresponding test case results.

[0008] Optionally, determining the test case information corresponding to the multiple test tasks respectively includes: when the test case information includes a predicted case result, determining the associated test case information corresponding to the test case item, wherein the associated test case information is information corresponding to a completed associated case item, and the associated test case information includes a case completion cycle; inputting the test case item and the associated test case information into an information prediction model to obtain a predicted case result corresponding to the test case item, wherein the predicted case result includes a predicted completion cycle, and the information prediction model is a model trained based on sample data.

[0009] Optionally, the receiving of the test information query instruction includes: receiving an execution request for executing a test case to be executed; in response to the execution request, triggering the test information query instruction to obtain test information including associated progress information, wherein the test information query instruction also carries the test case to be executed, and the associated progress information is information associated with the test case to be executed and corresponding to the test case with update progress.

[0010] Optionally, after determining the test information corresponding to the test object based on the test case information corresponding to the multiple test tasks respectively, it also includes: determining the use case impact result based on the associated progress information; when the use case impact result is to affect the use case process of the test case to be executed, changing the test case parameters of the test case to be executed to obtain updated test case parameters, so as to execute the test on the test case to be executed under the updated test case parameters.

[0011] Optionally, it also includes: determining the code change result of the test object; when the code change result is the code change of the test object, determining the update test task from the multiple test tasks based on the update code; updating the test case item corresponding to the update test task to obtain an update use case item; determining the update use case information corresponding to the update test tasks respectively, wherein the update use case information includes the use case execution progress of the corresponding update use case item.

[0012] According to one aspect of an embodiment of the present invention, a test information query device is provided, comprising: a receiving module, used to receive a test information query instruction, wherein the test information query instruction carries a test object; a first determination module, used to determine a plurality of test tasks corresponding to the test object in response to the test information query instruction; a second determination module, used to determine test case information respectively corresponding to the plurality of test tasks, wherein the corresponding test case information includes a case execution progress of a corresponding test case item; and a third determination module, used to determine the test information corresponding to the test object based on the test case information respectively corresponding to the plurality of test tasks, wherein the test information includes a test progress.

[0013] According to one aspect of an embodiment of the present invention, there is provided an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement any one of the test information query methods described above.

[0014] According to one aspect of an embodiment of the present invention, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute any of the test information query methods described above.

[0015] In an embodiment of the present invention, a test information query instruction is received, wherein the test information query instruction carries a test object; in response to the test information query instruction, multiple test tasks corresponding to the test object are determined; test case information corresponding to the multiple test tasks is determined, wherein the corresponding test case information includes the execution progress of the test case item corresponding to the test case item; and test information corresponding to the test object is determined according to the test case information corresponding to the multiple test tasks, wherein the test information includes the test progress. By receiving the test information query instruction carrying the test object, it is helpful to quickly locate the test object for information query, thereby facilitating the subsequent test information query for the test object and shortening the subsequent response time. By responding to the test information query instruction and determining the multiple test tasks corresponding to the test object, it is helpful to subsequently carry out the test information query for the test object, and at the same time, it can further clarify the process of the test object being tested, thereby avoiding blind search in a large amount of data. By determining the test case information corresponding to the multiple test tasks, including the execution progress of the test case item corresponding to the test case item, it is helpful to clarify the test situation of each test case item, improve the transparency of the relevant information in the test process, thereby facilitating the subsequent rapid access to the information required for the query. By comprehensively determining the test information corresponding to the test object based on the test case information corresponding to multiple test tasks, it is possible to effectively integrate these scattered information, so as to form complete test information about the test object, so that while achieving fast feedback on queries, it is also ensured that the overall completion status of tests related to the test object can be queried, thereby solving the technical problem in related technologies that, in the software testing process, the division of labor is scattered, resulting in low query efficiency when querying relevant information of software testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0017] Figure 1 is a flow chart of a test information query method according to an embodiment of the present invention;

[0018] Figure 2 is a schematic diagram of a newly added card type in an optional implementation manner of the present invention;

[0019] Figure 3 is a schematic diagram of an electronic billboard in an optional embodiment of the present invention;

[0020] Figure 4 is a schematic diagram of test case management in an optional implementation manner of the present invention;

[0021] Figure 5 It is a schematic diagram of a newly added release plan in an optional implementation mode of the present invention;

[0022] Figure 6 is a scoring schematic diagram in an optional embodiment of the present invention;

[0023] Figure 7 It is a schematic diagram showing the project situation in an optional implementation mode of the present invention;

[0024] Figure 8 is a schematic diagram of a test report in an optional embodiment of the present invention;

[0025] Fig. 9 is a flow chart of a test information query system in an optional implementation manner of the present invention;

[0026] Fig.10 It is a system flow chart of the version release plan statistics module in an optional implementation mode of the present invention;

[0027] Fig.11 is a structural block diagram of a test information query device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] Example 1

[0031] According to an embodiment of the present invention, an embodiment of a test information query method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0032] Figure 1 is a flow chart of a test information query method according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0033] S102, receiving a test information query instruction, wherein the test information query instruction carries a test object;

[0034] In step S102 provided in the present application, a test information query instruction is received.

[0035] Among them, a test information query instruction is involved. The test information query instruction is an instruction for querying test information. The test information query instruction carries a test object.

[0036] Among them, the test object is involved, which is the specific software, functional module or system used for testing during the test process. For example, the test object can be any component of the software, from a single function, class to an entire module or function set, or a complete software application, system update or newly developed specific function.

[0037] By receiving the test information query instruction carrying the test object, it is helpful to quickly locate the test object for information query, which helps to carry out subsequent test information query for the test object, shortens the subsequent response time, avoids unnecessary query of test objects, improves query efficiency, and further helps to solve the technical problem of low query efficiency when querying relevant information of software testing due to scattered division of labor in the software testing process.

[0038] It should be noted that there is no specific limitation on the method of receiving the test information query instruction, and the method can be customized according to the actual application and scenario.

[0039] S104, in response to the test information query instruction, determining a plurality of test tasks corresponding to the test object;

[0040] In step S104 provided in the present application, a test information query instruction is responded to, and a plurality of test tasks corresponding to the test object are determined.

[0041] Among them, the test task is involved, which is determined according to the test object and is a specific task that needs to be performed. The test task may include the execution of multiple test cases, or a larger range of test activities (such as system testing, regression testing, etc.). Each test task is designed and executed around a specific test object (such as a software function, module or version update) to ensure that the object meets the predetermined requirements. The test task may include information such as the test deadline, priority, test environment, test tools, etc., and is part of the test plan.

[0042] By responding to the test information query instruction and determining the multiple test tasks corresponding to the test object, it is helpful to carry out subsequent test information query for the test object. At the same time, it can further clarify the specific test situation of the test object during the test process, which helps to track the test coverage and test history, thereby avoiding blind searching in large amounts of data, saving time and energy, and further helping to solve the technical problem of low query efficiency when querying relevant information of software testing due to scattered division of labor in related technologies in the software testing process.

[0043] It should be noted that the method for determining multiple test tasks corresponding to a test object in response to a test information query instruction is not specifically limited here and can be customized according to actual applications and scenarios.

[0044] S106, determining test case information corresponding to the plurality of test tasks respectively, wherein the corresponding test case information includes the case execution progress of the corresponding test case item;

[0045] In step S106 provided in the present application, test case information corresponding to the plurality of test tasks is determined.

[0046] Among them, test case information is involved, which is information related to the test case items during the test process of the test object. The test case information includes the test case execution progress of the test case items, such as input data, expected results, preconditions, and postconditions.

[0047] Among them, the test case item is involved. This test case item is a set of test steps designed to test a certain function or requirement, including input data, expected results, and any necessary preconditions, postconditions, etc. The test case item is obtained in the test design process and is the basic unit of test design and execution. By defining a series of test steps and expected results, the correctness of the test object's functions and performance indicators can be systematically checked to ensure that the test object can operate normally under various conditions and environments.

[0048] Among them, the use case execution progress is involved. The use case execution progress reflects the execution status and completion degree of the test case item during the test of the test object. The use case execution progress can be expressed in the form of a percentage, which is used to represent the ratio of the completed test steps of the test case item to the total number of steps in the plan.

[0049] By determining the test case information corresponding to multiple test tasks, including the execution progress of the corresponding test case items, it is helpful to clarify which test case items have been completed, which test case items are still in progress, and which test case items have not yet started, thereby improving the transparency of relevant information in the testing process, thereby facilitating subsequent rapid access to the information required for the query, thereby avoiding the process of disorderly search, and further helping to improve the query efficiency and accuracy of test information query.

[0050] It should be noted that the method for determining the test case information corresponding to multiple test tasks is not specifically limited here, and can be customized according to actual applications and scenarios.

[0051] S108, determining test information corresponding to the test object according to the test case information respectively corresponding to the plurality of test tasks, wherein the test information includes a test progress.

[0052] In step S108 provided in the present application, test information corresponding to the test object is determined.

[0053] Among them, test information is involved, which is determined according to the test case information corresponding to multiple test tasks, and is used to reflect the test situation of the test object, and may include test case information, test results, test progress, defect reports, test coverage, etc. The test information can be used as a key basis for evaluating the comprehensiveness and effectiveness of the test activities conducted on the test object, monitoring the test progress and quality, and analyzing the test results.

[0054] Among them, the test progress is involved. The test progress is an indicator used to reflect the test completion status of the current test object, which can be expressed in percentage form. The test progress can be the ratio between the number of completed test cases in the test of the test object and the total number of test cases that need to be executed, or it can be the ratio of the execution time of the test of the test object to the expected completion time in the time dimension. The test progress can be used to monitor test efficiency, predict completion time, and evaluate test volume.

[0055] By comprehensively determining the test information corresponding to the test object based on the test case information corresponding to multiple test tasks, it is possible to effectively integrate these scattered information, so as to form complete test information about the test object, so that while achieving rapid feedback on queries, it is also ensured that the overall completion status of the tests related to the test object can be queried, which helps to solve the problem in related technologies that in the process of software testing, depending on the different test tasks, the entire test division of labor is often scattered, resulting in a large amount of cost to search, screen and integrate relevant information such as data and reports from different sources when querying relevant information of software testing, resulting in a technical problem of low query efficiency.

[0056] It should be noted that the method of determining the test information corresponding to the test object based on the test case information corresponding to multiple test tasks is not specifically limited here and can be customized according to actual applications and scenarios.

[0057] Through the above steps S102-S108, a test information query instruction is received, wherein the test information query instruction carries a test object; in response to the test information query instruction, multiple test tasks corresponding to the test object are determined; test case information corresponding to multiple test tasks is determined, wherein the corresponding test case information includes the execution progress of the test case item corresponding to the test case item; and test information corresponding to the test object is determined according to the test case information corresponding to multiple test tasks, wherein the test information includes the test progress. By receiving the test information query instruction carrying the test object, it is helpful to quickly locate the test object for information query, thereby facilitating the subsequent test information query for the test object and shortening the subsequent response time. By responding to the test information query instruction and determining the multiple test tasks corresponding to the test object, it is helpful to subsequently carry out the test information query for the test object, and at the same time, it can further clarify the process of the test object being tested, thereby avoiding blind search in a large amount of data. By determining the test case information corresponding to multiple test tasks, including the execution progress of the test case item corresponding to the test case item, it is helpful to clarify the test situation of each test case item, improve the transparency of relevant information in the test process, and thus help to quickly access the information required for the query in the subsequent. By comprehensively determining the test information corresponding to the test object based on the test case information corresponding to multiple test tasks, it is possible to effectively integrate these scattered information, so as to form complete test information about the test object, so that while achieving fast feedback on queries, it is also ensured that the overall completion status of tests related to the test object can be queried, thereby solving the technical problem in related technologies that, in the software testing process, the division of labor is scattered, resulting in low query efficiency when querying relevant information of software testing.

[0058] As an optional embodiment, test information corresponding to the test object is determined based on test case information corresponding to multiple test tasks, including: when the test information includes a target indicator index, multiple evaluation items corresponding to the target indicator item are determined; from the test case information corresponding to the multiple test tasks, evaluation parameters corresponding to the multiple evaluation items are determined; and the target indicator index is determined based on the multiple evaluation parameters.

[0059] In this embodiment, specific steps of determining the test information corresponding to the test object according to the test case information respectively corresponding to a plurality of test tasks are described.

[0060] Among them, a target indicator index is involved, which is an index used to quantitatively evaluate the comprehensive quality or performance of the test object during the test process. The target indicator index can be a comprehensive score for the test process of the test object.

[0061] Among them, it involves target indicator items, which are pre-determined indicators used to evaluate the comprehensive quality or performance of the test object during the test process. The target indicator items can be determined based on pre-determined evaluation dimensions. For example, the target indicator items can include indicators such as progress control, demand quality, technical solution quality, test case (case) quality, test quality, online quality, etc. The target indicator items can also include indicators such as test quality, business understanding, entity relationship (ERD) quality, case quality, progress control, online quality, etc.

[0062] Among them, an evaluation item is involved, which is an item corresponding to the target index item and is used to evaluate the specific target index value under the target index item. The evaluation item can come directly from the result of the test case, or it can be statistical or analytical data derived from the test case information. For example, when the target index item is the quality of the test case, the evaluation item can be the pass rate of the test case, the average response time, etc.

[0063] Among them, an evaluation parameter is involved, which is a specific parameter value corresponding to the evaluation item, obtained according to the test case information corresponding to multiple test tasks, and used to directly or indirectly reflect the test situation of the test object. For example, when the evaluation is the pass rate of the test case, the corresponding evaluation parameter can be 80%.

[0064] Through the above steps, when the test information includes the target indicator index, multiple evaluation items corresponding to the target indicator items are determined, and a clear and specific test quality evaluation framework is obtained, which solves the problem of how to quantify and comprehensively evaluate the test situation of the test object, so that the test situation of the test object can be objectively and comprehensively reflected. The target indicator index obtained by further determination is determined by combining the evaluation parameters corresponding to multiple evaluation items, so that the test situation of the test object can be more comprehensively reflected, avoiding the deviation that may be caused by a single indicator, and effectively solving the subjectivity and one-sidedness of the test situation evaluation of the test object, thereby helping to provide more comprehensive and accurate test information.

[0065] As an optional embodiment, determining test case information corresponding to multiple test tasks respectively includes: when the test case information includes test case results, determining the object deployment stages corresponding to the multiple test tasks respectively; determining the target codes corresponding to the multiple object deployment stages respectively from the multiple version codes corresponding to the test object, wherein the multiple version codes correspond one-to-one to the multiple deployment stages of the test object; and testing the corresponding target codes according to the corresponding test case parameters to obtain the corresponding test case results.

[0066] In this embodiment, specific steps of determining the test case information respectively corresponding to a plurality of test tasks are described.

[0067] Among them, the object deployment phase is involved, which represents the deployment phase corresponding to the test task. Different test tasks usually belong to different deployment phases. The object deployment phase corresponding to each test task has its specific purpose and test focus, such as functional testing, performance testing, compatibility testing, etc.

[0068] Among them, a version code is involved, which corresponds one-to-one to multiple deployment stages of the test object and is a code used to represent the status of a certain deployment stage of the test object.

[0069] The target code is a version code corresponding to the object deployment phase and used for testing. The target code can be used to evaluate the performance of the test case item in the corresponding object deployment phase.

[0070] Among them, the deployment stage is involved, which is the various stages in the process of test object from development to launch, and can include unit testing, integration testing, system testing, etc.

[0071] Among them, the test case parameters are involved, and the test case parameters are parameters used to reflect the performance of the test case. Through the test case parameters, the performance of the test case can be evaluated.

[0072] Among them, the test case result is involved, which is the test result of the test case contained in the test case information and determined according to the corresponding test case parameters. The test case result may include data such as whether it passes, any errors or defects encountered during execution, performance indicators, test coverage, etc.

[0073] Through the above steps, when the test case information includes the test case results, the object deployment stages corresponding to the multiple test tasks are first determined, and then the target codes corresponding to the multiple object deployment stages are determined from the multiple version codes corresponding to the test object, wherein the multiple version codes correspond to the multiple deployment stages of the test object one by one. Then, according to the corresponding test case parameters, these corresponding target codes are tested, and finally the corresponding test case results are obtained.

[0074] By clarifying the correspondence between test tasks and object deployment stages, it can ensure that each test task focuses on the specific needs of its deployment stage, and can adjust the test strategy and resource allocation according to the stage to which the test task belongs, avoiding duplication and omission of tests, thereby improving the pertinence and efficiency of tests, and thus recording these related information for subsequent query and analysis. By determining the target code corresponding to different deployment stages from multiple versions of code, it not only simplifies the test code acquisition process, but also ensures the consistency of test results and code versions, which is conducive to the tracking and version control of test results. And this matching mechanism also helps to quickly locate and solve problems found in the test, improving the efficiency of the test process and the speed of problem solving. By testing according to clear test case parameters, the comparability and repeatability of test results can be ensured, providing a unified standard for the performance evaluation of test objects at different deployment stages. In addition, the subsequent recording and query of test case results are more efficient, thereby improving the efficiency of test management as a whole, and helping to solve the technical problem of low query efficiency when querying relevant information of software testing due to scattered division of labor in the software testing process in related technologies.

[0075] As an optional embodiment, determining test case information corresponding to multiple test tasks respectively includes: when the test case information includes predicted case results, determining associated test case information corresponding to the test case item, wherein the associated test case information is information corresponding to the completed associated test case item, and the associated test case information includes a case completion cycle; inputting the test case item and the associated test case information into an information prediction model to obtain a predicted case result corresponding to the test case item, wherein the predicted case result includes a predicted completion cycle, and the information prediction model is a model trained based on sample data.

[0076] In this embodiment, specific steps of determining the test case information respectively corresponding to a plurality of test tasks are described.

[0077] Among them, it involves predicted case results, which are obtained by predicting test case items and associated test case information through a prediction model, and are predicted results of possible test results when testing the test case items.

[0078] Among them, the associated test case information is involved, and the associated test case information refers to the information of the completed test cases related to the current test case item. The associated test case information may include the execution results, execution time, test environment used, etc. of the case. For example, the current test case involves the test of a certain functional module, and the associated test case information includes the previous test results and cycles of the related functional modules.

[0079] Among them, a use case completion cycle is involved, and the use case completion cycle is the completion cycle of the test case corresponding to the associated test case information.

[0080] Among them, an information prediction model is involved, which is a model trained based on sample data and used to predict test results of test case information.

[0081] Among them, the predicted completion cycle is involved, which is a prediction of the time required for the execution of the test case item based on the information prediction model. The predicted completion cycle can be a specific value (such as a prediction of 20 hours) or a time range (such as a prediction of completion between 18 and 22 hours).

[0082] Among them, sample data is involved, which is historical data used to train the information prediction model, and these data can be completed test case information, test results, test time, etc. For example, all the case data that have been executed and associated with the current test case item can be used as sample data for training the model.

[0083] Through the above steps, when the test case information includes the predicted case result, the associated test case information corresponding to the test case item is determined, and the associated test case information is the information corresponding to the completed associated test case item, and the associated test case information includes the corresponding case completion cycle. Then, the test case item and the associated test case information are input into the information prediction model that has been trained with the sample data, and finally the predicted case result corresponding to the test case item is obtained.

[0084] By determining the associated test case information corresponding to the test case item, the associated test case information is the information corresponding to the completed associated test case item, and the associated test case information includes the corresponding case completion cycle, a rich and specific data basis can be provided for the information prediction model, helping the model to learn and predict more accurately. By automatically determining the associated test case information, the tediousness of manually searching for relevant information is avoided. Due to the scattered division of labor in the software testing process, there is a technical problem of low query efficiency when querying relevant information of software testing, thereby improving the accuracy of test planning and time prediction, thereby improving testing efficiency. By inputting the current test case item and its associated completed test case information into the information prediction model, the model can predict the completion cycle and results of the current case based on the patterns and rules learned from the historical sample data, realizing the objective analysis from subjective judgment to data-driven, thereby improving the scientificity and accuracy of the prediction.

[0085] As an optional embodiment, receiving a test information query instruction includes: receiving an execution request for executing a test case to be executed; in response to the execution request, triggering the test information query instruction to obtain test information including associated progress information, wherein the test information query instruction also carries the test case to be executed, and the associated progress information is information associated with the test case to be executed and corresponding to the test case with update progress.

[0086] In this embodiment, the specific steps of receiving the test information query instruction are described.

[0087] Among them, it involves the pending test cases, which are the cases that need to be tested during the test process of the test object, but have not yet started to be tested. For example, after the development of a new software function, a series of test cases will be created to verify its correctness and stability, and those test cases that have not yet been executed are the pending test cases.

[0088] Among them, an execution request is involved, and the execution request is a request for requesting the execution of a test case to be executed, and is used to trigger a test information query instruction.

[0089] Among them, the associated progress information is involved, and the associated progress information is the progress information of other completed or executing test cases related to the test case to be executed. For example, if the test case to be executed is a test on the software user interface, then the associated progress information may include the execution progress and results of the previous test cases on the same function or related functions. And if the test case corresponding to the associated progress information has updated the progress, then the associated progress information includes the information corresponding to the test case with updated progress.

[0090] Among them, the update progress is involved, which is used to indicate the change of the state of the test case during the execution process. The update progress can be a state transition from "not executed" to "executing", from "executing" to "passed" or "failed", as well as progress updates at any time point during the execution process. For example, when a test case starts to execute, its status will be updated from "not executed" to "executing", and the real-time execution progress will be recorded as the test progresses.

[0091] Through the above steps, an execution request for executing the test case to be executed is first received, then the execution request is responded to, and a test information query instruction carrying the test case to be executed is triggered to obtain test information including associated progress information, which is information associated with the test case to be executed and corresponding to the test case with update progress.

[0092] By receiving and responding to execution requests for executing test cases to be executed and triggering test information query instructions carrying test cases to be executed, subsequent targeted operations on test cases to be executed are implemented, which helps to quickly obtain test information including associated progress information related to the test cases to be executed, optimizes information query speed and accuracy, ensures that all test information related to the test cases to be executed can be quickly obtained, and avoids the tediousness and possible errors of manual queries.

[0093] As an optional embodiment, after determining the test information corresponding to the test object based on the test case information corresponding to multiple test tasks, it also includes: determining the use case impact result based on the associated progress information; when the use case impact result is to affect the use case process of the test case to be executed, changing the test case parameters of the test case to be executed to obtain updated test case parameters, so as to execute the test on the test case to be executed under the updated test case parameters.

[0094] In this embodiment, the specific steps after determining the test information corresponding to the test object according to the test case information respectively corresponding to the plurality of test tasks are described.

[0095] Among them, the use case impact result is involved, which is determined based on the associated progress information and is used to indicate whether the test case to be executed has an impact. For example, the use case impact result can be a situation where the use case progress of the test case to be executed is affected, or a situation where the use case progress of the test case to be executed is not affected.

[0096] Among them, the use case process is involved, which is the status and progress of the test case during execution.

[0097] Among them, it involves updating test case parameters, which are parameters obtained by updating the test case parameters of the test case to be executed based on the associated progress information. The updated test case parameters can modify the parameters originally used to execute the test case to be executed after identifying the impact of the case (that is, the execution of the associated test case may affect the test case to be executed) to adapt to the new situation or demand. For example, if the associated test case finds a problem with a certain function in a specific environment, then updating the test case parameters can include a record of the corresponding related parameters, which can increase the test of the environment, modify the input data or environment configuration, etc., or after recording and updating, there is no need to repeat the test of the function.

[0098] Through the above steps, the corresponding use case impact result is determined according to the associated progress information. When the use case impact result is to affect the use case process of the test case to be executed, the test case parameters of the test case to be executed are changed to obtain updated test case parameters, and the test is performed on the test case to be executed under the updated test case parameters.

[0099] By determining the impact results of the use case based on the associated progress information, it helps to avoid the waste of test resources and ensure the pertinence and effectiveness of the test, that is, when the impact result of the use case is that it does not affect the use case process of the test case to be executed, there is no need to perform subsequent update operations. When the impact result of the use case is that it affects the use case process of the test case to be executed, the test case parameters of the test case to be executed are changed to obtain updated test case parameters, and the test is performed on the test case to be executed under the updated test case parameters, so that the use case impact results can be adapted to ensure that the subsequent test cases to be executed can be executed in the most effective state, which can not only avoid invalid or repeated tests, but also increase the test of the environment according to the update situation, or modify the input data to more comprehensively verify the repair situation, thereby reducing test failures or invalid tests caused by improper parameter configuration, ensuring that the test can timely reflect the latest status of the software, improve test efficiency and quality, and optimize the processing flow of test information, which helps to effectively solve the problem of low query efficiency caused by scattered division of labor.

[0100] As an optional embodiment, determine the code change result of the test object; when the code change result is the code change of the test object, determine the update test task from multiple test tasks based on the update code; update the test case item corresponding to the update test task to obtain an update use case item; determine the update use case information corresponding to the update test tasks, wherein the update use case information includes the use case execution progress of the corresponding update use case item.

[0101] In this embodiment, specific steps of determining update use case information respectively corresponding to update test tasks are described.

[0102] The code change result is used to determine whether the code of the test object has been changed, for example, adding new functions, fixing defects or optimizing performance to the code of the test object.

[0103] Among them, it involves updated code, which is the code obtained after the code of the test object is changed. For example, the updated code fixes defects in the original code or adds new functions.

[0104] Among them, it involves update test tasks, which are updated test tasks determined from multiple test tasks after the code is changed, and are determined based on the updated code. For example, after the code is changed, in order to verify whether the change is correct and whether new problems are introduced, it is necessary to re-execute or add new test tasks (i.e., update test tasks). These update test tasks can be used to verify the correctness and stability of the changed part, or they can involve regression testing of the entire functional module.

[0105] Among them, the update use case item is involved, which is a specific test case item that needs to be executed in the update test task. For example, for the code change of the user login module, the update use case item may include a use case for verifying the new login function and a use case for verifying the interaction between the login function and other functions.

[0106] Among them, update use case information is involved, and the update use case information is the relevant information of the update use case item during the testing process. The update use case information includes the use case execution progress corresponding to the update use case item.

[0107] Through the above steps, the code change result of the test object is first determined. When the code change result is a code change of the test object, the corresponding update test task is determined from multiple test tasks according to the update code. Then, the test case item corresponding to the update test task is updated to obtain the update use case item, and the update test task corresponding to each other is determined, including the update use case execution progress of the corresponding update use case item.

[0108] By determining the code change result of the test object, it helps to avoid the waste of test resources, that is, when the code change result is that the test object has not undergone code changes, there is no need to perform subsequent update operations, avoiding unnecessary testing of unchanged code, thereby improving the pertinence and efficiency of the test. In the case where the code change result is a code change of the test object, the corresponding update test task is determined from multiple test tasks according to the update code, and the test case item corresponding to the update test task is updated to obtain the update case item, and the update case information including the execution progress of the case corresponding to the update case item is determined, thereby achieving the test of the test points that really need attention, avoiding the dispersion and waste of test resources, and ensuring the comprehensiveness of the test. By updating the case item, it can ensure that the test and development are kept in sync, avoiding the deviation of test results caused by case mismatch, improving the effectiveness and reliability of the test, and optimizing the processing flow of test information, which helps to effectively solve the problem of low query efficiency caused by scattered division of labor.

[0109] Based on the above embodiments and optional embodiments, an optional implementation is provided, which is described in detail below.

[0110] In the related technology, during the software testing process, depending on the different testing tasks, the entire testing division of labor is often scattered, resulting in a large amount of cost to search, screen and integrate relevant information from different data and reports when querying relevant information of the software testing, resulting in a technical problem of low query efficiency.

[0111] To address the above-mentioned problems, no effective solution has been proposed yet.

[0112] In view of this, a test information query method and system are provided in an optional embodiment of the present invention, which can also be called a WEB-based software testing management method and system, which can effectively solve the technical problem in the related technology that the software testing process has scattered division of labor, resulting in low query efficiency when querying relevant information of the software test.

[0113] Figure 2 is a schematic diagram of a newly added card type in an optional implementation manner of the present invention, Figure 3 is a schematic diagram of an electronic billboard in an optional embodiment of the present invention, Figure 4 is a schematic diagram of test case management in an optional implementation manner of the present invention, Figure 5 is a schematic diagram of a newly added version release plan in an optional implementation mode of the present invention, Figure 6 is a scoring schematic diagram in an optional embodiment of the present invention, Figure 7 It is a schematic diagram showing the project situation in an optional implementation mode of the present invention. Figure 8 is a schematic diagram of a test report in an optional embodiment of the present invention, Fig. 9is a flow chart of a test information query system in an optional implementation mode of the present invention, Fig.10 It is a system flow chart of the release plan statistics module in an optional implementation mode of the present invention, and is specifically described as follows.

[0114] (I) Test information query method:

[0115] S1. Receive a test information query instruction, wherein the test information query instruction carries a test object;

[0116] Specifically, S1 also includes:

[0117] S11, receiving an execution request for executing a test case to be executed;

[0118] S12. In response to the execution request, a test information query instruction is triggered to obtain test information including associated progress information, wherein the test information query instruction also carries a test case to be executed, and the associated progress information is a test case associated with the test case to be executed and has an update progress.

[0119] For example, the test object can be any component of the software, from a single function, class to an entire module or set of functions, or it can be a complete software application, a system update, or a newly developed specific function.

[0120] S2. In response to the test information query instruction, determine a plurality of test tasks corresponding to the test object;

[0121] For example, the test task may include the execution of multiple test cases, or a larger range of test activities (such as system testing, regression testing, etc.). Each test task is designed and executed around a specific test object (such as a software function, module, or version update) to ensure that the object meets the predetermined requirements. The test task may include information such as the test deadline, priority, test environment, and test tools, and is part of the test plan.

[0122] S3, determining the test case information corresponding to the multiple test tasks respectively, wherein the corresponding test case information includes the case execution progress of the corresponding test case item;

[0123] For example, the test case information may include input data, expected results, preconditions, and postconditions, etc. The test case item is obtained in the test design process and is the basic unit of test design and execution. By defining a series of test steps and expected results, the correctness and performance indicators of the test object functions can be systematically checked to ensure that the test object can operate normally under various conditions and environments. The use case execution progress can be expressed in the form of a percentage, which is used to characterize the ratio of the completed test steps of the test case item to the total number of steps in the plan. Table 1 is an example table of the test task progress provided by an optional implementation of the present invention. As shown in Table 1, the test task progress may include the smoke execution progress and the use case execution progress, wherein the smoke execution progress is the progress of the most basic functional testing of a new version after the development of the new version is completed during the software development process.

[0124] Table 1

[0125]

[0126] Specifically, S3 also includes:

[0127] S301, when the test case information includes test case results, determining object deployment phases corresponding to a plurality of test tasks respectively;

[0128] S302, determining target codes corresponding to multiple object deployment stages respectively from multiple version codes corresponding to the test object, wherein the multiple version codes correspond to the multiple deployment stages of the test object one-to-one;

[0129] S303. Test the corresponding target codes according to the corresponding test case parameters to obtain the corresponding test case results.

[0130] Specifically, S3 also includes:

[0131] S311. When the test case information includes a predicted test case result, determine associated test case information corresponding to the test case item, wherein the associated test case information is information corresponding to a completed associated test case item, and the associated test case information includes a case completion cycle;

[0132] S312. Input the test case item and the associated test case information into the information prediction model to obtain the predicted case result corresponding to the test case item, wherein the predicted case result includes the predicted completion period, and the information prediction model is a model trained based on the sample data.

[0133] S4. Determine test information corresponding to the test object based on the test case information corresponding to the multiple test tasks, wherein the test information includes the test progress.

[0134] For example, test information may include test case information, test results, test progress, defect reports, test coverage, etc. The test information can serve as a key basis for evaluating the comprehensiveness and effectiveness of test activities on the test object, monitoring test progress and quality, and analyzing test results.

[0135] Specifically, S4 also includes:

[0136] S41. When the test information includes a target indicator index, determine a plurality of evaluation items corresponding to the target indicator item;

[0137] S42, determining evaluation parameters corresponding to the plurality of evaluation items respectively from the test case information corresponding to the plurality of test tasks respectively;

[0138] S43. Determine the target indicator index based on multiple evaluation parameters.

[0139] For example, the target indicator items may include progress control, demand quality, technical solution quality, test case quality, test quality, online quality, etc. In the case where the target indicator item is the test case quality, the evaluation item may be the pass rate of the test case, the average response time, etc. In the case where the evaluation item is the pass rate of the test case, the corresponding evaluation parameter may be 80%.

[0140] S5, after determining the test information corresponding to the test object according to the test case information corresponding to the plurality of test tasks, the method further includes:

[0141] S6. Determine the impact results of the use case based on the associated progress information;

[0142] S7. When the use case impact result is to affect the use case process of the test case to be executed, the test case parameters of the test case to be executed are changed to obtain updated test case parameters, so as to execute the test on the test case to be executed under the updated test case parameters.

[0143] After that, the corresponding steps of updating the code of the test object are also included, including:

[0144] A1. Determine the code change results of the test object;

[0145] A2. When the code change result is a code change of the test object, determine the update test task from the multiple test tasks according to the update code;

[0146] A3. Update the test case item corresponding to the update test task to obtain the update case item;

[0147] A4. Determine the update use case information corresponding to the update test tasks, wherein the update use case information includes the use case execution progress of the corresponding update use case item.

[0148] For example, Table 2 is an example table of release plan statistics (same as the above-mentioned code changes) provided by an optional implementation manner of the present invention, as shown in Table 2.

[0149] Table 2

[0150]

[0151] (II) Test information query system:

[0152] The test information query system is designed based on B / S architecture, and consists of three main components: the front-end Web server (built using the VUE framework) provides a user interaction interface, the application logic server (based on the Flask framework) processes business logic, and the database server (using MySQL) stores data. This architecture not only ensures the high availability and scalability of the system, but also facilitates subsequent maintenance and upgrades.

[0153] Optionally, the test information query system provides an intuitive graphical user interface (GUI) that allows users to enter key information of the release, including work order number, scheduled release date, dependencies, and risk assessment. In order to improve user experience and efficiency, the system presets a series of templates and can automatically match corresponding test tasks (same as the above test tasks) according to the keywords entered by the user. After selecting a specific test task, the system automatically retrieves and displays relevant information of the task (same as the above test case information), such as project line, product name, etc. This design not only reduces the need for manual input, but also ensures that the creation process of the release (same as the above version code) plan is fast and accurate. Specifically, it includes functions such as test task electronic dashboard module, test case management module, release plan statistics module, project scoring (same as the above target indicator index) and test report output module to improve the efficiency and quality of software testing.

[0154] (1) Test task electronic signboard module:

[0155] The test task electronic board module introduces the electronic board as the core task management tool, providing an intuitive task progress visualization interface. It supports the creation and status management of multiple task types, as well as condition-based task filtering functions, greatly improving the transparency and efficiency of test management.

[0156] The electronic signboard module of this test task can realize the following functions:

[0157] 1) Realize visual management of test tasks, including creation, assignment, and execution status tracking of test tasks.

[0158] 2) Support drag-and-drop operation to facilitate the scheduling and management of test tasks.

[0159] 3) Provide real-time display of test task progress to determine test progress and quality.

[0160] (2) Test case management module:

[0161] The test case management module provides a comprehensive test case management solution, including the creation, execution, and management of test cases. By supporting multiple formats and batch import, as well as detailed records of test case execution results, the module aims to improve the accuracy and efficiency of testing.

[0162] The test case management module can achieve the following functions:

[0163] 1) Implement test case creation, management and execution tracking.

[0164] 2) Support version management of test cases (same as the version code above) to ensure the consistency of test cases and software versions.

[0165] 3) Provides a variety of test case templates to facilitate the rapid creation and maintenance of test cases.

[0166] (3) Release plan statistics module:

[0167] The release plan statistics module integrates the creation, query, analysis and notification functions of the release plan. This module helps to better plan and evaluate release activities through a data-driven approach to ensure an efficient and orderly release process.

[0168] The release plan statistics module can achieve the following functions:

[0169] 1) Query function: equipped with a powerful query interface, users can quickly retrieve the release plan by work order number, release date or other custom fields. The query results will be displayed in a list format, allowing users to easily analyze the data and further optimize the release process.

[0170] 2) Analysis function: Provide key performance indicators (KPIs) by collecting and analyzing historical release data. These analyses include:

[0171] B1. Descriptive analysis: basic statistics on key indicators such as release cycle and success rate, providing an intuitive data overview.

[0172] B2. Correlation analysis: Apply statistical methods to explore how different factors (such as changes in technology stack, etc.) affect the success rate and cycle of releases.

[0173] B3. Regression analysis: Use regression models to predict release cycles under specific conditions and provide data support for resource allocation and optimization.

[0174] B4. Time series analysis: Analyze the time series data of release planning and implementation, predict future release trends, and assist in formulating future release plans.

[0175] These analytical functions not only help evaluate and improve release efficiency and quality, but also promote continuous optimization of the process.

[0176] 3) Notification function: In order to ensure timely updates and warnings of release status, an information notification robot is integrated. By automatically sending notifications, it ensures immediate understanding and response to any emergency situations during the release process, further ensuring the smooth progress of the release process.

[0177] (4) Project scoring and test report output module:

[0178] The project scoring and test report output module not only promotes the continuous improvement of test quality, but also strengthens information transfer through the report sharing mechanism by setting scoring standards (same as the above evaluation items) for each dimension of the project (same as the above target indicators) and conducting in-depth analysis of the test results.

[0179] The project scoring and test report output module can achieve the following functions:

[0180] 1) Automatically generate test reports, including key information such as test coverage, defect distribution, and test execution status.

[0181] 2) The test report can be exported in multiple formats, making it easy to share and communicate with project-related personnel.

[0182] 3) Test reports can be generated regularly or on demand to meet project management needs at different stages.

[0183] By integrating various aspects of test management, the system realizes full-process management from test planning, case management to test execution and result evaluation, effectively improving the efficiency and quality of software testing.

[0184] Through the above optional implementation, at least the following beneficial effects can be achieved:

[0185] (1) Compared with the related art, the present invention helps to quickly locate the test object for information query by receiving the test information query instruction carrying the test object, thereby helping to carry out the test information query for the test object in the future and shortening the response time in the future. By responding to the test information query instruction and determining the multiple test tasks corresponding to the test object, it helps to carry out the test information query for the test object in the future, and at the same time, it can further clarify the process of the test object being tested, thereby avoiding blind search in a large amount of data. By determining the test case information corresponding to the multiple test tasks, including the test case execution progress of the corresponding test case items, it helps to clarify the test situation of each test case item, improves the transparency of the relevant information in the test process, and helps to quickly access the information required for the query in the future. By comprehensively determining the test information corresponding to the test object according to the test case information corresponding to the multiple test tasks, it is achieved to effectively integrate these scattered information, so that complete test information about the test object can be formed, so that while realizing the rapid feedback of the query, it is also ensured that the overall completion status of the test related to the test object can be queried, thereby solving the technical problem in the related art that the scattered division of labor in the software testing process leads to low query efficiency when querying the relevant information of the software test.

[0186] (2) Compared with the related art, the present invention determines multiple evaluation items corresponding to the target indicator items when the test information includes the target indicator index, and obtains a clear and specific test quality evaluation framework, which solves the problem of how to quantify and comprehensively evaluate the test situation of the test object, thereby being able to objectively and comprehensively reflect the test situation of the test object. The target indicator index determined by the present invention is obtained by combining the evaluation parameters corresponding to the multiple evaluation items, thereby being able to more comprehensively reflect the test situation of the test object, avoiding the deviation that may be caused by a single indicator, and effectively solving the subjective and one-sided problems in the evaluation of the test situation of the test object, thereby helping to provide more comprehensive and accurate test information.

[0187] (3) Compared with related technologies, by clarifying the correspondence between test tasks and object deployment stages, it can ensure that each test task focuses on the specific needs of its deployment stage, and can adjust the test strategy and resource allocation according to the stage to which the test task belongs, avoiding duplication and omission of tests, thereby improving the pertinence and efficiency of the test. The associated information recorded accordingly is convenient for subsequent query and analysis. By determining the target code corresponding to different deployment stages from multiple versions of code, it not only simplifies the test code acquisition process, but also ensures the consistency of test results and code versions, which is conducive to the tracking and version control of test results. Moreover, this matching mechanism also helps to quickly locate and solve problems found in the test, improving the efficiency of the test process and the speed of problem solving. By testing according to clear test case parameters, the comparability and repeatability of test results can be ensured, providing a unified standard for the performance evaluation of the test object at different deployment stages. This makes the subsequent recording and query of test case results more efficient, thereby improving the efficiency of test management as a whole.

[0188] (4) Compared with the related art, the present invention can provide a rich and specific data basis for the information prediction model by determining the associated test case information corresponding to the test case item, and the associated test case information is the information corresponding to the completed associated test case item, and the associated test case information includes the corresponding case completion cycle, so as to help the model learn and predict more accurately. By automatically determining the associated test case information, the tediousness of manually searching for relevant information is avoided. Due to the scattered division of labor in the software testing process, there is a technical problem of low query efficiency when querying the relevant information of the software test, thereby improving the accuracy of the test plan and time prediction, thereby improving the test efficiency.

[0189] (5) Compared with the prior art, the present invention realizes intuitive monitoring of the progress of test tasks through the intuitive management of electronic boards and the real-time updated test task electronic boards, effectively shortens the project management time and improves the test efficiency. Through the optimization of test case management, a highly automated test case management function is introduced, which reduces duplication of work, speeds up the writing and execution of test cases, and significantly improves the efficiency of test execution. Through accurate statistics of release plans and accurate analysis of the execution of release plans, project bottlenecks are quickly identified, thereby improving the overall release efficiency. Through quantitative analysis of project scores, a project scoring mechanism is introduced, and the test quality is evaluated through quantitative analysis methods, which provides a basis for discovering potential quality problems and formulating improvement measures. And through in-depth analysis of test reports, problems in the test process can be discovered and solved in a timely manner, ensuring the accuracy and reliability of test results. And through continuous tracking of test result trends, continuous monitoring and analysis of test result trends are achieved, promoting continuous improvement and optimization of test processes and quality.

[0190] (6) Compared with the related art, the present invention realizes a set of WEB-based software testing management system, whose core advantage is that it can comprehensively manage all stages within the software testing cycle, and significantly improve the efficiency and output quality of the testing process through automated and intelligent tools. The system adopts an advanced B / S architecture, which not only ensures the high customizability and easy deployment of the system, but also promotes the ease of use and scalability. The system integrates multiple key modules to provide a one-stop solution for the software testing process, thereby achieving comprehensive coverage and efficient management of testing activities. And by designing a simple and intuitive user interface, the system reduces the complexity of operation, makes operation convenient, and further improves the efficiency and experience of testing work.

[0191] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0192] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of various embodiments of the present invention.

[0193] Example 2

[0194] According to an embodiment of the present invention, a device for implementing the above test information query method is also provided. Fig.11 is a structural block diagram of a test information query device according to an embodiment of the present invention. Fig.11 As shown, the device includes: a receiving module 1102, a first determining module 1104, a second determining module 1106 and a third determining module 1108. The device is described in detail below.

[0195] The receiving module 1102 is used to receive a test information query instruction, wherein the test information query instruction carries a test object;

[0196] A first determining module 1104, connected to the receiving module 1102, is used to determine a plurality of test tasks corresponding to the test object in response to the test information query instruction;

[0197] A second determination module 1106, connected to the first determination module 1104, is used to determine the test case information corresponding to the plurality of test tasks, wherein the corresponding test case information includes the case execution progress of the corresponding test case item;

[0198] The third determining module 1108 is connected to the second determining module 1106 and is used to determine the test information corresponding to the test object according to the test case information respectively corresponding to the plurality of test tasks, wherein the test information includes the test progress.

[0199] It should be noted here that the above-mentioned receiving module 1102, the first determination module 1104, the second determination module 1106 and the third determination module 1108 correspond to steps S102 to S108 in implementing the test information query method, and the instances and application scenarios implemented by the multiple modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned embodiment 1.

[0200] Example 3

[0201] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, comprising: a processor; and a memory for storing processor executable instructions, wherein the processor is configured to execute instructions to implement any of the above test information query methods.

[0202] Example 4

[0203] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can execute any of the above test information query methods.

[0204] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0205] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0206] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0207] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0208] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0209] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0210] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A test information query method, characterized in that: include: Receiving a test information query instruction, wherein the test information query instruction carries a test object; In response to the test information query instruction, determining a plurality of test tasks corresponding to the test object; Determine the test case information corresponding to the multiple test tasks respectively, wherein the corresponding test case information includes the case execution progress of the corresponding test case item; According to the test case information respectively corresponding to the multiple test tasks, test information corresponding to the test object is determined, wherein the test information includes a test progress.

2. The method according to claim 1, characterized in that The determining, based on the test case information respectively corresponding to the plurality of test tasks, the test information corresponding to the test object comprises: In the case where the test information includes a target indicator index, determining a plurality of evaluation items corresponding to the target indicator item; Determining evaluation parameters corresponding to the multiple evaluation items respectively from the test case information corresponding to the multiple test tasks respectively; The target indicator index is determined based on multiple evaluation parameters.

3. The method according to claim 1, characterized in that The determining of the test case information corresponding to the plurality of test tasks respectively includes: In a case where the test case information includes test case results, determining object deployment phases corresponding to the plurality of test tasks respectively; Determining target codes corresponding to multiple object deployment stages respectively from multiple version codes corresponding to the test object, wherein the multiple version codes correspond one-to-one to the multiple deployment stages of the test object; According to the corresponding test case parameters, the corresponding target codes are tested to obtain the corresponding test case results.

4. The method according to claim 1, characterized in that: The determining of the test case information corresponding to the plurality of test tasks respectively includes: In the case where the test case information includes a predicted case result, determining associated test case information corresponding to the test case item, wherein the associated test case information is information corresponding to a completed associated test case item, and the associated test case information includes a case completion cycle; The test case item and the associated test case information are input into the information prediction model to obtain the predicted case result corresponding to the test case item, wherein the predicted case result includes a predicted completion cycle, and the information prediction model is a model trained based on sample data.

5. The method according to claim 1, characterized in that The receiving of the test information query instruction comprises: receiving an execution request for executing a test case to be executed; In response to the execution request, the test information query instruction is triggered to obtain test information including associated progress information, wherein the test information query instruction also carries a test case to be executed, and the associated progress information is information associated with the test case to be executed and corresponding to the test case with update progress.

6. The method according to claim 5, characterized in that After determining the test information corresponding to the test object according to the test case information respectively corresponding to the plurality of test tasks, the method further includes: Determine the impact result of the use case based on the associated progress information; In the case where the use case impact result affects the use case process of the test case to be executed, the test case parameters of the test case to be executed are changed to obtain updated test case parameters, so as to execute the test on the test case to be executed under the updated test case parameters.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: Determining a code change result of the test object; In a case where the code change result is a code change of the test object, determining an update test task from the plurality of test tasks according to the update code; Update the test case item corresponding to the update test task to obtain an update case item; Determine the update use case information corresponding to the update test tasks respectively, wherein the update use case information includes the use case execution progress of the corresponding update use case item.

8. A test information query device, characterized in that: include: A receiving module, used for receiving a test information query instruction, wherein the test information query instruction carries a test object; A first determining module, configured to determine a plurality of test tasks corresponding to the test object in response to the test information query instruction; A second determination module is used to determine the test case information corresponding to the plurality of test tasks respectively, wherein the corresponding test case information includes the case execution progress of the corresponding test case item; The third determination module is used to determine the test information corresponding to the test object according to the test case information respectively corresponding to the multiple test tasks, wherein the test information includes the test progress.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the test information query method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the test information query method according to any one of claims 1 to 7.

Images