System interaction method, device, equipment and medium

Abstract

The present application discloses a system interaction method, which relates to the field of computers. The method includes: monitoring the execution status of projects in a preset demand management system according to a preset monitoring method, determining the project that meets the preset first condition as the first target project, and sending a stage update instruction to the preset demand management system; the preset demand management system receives the stage update instruction, determines the project whose current demand execution stage is the preset stage in the first target project as the second target project, and queries its use case execution result from the preset test case management system; if the result is execution failure, the bug status in the bug information of the second target project is determined through the preset defect management system; based on the bug status and the use case execution result, the actual demand execution stage is determined, and it is judged whether the current demand stage is consistent with the actual demand stage; if not, the current demand stage is updated to the actual demand stage. The present invention can reduce the testing cost when managing requirements, use cases, and bugs on different platforms.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a system interaction method, device, equipment and medium. Background Art

[0002] With the development of technology and the Internet, there are more and more demand management systems, use case management systems, and defect management systems. Among them, open source development management software such as ZenTao, Jira, and Metersphere are widely used in daily work. However, due to the differences in business between companies, sometimes it is necessary to maintain requirements, use cases, and bugs on different systems. At this time, because the various software are not interoperable, when testers perform demand testing or submit bugs, they can only achieve association manually. Among them, the demand development stage in ZenTao is an important parameter for demand management. The options for this parameter generally include: not started (wait), planned (planned), projected (projected), closed (closed), developing (developing), developed (developed), submitted for testing (showcase), testing (testing), tested (tested), etc. Project managers can use this indicator to confirm the current stage of the demand and judge whether the project progress is normal.

[0003] Currently, if requirements, use cases, and bugs need to be managed separately on multiple platforms (such as ZenTao, metersphere, and jira), when updating the stage to which a requirement belongs in ZenTao, it is necessary to manually calculate the stage to which the requirement belongs based on the execution status of multiple use cases on the use case management system, and then find the corresponding requirement in ZenTao and change the development stage of the requirement one by one. This may result in uncertainties such as update errors, resulting in a huge waste of time and manpower.

[0004] As can be seen from the above, in the process of project requirement testing, how to avoid the situation where the project progress update operation in the requirement management system is complicated and laborious due to manual association of the system is a problem to be solved in the art. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a system interaction method, device, equipment and medium, which can automatically connect the demand management system, the use case management system and the defect management system, and then use the interaction of the three systems to realize the automatic and accurate update of the project progress, and can automatically add test cases for bugs that do not have test cases, thereby improving the testing efficiency. The specific scheme is as follows:

[0006] In a first aspect, the present application discloses a system interaction method, comprising:

[0007] Monitor the execution status of all projects in the preset demand management system according to the preset monitoring method, determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system;

[0008] When the preset requirement management system receives the stage update instruction, the project whose current requirement execution stage is the preset stage in the first target project is determined as the second target project, and the test case execution result of the second target project is queried from the preset test case management system;

[0009] If the execution result of the use case is execution failure, determining the bug status in the bug information corresponding to the second target project through a preset defect management system;

[0010] Determine the actual demand execution stage of the second target project based on the bug status and the use case execution result, and judge whether the current demand stage of the second target project is consistent with the actual demand stage;

[0011] If the current demand stage of the second target project is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage.

[0012] Optionally, monitoring the execution status of all projects in a preset demand management system according to a preset monitoring method includes:

[0013] A management service for monitoring the execution status of projects is created in the control layer in the preset demand management system, and the execution status of all projects in the preset demand management system is monitored through the management service according to a preset monitoring method.

[0014] Optionally, monitoring the execution status of all projects in a preset demand management system according to a preset monitoring method includes:

[0015] Determine the current time and the planned completion time corresponding to each project in the preset demand management system;

[0016] Determine the project corresponding to the planned completion time being greater than the current time and satisfying the preset first time difference condition as the first project, and monitor the execution status of the first project according to the first monitoring frequency;

[0017] Determine the project whose planned completion time is greater than the current time and satisfies the preset second time difference condition as the second project, and monitor the execution status of the second project according to the second monitoring frequency;

[0018] The project whose planned completion time is less than the current time is determined as a third project, and the execution status of the third project is monitored according to a third monitoring frequency.

[0019] Optionally, when the preset requirement management system receives the stage update instruction, the project whose current requirement execution stage is the preset stage in the first target project is determined as the second target project, and the test case execution result of the second target project is queried from the preset test case management system, including:

[0020] When the control layer in the preset demand management system receives the stage update instruction, the model layer in the preset demand management system is called to determine the demand and the current demand execution stage corresponding to the first target project from the database connected to the preset demand management system, and the project in the first target project whose current demand execution stage is the preset stage is determined as the second target project;

[0021] The model layer is called to send a query request for querying the use case execution result of the second target project to a preset test case management system to obtain the use case execution result of the second target project.

[0022] Optionally, determining the project whose current demand execution stage is a preset stage in the first target project as the second target project includes:

[0023] The project in the first target project whose current requirement execution stage is in the testing or testing submitted state is determined as the second target project.

[0024] Optionally, after determining the project whose current demand execution stage is a preset stage among the first target projects as the second target project, the method further includes:

[0025] generating a first character string based on the requirement corresponding to the second project and the current requirement execution stage;

[0026] Accordingly, determining the actual requirement execution stage of the second target project based on the bug status and the use case execution result, and judging whether the current requirement stage of the second target project is consistent with the actual requirement stage, includes:

[0027] Based on the bug status and the use case execution result, the actual requirement execution phase of the second target project is determined to generate a second string, and it is determined whether the first string is consistent with the second string.

[0028] Optionally, after determining the project whose execution status meets the preset first condition as the first target project, the method further includes:

[0029] Obtaining a project bug list of the first target project through an interface provided by a preset defect management system, and determining bugs without test cases in the project bug list as test cases to be supplemented;

[0030] Based on the bug information corresponding to the use case item to be supplemented in the project bug list, and using the use case template preset in the preset test case management system, a use case is created for the use case item to be supplemented.

[0031] In a second aspect, the present application discloses a system interaction device, comprising:

[0032] A status monitoring module, used to monitor the execution status of all projects in the preset demand management system according to a preset monitoring method, and determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system;

[0033] A requirement query module, configured to determine, when the preset requirement management system receives the stage update instruction, a project in the first target project whose current requirement execution stage is the preset stage as a second target project, and query the test case execution result of the second target project from the preset test case management system;

[0034] A bug status determination module, configured to determine the bug status in the bug information corresponding to the second target project through a preset defect management system if the execution result of the use case is an execution failure;

[0035] An actual demand determination module, used to determine the actual demand execution stage of the second target project based on the bug status and the use case execution result, and to determine whether the current demand stage of the second target project is consistent with the actual demand stage;

[0036] The demand updating module is used to update the current demand stage in the preset demand management system to the actual demand stage if the current demand stage of the second target project is inconsistent with the actual demand stage.

[0037] In a third aspect, the present application discloses an electronic device, comprising:

[0038] Memory, used to store computer programs;

[0039] The processor is used to execute the computer program to implement the aforementioned system interaction method.

[0040] In a fourth aspect, the present application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned disclosed system interaction method are implemented.

[0041] The present application first monitors the execution status of all projects in the preset demand management system according to the preset monitoring method, and determines the project whose execution status meets the preset first condition as the first target project, and then sends a stage update instruction to the preset demand management system; when the preset demand management system receives the stage update instruction, the project whose current demand execution stage is the preset stage in the first target project is determined as the second target project, and the use case execution result of the second target project is queried from the preset test case management system; if the use case execution result is execution failure, the bug status in the bug information corresponding to the second target project is determined through the preset defect management system; based on the bug status and the use case execution result, the actual demand execution stage of the second target project is determined, and it is judged whether the current demand stage of the second target project is consistent with the actual demand stage; if the current demand stage of the second target project is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage. In this way, the present application can update the demand development stage of the preset demand management system by using the use case execution status of the preset test management system outside the preset demand management system, realize the intercommunication of the preset demand management system, the preset test case management system and the defect management system, and ensure the consistency between the demand development stage in the preset demand management system and the actual development stage. After applying the present invention, the testing cost can be greatly reduced when managing requirements, use cases, and bugs on different platforms. There is no need to manually intervene to update the requirements one by one during the development phase, which reduces unnecessary working time and improves efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0043] Figure 1 A flow chart of a system interaction method provided for this application;

[0044] Figure 2 A schematic diagram of a strategy provided for this application;

[0045] Figure 3 A specific system interaction method flow chart provided for this application;

[0046] Figure 4 A schematic diagram of a process provided for this application;

[0047] Figure 5A schematic diagram of the structure of a system interaction device provided in this application;

[0048] Figure 6 A structural diagram of an electronic device provided for this application. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 are within the scope of protection of the present invention.

[0050] In the prior art, when requirements, use cases, and bugs need to be managed separately on multiple platforms (such as ZenTao, Metersphere, and Jira), when updating the stage to which the requirements belong in ZenTao, it is necessary to manually calculate the stage to which the requirements belong based on the execution of multiple use cases on the use case management system, and then find the corresponding requirements in ZenTao, and change the development stage of the requirements one by one. There may be uncertainties such as update errors, resulting in a huge waste of time and manpower. In this application, the requirements management system, use case management system, and defect management system can be automatically connected, and then the interaction of the three systems can be used to realize the automatic and accurate update of the project progress, and use cases can be automatically added for bugs that do not have test cases, thereby improving the testing efficiency.

[0051] The embodiment of the present invention discloses a system interaction method, see Figure 1 Said method comprises:

[0052] Step S11: monitor the execution status of all projects in the preset demand management system according to the preset monitoring method, determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system.

[0053] It can be understood that the preset demand management system in this embodiment stores the execution status of all projects, and this embodiment uses a preset monitoring method to monitor the execution status of all projects.

[0054] It should be noted that in some preferred implementations of the present invention, the preset demand management system can be ZenTao. In the specific implementation process, the execution status of all projects in ZenTao will be monitored. When the execution status of a project changes from in progress to closed, the project will be determined as the first target project, and then the step of sending the stage update instruction will be triggered.

[0055] It should be pointed out that, in this embodiment, if the project administrator wants to obtain the demand development stage status before the end of the project, the process of sending the stage update instruction to the preset demand management system can also be manually triggered.

[0056] In this embodiment, a button interface entrance can also be added to the front end of the preset requirement management system. After the user clicks it, all the requirements in the current project and the current requirement development stage of each requirement can be obtained. After clicking, a request for the latest use case execution status can also be initiated to the preset test case management system.

[0057] Step S12: When the preset requirement management system receives the stage update instruction, the project whose current requirement execution stage in the first target project is the preset stage is determined as the second target project, and the use case execution result of the second target project is queried from the preset test case management system.

[0058] It is understandable that, in this embodiment, the second target project is a project that needs to be updated in stage. In this embodiment, the project whose current demand execution stage is the preset stage in the first target project is determined as the second target project, which may include: determining the project whose current demand execution stage is in the testing (testing) or showcase state in the first target project as the second target project. And in this embodiment, the use case execution results are divided into pass, block, fail and not executed.

[0059] It can be understood that after receiving the stage update instruction, the preset demand management system in this embodiment will trigger the corresponding parameter update action, and its specific process is: determine the demand corresponding to the target project in the preset demand management system and the current demand execution stage of the current record. Then, the use case execution result obtained after the use case is pre-executed in the preset test case management system will be obtained. Specifically, in this embodiment, when determining the demand corresponding to the target project and the current demand execution stage, it can be queried from the database linked to the demand management system.

[0060] In some specific implementations, the use case execution result can be expressed in the form of a JSON string, and one requirement can correspond to multiple use cases. When one requirement can correspond to two use cases, the specific format of the use case execution result can be: {Requirement 1: Use case 1 execution result, Use case 2 execution result}.

[0061] Step S13: If the execution result of the use case is execution failure, the bug status in the bug information corresponding to the second target project is determined through a preset defect management system.

[0062] In this embodiment, one requirement may correspond to one or more use cases. When a requirement corresponds to one use case, if the use case execution result of this use case is execution failure, the bug status in the bug information corresponding to the second target project is determined through the preset defect management system; when a requirement corresponds to multiple use cases, if the use case execution result of any use case corresponding to this requirement is execution failure, the bug status in the bug information corresponding to the second target project is determined through the preset defect management system.

[0063] In this embodiment, the preset defect management system stores bug information corresponding to the second target project, and the bug information stores a bug status. In some specific implementations, the bug status includes a bug closed state and an unclosed state.

[0064] Step S14: Determine the actual requirement execution stage of the second target project based on the bug status and the use case execution result, and judge whether the current requirement stage of the second target project is consistent with the actual requirement stage.

[0065] Because a requirement may correspond to multiple use cases, it is necessary to jointly determine the stage of the requirement based on the execution status of all use cases under the requirement. Therefore, in this step, the actual requirement execution stage of the second target project will be determined based on the bug status and the use case execution results. Figure 2 The method in determines the actual demand execution stage of the project, that is, if the use case execution results of all use cases corresponding to the second target project are not executed, the actual demand execution stage of the second target project is determined as showcase; if the use case execution results of all use cases corresponding to the second target project are pass, the actual demand execution stage of the second target project is determined as tested; if the use case execution results of all use cases corresponding to the second target project are block, the actual demand execution stage of the second target project is determined as testing; if the use case execution results of all use cases corresponding to the second target project include fail, the bug status of the second target project is determined, if the bug status of the second target project is all closed, the actual demand execution stage is determined as tested, if the bug status of the second target project includes unclosed status, the actual demand execution stage is determined as testing.

[0066] In this embodiment, after determining the project in the first target project whose current requirement execution stage is a preset stage as the second target project, it may also include: generating a first character string based on the requirements corresponding to the second project and the current requirement execution stage; correspondingly, determining the actual requirement execution stage of the second target project based on the bug status and the use case execution result, and judging whether the current requirement stage of the second target project is consistent with the actual requirement stage, includes: generating a second character string based on the actual requirement execution stage of the second target project based on the bug status and the use case execution result, and judging whether the first character string is consistent with the second character string.

[0067] In this embodiment, both the first string and the second string can be expressed in the form of a json string. Specifically, the format of the first string can be: {Requirement 1: Current requirement development stage}, where the current requirement development stage is testing or showcase. The format of the second string can be: {Requirement 1: Actual requirement development stage}, where the actual requirement development stage is testing, showcase, or tested.

[0068] Step S15: If the current demand stage of the second target project is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage.

[0069] In this embodiment, when the current demand stage of the second target project is consistent with the actual demand stage, it means that the current demand stage recorded in the preset demand management system is in a correct state and no update is required at this time; when the current demand stage of the second target project is inconsistent with the actual demand stage, it means that the current demand stage recorded in the preset demand management system is in an error state, and the current demand stage will be updated to the actual demand stage to ensure that the information recorded in the task progress is consistent with the actual situation.

[0070] In a specific implementation, when the current demand stage of the second target project is inconsistent with the actual demand stage, the corresponding project is determined as the project to be updated, and then the project ID of the project to be updated is determined, and then the actual research and development stage corresponding to the project to be updated is obtained from the actual demand research and development stage based on the project ID of the project to be updated, and finally the current demand stage of the project to be updated is updated to the actual demand stage.

[0071] In the existing testing process, there are sometimes situations where there are no corresponding use cases for bugs. In this case, testers are generally required to record the corresponding bugs, write the corresponding test cases and upload them to the use case management system when the test is completed or reviewed. However, some bugs may be missed or forgotten.

[0072] In this embodiment, after determining the project whose execution status meets the preset first condition as the first target project, it can also include: obtaining the project bug list of the first target project through the interface provided by the preset defect management system, and determining the bugs without test cases in the project bug list as use case items to be supplemented; based on the bug information corresponding to the use case items to be supplemented in the project bug list, and using the use case template preset in the preset test case management system to create a use case for the use case item to be supplemented, and importing the created use case into the preset use case management system.

[0073] It should be noted that in this embodiment, the use case template preset in the preset test case management system can also be used to supplement the use cases for bugs without use cases according to the bug list in the defect management system, thereby realizing the intercommunication between the preset requirement management system and the preset test case management system. Bugs lacking use cases can be automatically identified without manual intervention, and appropriate use cases can be created quickly and accurately using preset templates, reducing unnecessary working time and improving testing efficiency.

[0074] In this embodiment, the system interaction method may further include: adding a first custom field require and a second custom field case in the defect management system, wherein the first custom field is used to associate bugs with requirements; and the second custom field case is used to associate bugs with use cases. In some preferred implementations, the defect management system may be jira, and this step may specifically be: adding a first custom field require and a second custom field case in jira. Then the process of adding use cases in this embodiment may specifically be: obtaining a bug list of the second target project in the preset defect management system, filtering out require! ~empty AND case~empty bugs, generating test cases based on the bug content, and then calling the preset test case management system to add a use case API (i.e., Application Programming Interface) to dynamically add use cases.

[0075] In this embodiment, the execution status of all projects in the preset demand management system is first monitored according to the preset monitoring method, and the project whose execution status meets the preset first condition is determined as the first target project, and then a stage update instruction is sent to the preset demand management system; when the preset demand management system receives the stage update instruction, the project whose current demand execution stage is the preset stage in the first target project is determined as the second target project, and the use case execution result of the second target project is queried from the preset test case management system; if the use case execution result is execution failure, the bug status in the bug information corresponding to the second target project is determined through the preset defect management system; based on the bug status and the use case execution result, the actual demand execution stage of the second target project is determined, and it is judged whether the current demand stage of the second target project is consistent with the actual demand stage; if the current demand stage of the second target project is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage. In this way, this embodiment can update the demand development stage of the preset demand management system by the use case execution status of the test management system outside the preset demand management system, and supplement the bugs without use cases with use cases according to the bug list in the defect management system, so as to realize the intercommunication between the demand management system and the test case management system, and ensure the consistency between the demand development stage in the demand management system and the actual development stage. After applying the present invention, the testing cost can be greatly reduced when managing requirements, use cases, and bugs on different platforms. There is no need to manually intervene to update the requirements one by one in the development stage, and to supplement the missing use cases, thereby reducing unnecessary working time and improving efficiency.

[0076] Figure 3 This is a flow chart of a specific system interaction method provided in the embodiment of the present application. Figure 3 As shown, the method includes:

[0077] Step S21: Create a management service for monitoring the execution status of projects in the control layer of the preset demand management system, and monitor the execution status of all projects in the preset demand management system according to a preset monitoring method through the management service, and determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system.

[0078] In the actual operation process, the actual completion time of development and testing may deviate from the planned time, so the planned completion time cannot be used as the only indicator. Therefore, in this embodiment, a management service for monitoring the project execution status can be created in the control layer of the preset demand management system. In some preferred implementations, when the preset demand management system is ZenTao, a resident monitor-compare service can be introduced in the Controller layer of ZenTao, which dynamically obtains the status of the project in the ongoing project and records the project status as project_status.

[0079] In this embodiment, the monitor-compare service will monitor the execution status of all projects in the preset demand management system according to the preset monitoring method. The monitoring of the execution status of all projects in the preset demand management system according to the preset monitoring method may include: determining the current time, and determining the planned completion time corresponding to each project in the preset demand management system; determining the project whose planned completion time is greater than the current time and satisfies the preset first time difference condition as the first project, and monitoring the execution status of the first project according to the first monitoring frequency; determining the project whose planned completion time is greater than the current time and satisfies the preset second time difference condition as the second project, and monitoring the execution status of the second project according to the second monitoring frequency; determining the project whose planned completion time is less than the current time as the third project, and monitoring the execution status of the third project according to the third monitoring frequency.

[0080] In some specific implementations, when a project is "in progress", the monitor-compare service first obtains the planned completion date t1 of the ongoing project and determines the current date t2. When t1-t2 is greater than the first preset value, project_status is obtained once a day (i.e., 24 hours); when t1-t2 is less than or equal to the first preset value and greater than or equal to the second preset value, project_status is obtained every 12 hours; when t1-t2 is less than or equal to the second preset value, project_status is obtained every 4 hours; if t1-t2 is less than zero (the project has passed the expected completion time but the project has not yet ended), project_status is obtained every 2 hours. It should be noted that the first preset value, the second preset value, and the parameter acquisition frequency can be arbitrarily set and changed according to the actual application scenario. In some preferred implementations, the first preset value can be set to 3, and the second preset value can be set to 1.

[0081] When the project_status obtained by the monitor-compare service is "closed", the monitor-compare process of the project will be stopped, and the corresponding project will be determined as the first target project, and then a stage update instruction will be sent to the control layer in the preset demand management system to trigger the action of updating the project demand.

[0082] Step S22: When the control layer in the preset demand management system receives the stage update instruction, the model layer in the preset demand management system is called to determine the demand and current demand execution stage corresponding to the first target project from the database connected to the preset demand management system, and the project in the first target project whose current demand execution stage is the preset stage is determined as the second target project.

[0083] In this embodiment, if the preset demand management system is ZenTao, when the Controller layer receives the stage update instruction, the Controller layer will call the Model layer to query the demand corresponding to the first target project in the database and the current demand development stage, and determine the project with the current demand development stage of the showcase and testing as the second target project, and then generate a first string in json string format. In a specific implementation, the monitor-compare service will write the project ID of the first target project into the stage update instruction after determining the first target project, and the Model layer can query the demand corresponding to the first target project in the database and the current demand development stage according to the project ID in the stage update instruction.

[0084] Step S23: calling the model layer to send a query request for querying the use case execution result of the second target project to a preset test case management system to obtain the use case execution result of the second target project.

[0085] In a specific implementation, the Model layer in ZenTao can send a test case execution result query request to a preset test case management system to obtain a test case result string generated in a json string format.

[0086] Step S24: If the execution result of the use case is execution failure, the bug status in the bug information corresponding to the target project is determined through a preset defect management system.

[0087] In some specific implementations, if the defect management system is jira, and there is a use case with a fail result, the corresponding bug information (carrying parameters: require~file requirements) can be obtained through the preset API in jira to obtain the corresponding bug status.

[0088] Step S25: Determine the actual demand execution stage of the target project based on the bug status and the use case execution result, and judge whether the current demand stage is consistent with the actual demand stage.

[0089] For a more specific processing procedure of step S25, reference may be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be described in detail here.

[0090] Step S26: If the current demand stage is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage.

[0091] For a more specific processing procedure of step S26, reference may be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be described in detail here.

[0092] In this embodiment, use cases can be added to bugs without use cases according to the bug list in the preset defect management system. In the specific implementation, the demand development stage of the corresponding demand in ZenTao can be dynamically updated through the use case execution status in the use case management system outside ZenTao, and when the bug has no corresponding test case, a test case is generated and imported into the use case management system. To a certain extent, the intercommunication between ZenTao, the defect management system and the use case management system is achieved, and the consistency between the demand development stage in ZenTao and the latest execution status is ensured. After applying the present invention, when managing requirements, use cases, and bugs on different platforms, the testing cost can be greatly reduced, unnecessary working time can be reduced, and efficiency can be improved.

[0093] like Figure 4The figure shows a specific process diagram provided by the present application, in which ZenTao is used as the preset demand management system, and Jira is used as the preset defect management system. When the project in ZenTao is in progress, the monitor-compare service preset in ZenTao is used to obtain the execution status of each project. When monitoring the project status, the monitoring interval can be dynamically adjusted according to the estimated completion time of the project. The closer the estimated completion time of the project is, the more frequent the frequency of obtaining the status. When it is monitored that the execution status of the project has changed to closed, the process of updating the demand stage will be triggered (wherein the process of triggering the update of the demand stage can also be triggered manually), and then the current demand development stage of each demand of the project will be determined, and the projects with the current demand development stage in the showcase and testing status will be used as the second target project, and the API of the use case management system will be called to determine the use case execution status list of the second target project. Among them, the json strings of the remaining projects will be removed from the first string list, that is, the first strings retained are all strings corresponding to the second target project. Then it will determine whether there is a use case in the use case execution list with a fail result. If so, it will call the Jira API to determine whether the bug status of the project is closed, and then write the bug status into the use case execution list. When the receiving module in ZenTao receives the use case execution data corresponding to the use case execution list, it will Figure 2 The strategy in determines the second string, and then determines whether the first string and the second string are consistent. If they are consistent, it indicates that the development stage of the requirement does not need to be updated. If they are inconsistent, the current development stage of the requirement should be updated to the actual development stage of the requirement. In addition, when it is detected that the project has been changed to closed, the supplementary use case process will be triggered. Specifically, the project bug list is obtained through the jira API, and the bugs that have requirements but no corresponding use cases are determined. Then, use cases are generated according to the bug content and imported into the preset test case management system.

[0094] See also Figure 5 As shown, the embodiment of the present application discloses a system interaction device, which may specifically include:

[0095] The status monitoring module 11 is used to monitor the execution status of all projects in the preset demand management system according to a preset monitoring method, and determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system;

[0096] The requirement query module 12 is used for determining the project whose current requirement execution stage is the preset stage in the first target project as the second target project when the preset requirement management system receives the stage update instruction, and querying the test case execution result of the second target project from the preset test case management system;

[0097] A bug status determination module 13, configured to determine the bug status in the bug information corresponding to the second target project through a preset defect management system if the execution result of the use case is an execution failure;

[0098] An actual demand determination module 14 is used to determine the actual demand execution stage of the second target project based on the bug status and the use case execution result, and to determine whether the current demand stage of the second target project is consistent with the actual demand stage;

[0099] The demand updating module 15 is configured to update the current demand stage in the preset demand management system to the actual demand stage if the current demand stage of the second target project is inconsistent with the actual demand stage.

[0100] The present application first monitors the execution status of all projects in the preset demand management system according to the preset monitoring method, and determines the project whose execution status meets the preset first condition as the first target project, and then sends a stage update instruction to the preset demand management system; when the preset demand management system receives the stage update instruction, the project whose current demand execution stage is the preset stage in the first target project is determined as the second target project, and the use case execution result of the second target project is queried from the preset test case management system; if the use case execution result is execution failure, the bug status in the bug information corresponding to the second target project is determined through the preset defect management system; based on the bug status and the use case execution result, the actual demand execution stage of the second target project is determined, and it is judged whether the current demand stage of the second target project is consistent with the actual demand stage; if the current demand stage of the second target project is inconsistent with the actual demand stage, the current demand stage in the preset demand management system is updated to the actual demand stage. In this way, the present application can update the demand development stage of the preset demand management system by using the use case execution status of the preset test management system outside the preset demand management system, realize the intercommunication of the preset demand management system, the preset test case management system and the defect management system, and ensure the consistency between the demand development stage in the preset demand management system and the actual development stage. After applying the present invention, the testing cost can be greatly reduced when managing requirements, use cases, and bugs on different platforms. There is no need to manually intervene to update the requirements one by one during the development phase, which reduces unnecessary working time and improves efficiency.

[0101] In some specific embodiments, the state monitoring module 11 specifically includes:

[0102] The service creation unit is used to create a management service for monitoring the execution status of projects in the control layer of the preset demand management system, and monitor the execution status of all projects in the preset demand management system according to a preset monitoring method through the management service.

[0103] In some specific embodiments, the state monitoring module 11 specifically includes:

[0104] A time determination unit is used to determine the current time and the planned completion time corresponding to each project in the preset demand management system;

[0105] A first execution status detection unit, configured to determine a project corresponding to a planned completion time greater than a current time and satisfying a preset first time difference condition as a first project, and monitor the execution status of the first project according to a first monitoring frequency;

[0106] A second execution status detection unit, configured to determine a project corresponding to a planned completion time greater than the current time and satisfying a preset second time difference condition as a second project, and monitor the execution status of the second project according to a second monitoring frequency;

[0107] The third execution status detection unit is used to determine the project whose planned completion time is less than the current time as the third project, and monitor the execution status of the third project according to a third monitoring frequency.

[0108] In some specific embodiments, the demand query module 12 includes:

[0109] A second target project determination unit is configured to, when the control layer in the preset demand management system receives the stage update instruction, call the model layer in the preset demand management system to determine the demand and current demand execution stage corresponding to the first target project from a database connected to the preset demand management system, and determine the project in the first target project whose current demand execution stage is the preset stage as the second target project;

[0110] The execution result query unit is used to call the model layer to send a query request for querying the test case execution result of the second target project to a preset test case management system to obtain the test case execution result of the second target project.

[0111] In some specific embodiments, the demand query module 12 includes:

[0112] The project determination unit is used to determine, among the first target projects, a project that is currently in a testing or test-submitted state at a current demand execution stage as a second target project.

[0113] In some specific embodiments, the system interaction device further includes:

[0114] A first character string generating unit, configured to generate a first character string based on the requirement corresponding to the second project and the current requirement execution stage;

[0115] Accordingly, the actual demand determination module 14 includes:

[0116] A second character string generating unit is used to determine the actual requirement execution phase of the second target project based on the bug status and the use case execution result to generate a second character string, and to determine whether the first character string is consistent with the second character string.

[0117] In some specific embodiments, the system interaction device further includes:

[0118] A unit for determining use cases to be supplemented is used to obtain a project bug list of the first target project through an interface provided by a preset defect management system, and determine bugs without test cases in the project bug list as use cases to be supplemented;

[0119] A use case creation unit is used to create a use case for the use case item to be supplemented based on the bug information corresponding to the use case item to be supplemented in the project bug list, and using a use case template preset in a preset test case management system.

[0120] Furthermore, the present application also discloses an electronic device. Figure 6 This is a structural diagram of an electronic device 20 according to an exemplary embodiment, and the content in the diagram cannot be considered as any limitation on the scope of use of the present application.

[0121] Figure 6 The present invention provides a schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a display screen 24, an input / output interface 25, a communication interface 26, and a communication bus 27. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the system interaction method disclosed in any of the above embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0122] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 26 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0123] In addition, the memory 22 as a carrier for resource storage may be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon may include an operating system 221, a computer program 222 and virtual machine data 223, etc. The virtual machine data 223 may include various data. The storage method may be temporary storage or permanent storage.

[0124] The operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, and may be Windows Server, Netware, Unix, Linux, etc. In addition to computer programs that can be used to complete the system interaction method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 may further include computer programs that can be used to complete other specific tasks.

[0125] Furthermore, the present application also discloses a computer-readable storage medium, wherein the computer-readable storage medium mentioned here includes a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a magnetic disk or an optical disk, or any other form of storage medium known in the technical field. Wherein, when the computer program is executed by the processor, the aforementioned disclosed system interaction method is implemented. For the specific steps of the method, reference can be made to the corresponding contents disclosed in the aforementioned embodiments, which will not be repeated here.

[0126] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts refer to the method part description. Professionals can also further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but this implementation should not be considered to exceed the scope of this application.

[0127] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0128] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0129] The system interaction method, device, equipment, and storage medium provided by the present invention are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A system interaction method, characterized in that: include: Monitor the execution status of all projects in the preset demand management system according to the preset monitoring method, determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system; When the preset requirement management system receives the stage update instruction, the project whose current requirement execution stage is the preset stage in the first target project is determined as the second target project, and the test case execution result of the second target project is queried from the preset test case management system; If the execution result of the use case is execution failure, determining the bug status in the bug information corresponding to the second target project through a preset defect management system; Determine the actual demand execution stage of the second target project based on the bug status and the use case execution result, and judge whether the current demand stage of the second target project is consistent with the actual demand execution stage; If the current demand stage of the second target project is inconsistent with the actual demand execution stage, updating the current demand stage in the preset demand management system to the actual demand execution stage; The step of determining the project whose execution status satisfies a preset first condition as the first target project includes: Changing the execution status of a project from in progress to closed is determined as the first target project; The step of determining the project in the first target project whose current demand execution stage is a preset stage as the second target project includes: Determine the project in the first target project whose current requirement execution stage is in the testing or submitted for testing state as the second target project; The step of determining the actual demand execution phase of the second target project based on the bug status and the use case execution result includes: If the use case execution results of all use cases corresponding to the second target project fail, the bug status of the second target project is determined; if the bug status of the second target project is all closed, the actual demand execution stage is determined to be tested; if the bug status of the second target project is not closed, the actual demand execution stage is determined to be in testing.

2. The system interaction method according to claim 1, characterized in that: The monitoring of the execution status of all projects in the preset demand management system according to the preset monitoring method includes: A management service for monitoring the execution status of projects is created in the control layer in the preset demand management system, and the execution status of all projects in the preset demand management system is monitored through the management service according to a preset monitoring method.

3. The system interaction method according to claim 2, characterized in that: The monitoring of the execution status of all projects in the preset demand management system according to the preset monitoring method includes: Determine the current time and the planned completion time corresponding to each project in the preset demand management system; Determine the project corresponding to the planned completion time being greater than the current time and satisfying the preset first time difference condition as the first project, and monitor the execution status of the first project according to the first monitoring frequency; Determine the project whose planned completion time is greater than the current time and satisfies the preset second time difference condition as the second project, and monitor the execution status of the second project according to the second monitoring frequency; The project whose planned completion time is less than the current time is determined as a third project, and the execution status of the third project is monitored according to a third monitoring frequency.

4. The system interaction method according to claim 1, characterized in that: When the preset requirement management system receives the stage update instruction, the project whose current requirement execution stage is the preset stage in the first target project is determined as the second target project, and the test case execution result of the second target project is queried from the preset test case management system, including: When the control layer in the preset demand management system receives the stage update instruction, the model layer in the preset demand management system is called to determine the demand and the current demand execution stage corresponding to the first target project from the database connected to the preset demand management system, and the project in the first target project whose current demand execution stage is the preset stage is determined as the second target project; The model layer is called to send a query request for querying the use case execution result of the second target project to a preset test case management system to obtain the use case execution result of the second target project.

5. The system interaction method according to claim 1, characterized in that: After determining the project whose current demand execution stage is the preset stage in the first target project as the second target project, the method further includes: Generate a first character string based on the requirements corresponding to the second target project and the current requirement execution stage; Accordingly, determining the actual requirement execution stage of the second target project based on the bug status and the use case execution result, and judging whether the current requirement stage of the second target project is consistent with the actual requirement execution stage, includes: Based on the bug status and the use case execution result, the actual requirement execution phase of the second target project is determined to generate a second string, and it is determined whether the first string is consistent with the second string.

6. The system interaction method according to any one of claims 1 to 5, characterized in that: After determining the project whose execution status meets the preset first condition as the first target project, the method further includes: Obtaining a project bug list of the first target project through an interface provided by a preset defect management system, and determining bugs without test cases in the project bug list as test cases to be supplemented; Based on the bug information corresponding to the use case item to be supplemented in the project bug list, and using the use case template preset in the preset test case management system, a use case is created for the use case item to be supplemented.

7. A system interaction device, characterized in that: include: A status monitoring module, used to monitor the execution status of all projects in the preset demand management system according to a preset monitoring method, and determine the project whose execution status meets the preset first condition as the first target project, and then send a stage update instruction to the preset demand management system; A requirement query module, configured to determine, when the preset requirement management system receives the stage update instruction, a project in the first target project whose current requirement execution stage is the preset stage as a second target project, and query the test case execution result of the second target project from the preset test case management system; A bug status determination module, configured to determine the bug status in the bug information corresponding to the second target project through a preset defect management system if the execution result of the use case is an execution failure; An actual demand determination module, used to determine the actual demand execution stage of the second target project based on the bug status and the use case execution result, and to determine whether the current demand stage of the second target project is consistent with the actual demand execution stage; A demand updating module, configured to update the current demand stage in the preset demand management system to the actual demand execution stage if the current demand stage of the second target project is inconsistent with the actual demand execution stage; Wherein, the status monitoring module is used to change the execution status of the project from in progress to a closed project, and determine it as the first target project; The demand query module is used to determine the project in the first target project whose current demand execution stage is in the testing or submitted for testing state as the second target project; Among them, the actual demand determination module is used to determine the bug status of the second target project if the use case execution results of all use cases corresponding to the second target project fail; if the bug status of the second target project is all closed, the actual demand execution stage is determined to be tested; if the bug status of the second target project is not closed, the actual demand execution stage is determined to be in testing.

8. An electronic device, characterized in that: It comprises a processor and a memory; wherein, when the processor executes the computer program stored in the memory, the system interaction method as described in any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the system interaction method according to any one of claims 1 to 6 is implemented.

Images