Test submission management method and device, equipment and storage medium

Abstract

The invention discloses a test submission management method and device, equipment and a storage medium, and relates to the technical field of network information, and discloses a test submission management method, which comprises the following steps: after determining to deploy a test submission service, marking a request interface corresponding to a to-be-tested case of the test submission service; executing the corresponding request interfaces in sequence based on an association request sequence in the to-be-tested case, completing testing of the branch codes corresponding to the test submission service in the test environment, and obtaining a test result; if it is determined that the test result is passed, the combined code is tested in the pre-issuing environment, test submitting information for testing the branch code is recorded, and the combined code is obtained after the branch code is combined to the pre-issuing branch. In other words, the requests with association are set in the to-be-tested case, independence among the cases is achieved, the testing efficiency is improved, the combined codes are tested in the pre-sending environment, errors existing when branch codes are officially issued are avoided, and then the testing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of network information technology, and in particular to a test management method, device, equipment and storage medium. Background Art

[0002] With the rapid development of software updates and iterations, the software development efficiency of each company now needs to be improved rapidly, so it is necessary to improve the testing efficiency of the developed software. Testing refers to submitting the code to the test environment for testing.

[0003] At present, the commonly used test process management method is to determine the use case according to the request of the test service corresponding to the software code when testing the software code in the test environment, so as to complete the test of the software code in the test environment by executing the request interface corresponding to each use case. After the software code passes the test of the test environment, the software code is tested in the pre-release environment. However, by executing the request interface corresponding to the use case to implement the test of the software code in the test environment, the error of one use case may lead to the error of other use cases, thereby reducing the efficiency of the test.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a test management method, which aims to solve the technical problem that staff are required to collect relevant information more frequently, thereby reducing the efficiency of testing.

[0006] To achieve the above objectives, the present application proposes a test management method, the method comprising:

[0007] After the deployment of the test service is determined, the request interface corresponding to the test case to be tested of the test service is marked;

[0008] Execute the corresponding request interfaces in sequence based on the associated request sequence in the test case, complete the test of the branch code corresponding to the test service in the test environment, and obtain the test result;

[0009] If it is determined that the test result is passed, the merged code is tested in a pre-release environment, and test information for testing the branch code is recorded. The merged code is obtained after merging the branch code into the pre-release branch.

[0010] In one embodiment, after the deployment of the testing service is determined, the step of marking the request interface corresponding to the test case to be tested of the testing service includes:

[0011] After determining to deploy the test service, determining the service level of the test service;

[0012] If the service level is the business domain level, detecting whether there is an undeployed service to be deployed in the test service;

[0013] If it is determined that the service to be deployed exists, re-detection is performed after a preset time period until it is determined that there is no service to be deployed in the service to be tested, and the service to be tested is determined to have been deployed;

[0014] Retrieve the corresponding request interface set deployed for the test case to be tested of the test service;

[0015] The request interfaces in the request interface set corresponding to the test cases of the testing service are marked in sequence.

[0016] In one embodiment, before the step of calling the corresponding request interface set deployed for the test case to be tested of the test service, the step further includes:

[0017] Identify the test cases corresponding to each application scenario from the test request service;

[0018] Identify the associated requests in each of the test cases;

[0019] The step of retrieving the corresponding request interface set deployed for the test case to be tested of the test service comprises:

[0020] The request interface deployed for each associated request in the test case is retrieved to obtain the request interface set of the test case.

[0021] In one embodiment, if it is determined that the test result is passed, the step of testing the merged code in a pre-release environment includes:

[0022] If it is determined that the test result is passed, the pre-release branch of the test service is called;

[0023] Merge the branch code into the pre-release branch to obtain a merged code;

[0024] Obtaining the test service corresponding to the merged code;

[0025] Deploy a pre-release test environment based on the test service to obtain a pre-release environment;

[0026] The merged code is subjected to a pre-release test in the pre-release environment.

[0027] In one embodiment, after the step of performing a pre-release test on the merged code in the pre-release environment, the step further includes:

[0028] If the pre-release test passes, the official code branch of the software corresponding to the test service is obtained;

[0029] Merge the official code branch into the merged code to obtain the code to be released;

[0030] Determine whether there is an error in the code to be released;

[0031] If it is determined that there is no error in the code to be released, the code to be released is merged into the code framework of the official code branch to obtain the official release code of the software corresponding to the testing service.

[0032] In one embodiment, if it is determined that the test result is passed, the merged code is tested in a pre-release environment, and the test information of the branch code is recorded, and the following is also included:

[0033] Generate a test report based on the test information, and display the test report to the test user;

[0034] If the modified data based on the test report is received from the test submitting user, all relevant data in the test report are updated based on the modified data to obtain a final test report.

[0035] In addition, to achieve the above purpose, the present application also proposes a test management device, the test management device comprising:

[0036] A trigger module is used to mark the request interface corresponding to the test case to be tested of the test service after determining the deployment of the test service;

[0037] The test environment test module is used to execute the corresponding request interfaces in sequence based on the associated request sequence in the test case, complete the test of the branch code corresponding to the test service in the test environment, and obtain the test result;

[0038] The pre-release environment testing module is used to test the merged code in the pre-release environment if it is determined that the test result is passed, and record the test information of the branch code. The merged code is obtained after merging the branch code into the pre-release branch.

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

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

[0041] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the test management method described above.

[0042] One or more technical solutions proposed in this application have at least the following technical effects:

[0043] Set the associated requests in a use case. After the deployment of the test service is determined, determine the test case for the test service, and mark the request interface corresponding to the test case. According to the order of the associated requests in the test case, execute the corresponding request interface in sequence to implement the testing of the branch code corresponding to the test service in the test environment. Since the associated requests are set in a test case, the independence of each use case is achieved. When an error occurs in a test case during the test, only the test case needs to be modified, and errors will not occur in other test cases, thereby speeding up the testing efficiency in the test environment. After passing the test in the test environment, the merged code obtained by merging the branch code into the pre-release branch is tested in the pre-release environment to avoid errors in the branch code when it is officially released, thereby improving the efficiency of the test. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0046] Figure 1 A flowchart of the first embodiment of the present application test management method is provided;

[0047] Figure 2 A flowchart of the second embodiment of the application test management method is provided;

[0048] Figure 3 A flowchart of the third embodiment of the present application test management method is provided;

[0049] Figure 4 This is a schematic diagram of the module structure of the test management device according to an embodiment of the present application;

[0050] Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the test management method in the embodiment of the present application.

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

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

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

[0054] The main solution of the embodiment of the present application is: after determining to deploy the testing service, the testing platform marks the request interface corresponding to the test case to be tested of the testing service; based on the associated request order in the test case, the corresponding request interface is executed in sequence to complete the test of the branch code corresponding to the testing service in the test environment and obtain the test result; if it is determined that the test result is passed, the merged code is tested in the pre-release environment, and the testing information of the branch code is recorded, and the merged code is obtained after the branch code is merged into the pre-release branch.

[0055] In this embodiment, for ease of description, the following description is made with the testing platform as the execution entity.

[0056] Because the prior art usually determines the use case according to the request of the testing service corresponding to the software code when testing the software code in the test environment, so as to complete the testing of the software code in the test environment by executing the request interface corresponding to each use case. After the software code passes the test of the test environment, the software code is tested in the pre-release environment. However, by executing the request interface corresponding to the use case to implement the testing of the software code in the test environment, the error of one use case may lead to the error of other use cases, thereby reducing the efficiency of testing.

[0057] The present application provides a solution, which sets the associated requests in a use case. After the deployment of the test service is determined, the test case of the test service is determined, and the request interface corresponding to the test case is marked. According to the order of the associated requests in the test case, the corresponding request interface is executed in sequence to implement the testing of the branch code corresponding to the test service in the test environment. Since the associated requests are set in a test case, the independence of each use case is achieved. When an error occurs in a test case during the test, only the test case needs to be modified, and errors will not occur in other test cases, thereby speeding up the testing efficiency in the test environment. After passing the test in the test environment, the merged code obtained by merging the branch code into the pre-release branch is tested in the pre-release environment to avoid errors in the branch code when it is officially released, thereby improving the testing efficiency.

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

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

[0060] In this embodiment, the test management method includes steps S10 to S30:

[0061] Step S10: after determining to deploy the test service, mark the request interface corresponding to the test case to be tested of the test service;

[0062] It should be noted that the test submission service can be the submission of the developed functions or codes to the test team for verification and testing during the software development process. Use cases can be used to describe the functional requirements and expected behaviors of an application, usually including a scenario, participants, preconditions, postconditions, and a series of steps to verify whether the system meets these requirements and behaviors. For example, when a user logs in to an application, the participant is the user; the precondition is the valid username and password that the user has registered and has; the postcondition is that the user successfully logs in to the system and can access his personal account information; the basic process can be 1. The user opens the login page, 2. The user enters a valid username and password, 3. The user clicks the "Login" button, 4. The application verifies whether the username and password are correct, 5. If the verification is successful, the application displays the user's personal account information, 6. If the verification fails, the application displays an error message to prompt the user to re-enter. The test case to be tested can be the use case that needs to be tested. The request interface can be the interface required to complete each request in the use case process.

[0063] It can be understood that after determining to deploy the test service, by marking the request interface corresponding to the test case, it is possible to quickly determine that the request interface needs to be used when testing the developed software code, so as to avoid the need to search one by one from all interfaces during testing, thereby improving testing efficiency.

[0064] In the specific implementation, the person in charge of the test environment creates a new testing process on the testing platform, fills in the project name, selects the services to be deployed and the corresponding developers, and submits it. The testing platform publishes a message to notify the developer to confirm the services, branches and release order to be deployed. After receiving the developer's confirmation of the service, the testing platform notifies the tester to deploy it according to the testing service. After determining to deploy the testing service, the testing platform marks the corresponding request interface through the test case to be tested of the testing service, so as to facilitate the subsequent testing of the corresponding branch code of the testing service in the test environment through the request interface.

[0065] Step S20, executing the corresponding request interfaces in sequence based on the associated request sequence in the test case, completing the test of the branch code corresponding to the test service in the test environment, and obtaining the test result;

[0066] It should be noted that the associated request may be a request with association, for example, the request to open the login page is related to the request to enter a valid username and password, that is, the request to enter a valid username and password cannot be executed without completing the request to open the login page. The order of associated requests may be the execution order of each mutually related request. Branch codes may be codes that different development users are responsible for, and the codes are all codes that need to test the software. The test environment may be a platform for completing software testing work. The test result may be pass or fail.

[0067] It can be understood that by automatically executing the associated request sequence in the test case, the test of the corresponding branch code of the test service can be completed quickly, saving the time and cost of manual testing.

[0068] It is understandable that since the test cases contain related requests within the entire scenario, the test cases are independent of each other and each test case can be run independently, which is convenient for debugging and maintenance. When a test case fails due to a problem during the test process, there is no need to analyze the remaining test cases. Only the failed test cases need to be sent to the developer side, and the developer can analyze the failed test cases separately, which improves the efficiency of testing.

[0069] In the specific implementation, the order of associated requests in the test case is analyzed to determine the execution order of each request interface; then, according to the determined execution order, the corresponding request interfaces are called in sequence to simulate user operations or trigger corresponding functions; in the test environment, the corresponding request interfaces are executed in sequence according to the execution time of each associated request to ensure the normal operation of the functions of the corresponding branch code of the test service; the execution results of each request interface are recorded, including success or failure, returned data, etc.; finally, the execution results of all request interfaces are combined to obtain the overall test results to determine whether the expected requirements and quality standards are met.

[0070] In the specific implementation, if the test result is failed, a message is automatically sent to the corresponding developer and an error log is given to facilitate the developer to locate the problem. Then the code modified by the developer is received and the tester is notified to deploy the service again.

[0071] Step S30: If it is determined that the test result is passed, the merged code is tested in a pre-release environment, and the test information of the branch code is recorded. The merged code is obtained after merging the branch code into the pre-release branch.

[0072] It should be noted that the merged code can be obtained by merging the branch code responsible for each developer into the preset release branch of the corresponding testing server. The pre-release environment can provide a platform that is as similar as possible to the production environment, which is used to perform final testing and verification of the software before the official release, so as to find problems that only appear in the production environment or are exposed under high load. Testing in the pre-release environment can include regression testing, integration testing, performance testing, etc. to ensure the stability and reliability of the software in real scenarios. Testing information can be information recorded during the entire process of branch code testing, which can include all information such as the specific time of each node, completion time, project cycle time, time of each stage, and every action performed by each participant.

[0073] It is understandable that merging branch code into a pre-release branch usually involves performing a merge operation and resolving possible conflicts between branch codes, and deploying the pre-release branch to a pre-release environment. Further testing in the pre-release environment can ensure the stability and reliability of the code during formal operation, and provide an effective testing process to manage the merging and testing of branch codes.

[0074] It is understandable that by recording the testing information of the branch code, after the branch code completes the test of a certain node, the staff who need to participate in the next node can understand the testing status and the next actions through the testing information, making the testing process design more reasonable and simpler, which can greatly improve the efficiency of the testing process and test communication, and liberate development, testing, and project management from the constraints of the project process. There is no need to send emails or message notifications every time, and one-click notification and automatic execution of automated regression are realized.

[0075] Optionally, after step S30, the test management method further includes:

[0076] Generate a test report based on the test information, and display the test report to the test user;

[0077] If the modified data based on the test report is received from the test submitting user, all relevant data in the test report are updated based on the modified data to obtain a final test report.

[0078] It should be noted that the user who submits the test can be the user who tests the branch code or software version submitted by the developer. The modified data may include errors that occur during the test process, conflicts between branch codes after the branch code is merged with the pre-release branch, or the merged code cannot achieve the expected function.

[0079] It can be understood that displaying the test report generated based on the test information to the test user can not only enable the test user to timely understand the test status of the test software, but also allow the test user to further send the test report to the operation and maintenance personnel for the data in the test report that does not reach the expected accuracy, and the operation and maintenance personnel will modify the software code according to the test report to improve the stability of the software during operation.

[0080] It is understandable that by manually modifying the test report for the test user, the accuracy of the test can be improved, thereby improving the efficiency of the test.

[0081] The present embodiment provides a test management method, which sets associated requests in a use case. After determining to deploy the test service, the test case to be tested of the test service is determined, and the request interface corresponding to the test case is marked. According to the order of each associated request in the test case, the corresponding request interface is executed in sequence to implement the test of the branch code corresponding to the test service in the test environment. Since the associated requests are set in a test case, the independence of each use case is achieved. When an error occurs in a test case during the test, only the test case needs to be modified, and errors will not occur in other test cases, thereby speeding up the testing efficiency in the test environment. After passing the test in the test environment, the merged code obtained by merging the branch code into the pre-release branch is tested in the pre-release environment to avoid errors in the branch code when it is officially released, thereby improving the test efficiency.

[0082] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , step S10 includes steps S11 to S15:

[0083] Step S11, after determining to deploy the test service, determining the service level of the test service;

[0084] Step S12: if the service level is the business domain level, detecting whether there is any undeployed service in the test service;

[0085] Step S13, if it is determined that the service to be deployed exists, then re-detect after a preset time period until it is determined that there is no service to be deployed in the service to be tested, and the service to be tested is determined to have been deployed;

[0086] Step S14, calling the corresponding request interface set deployed for the test case to be tested of the test service;

[0087] Step S15, sequentially marking the request interfaces in the request interface set corresponding to the test cases to be tested of the test service.

[0088] It should be noted that the service level can be the business domain level of all systems and the system level of a single functional system. The services to be deployed can be testing services that have not been fully deployed and testing services that have not yet been deployed. The preset duration can be the duration set by the user based on the computing power of the test platform, the difficulty assessment of the test code, and experience. The completed deployment of the testing service can be the deployment of the testing services corresponding to all systems in the business domain.

[0089] It is understandable that since the test cases can include the testing services of the systems corresponding to all application scenarios in the entire business domain, and can also include the testing services of some systems, in order to avoid the situation where the testing services fail to complete deployment and then start testing the branch code, the test will be interrupted when testing the code corresponding to the testing services that have not completed deployment. When testing again, it is necessary to start the test again, thereby improving the efficiency of testing.

[0090] It is understandable that in order to ensure that all test services within the business domain are deployed, a preset period of time is waited after detecting that there are services to be deployed. After all test services are deployed, the request excuse is marked to avoid test interruption and repeated testing, thereby improving the efficiency of testing.

[0091] It can be understood that by marking the request interface associated with each request in the test case, it is ensured that when executing the test, each request in the test case can be correctly matched with its corresponding interface, thereby performing effective testing.

[0092] In the specific implementation, after the test service is deployed, the automated test case is automatically triggered to determine the service level of the test service. The service level is divided into business domain and system (determine which level the configured microservice belongs to. If the configuration of microservice A is business domain, all automation of the domain will be triggered when A is deployed successfully; if microservice B is configured at the system level, the successful deployment of microservice B will trigger the automated execution of the system where service B is located); if the corresponding service in the corresponding business domain is successfully deployed, the automated execution of the request interface of the domain will be triggered. However, before executing the automation, it is necessary to check whether there are any microservices in the deployment process in the domain. If so, it will be checked again after 10 minutes. The automated execution will not be triggered until it is checked that there are no services in the deployment process.

[0093] Furthermore, before step S41, the test management method further includes:

[0094] Identify the test cases corresponding to each application scenario from the test request service;

[0095] Identify the associated requests in each of the test cases;

[0096] The step of retrieving the corresponding request interface set deployed for the test case to be tested of the test service comprises:

[0097] The request interface deployed for each associated request in the test case is retrieved to obtain the request interface set of the test case.

[0098] It should be noted that the associated request can be a request with association in the test case. The request interface can be an execution interface pre-configured by the developer with each associated request in each test case, that is, each test case includes at least one associated request, and the execution of each request needs to be implemented by an interface. Therefore, a request interface needs to be configured for each associated request in the test case.

[0099] It is understandable that the test cases are set according to the application scenarios to ensure that each test case is independent of each other and has no correlation, so that each test case can be run independently. And by calling the request interface corresponding to each associated request, it can also ensure that when the corresponding associated request is executed through the request interface, the correct request interface can be called quickly, reducing test errors and speeding up the test, thereby improving the efficiency of the test.

[0100] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 3 , step S30 includes steps S31 to S35:

[0101] Step S31: if it is determined that the test result is passed, the pre-release branch of the test service is called;

[0102] Step S32, merging the branch code into the pre-release branch to obtain a merged code;

[0103] Step S33, obtaining the test service corresponding to the merged code;

[0104] Step S34, deploying a pre-release test environment based on the test service to obtain a pre-release environment;

[0105] Step S35: performing a pre-release test on the merged code in the pre-release environment.

[0106] It can be understood that the branch code of the developer who needs to be released is automatically triggered, and the branch code of each developer is automatically merged into the pre-release branch of the corresponding microservice. Among them, the logic of merging the pre-release branch is to automatically obtain the pre-release branch and merge it into the branch of the service, and then merge the branch of the service into the pre-release branch to avoid common code conflicts. If there is still a conflict in the end, development intervention is required to resolve the conflict.

[0107] In the specific implementation, the test report or test log generated during the test execution process is analyzed and evaluated. If the test results show that all the test cases have been successfully executed, no errors or conflicts are found, and the predetermined test standards and quality requirements are met, then the test result can be considered to have passed. The pre-release branch is retrieved from the microservice corresponding to the test service, and the branch code is merged into the pre-release branch. That is, new functions or fixed defects are introduced into the pre-release environment. After the branch codes are merged into the pre-release branch, there will be certain adjustments between the branch codes. Therefore, it is necessary to deploy the pre-release environment required for the pre-release test with the test service corresponding to the merged code. The pre-release environment needs to simulate the production environment as much as possible so that the test can be performed under conditions close to the actual production environment.

[0108] Furthermore, after step S35, the test management method further includes:

[0109] If the pre-release test passes, the official code branch of the software corresponding to the test service is obtained;

[0110] Merge the official code branch into the merged code to obtain the code to be released;

[0111] Determine whether there is an error in the code to be released;

[0112] If it is determined that there is no error in the code to be released, the code to be released is merged into the code framework of the official code branch to obtain the official release code of the software corresponding to the testing service.

[0113] It should be noted that the code to be released can be the code that is merged after the pre-test and the formal code branch required for the formal release of the software. The formal code branch can be the code branch in the production node, that is, the code branch in the node before the software code is officially released. The code framework can be the infrastructure and predefined code templates used to build applications in software development, providing a standardized way to organize and manage code, so that developers can merge the branch code submitted for testing with the code template according to the infrastructure to form a code that can realize software functions.

[0114] It is understandable that by merging the official code into the merged code before merging the code, error checking can be performed before the code is released to quickly identify and fix problems and avoid introducing errors into the official release version. By merging the code to be released into the code framework of the official code branch, the smoothness and continuity of the version transition can be ensured, avoiding business interruptions caused by version upgrades.

[0115] It is understandable that since the testing process is highly automated, and the automated and standardized release process can improve release efficiency, reduce human errors and workload, and thus improve testing efficiency.

[0116] In the specific implementation, after the pre-release test is completed, the process will go to the production deployment node, which also needs to merge branches. Here, you need to merge the production official code branch into the pre-release branch first, and then merge the pre-release branch into the official code branch. After the merger is successful, the system will prompt. If it fails, the developer needs to intervene to solve it. If the merger is successful, you can directly publish the official code to the production environment at this node. When publishing, you need to confirm that the environment is the production environment, and the selected branch is the official code by default.

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

[0118] This application also provides a test management device, please refer to Figure 4 , the test management device comprises:

[0119] The trigger module 10 is used to mark the request interface corresponding to the test case to be tested of the test service after determining the deployment of the test service;

[0120] The test environment test module 20 is used to execute the corresponding request interface in sequence based on the associated request sequence in the test case, complete the test of the branch code corresponding to the test service in the test environment, and obtain the test result;

[0121] The pre-release environment testing module 30 is used to test the merged code in the pre-release environment if it is determined that the test result is passed, and record the test information of the branch code. The merged code is obtained after merging the branch code into the pre-release branch.

[0122] Optionally, the trigger module 10 is also used to determine the service level of the test service after determining the deployment of the test service; if the service level is the business domain level, then detect whether there are any unfinished deployed services in the test service; if it is determined that there are services to be deployed, then detect again after a preset time period until it is determined that there are no services to be deployed in the test service, and determine that the deployment of the test service is complete; retrieve the corresponding request interface set deployed for the test case of the test service; and mark the request interfaces in the request interface set corresponding to the test case of the test service in sequence.

[0123] Optionally, the trigger module 10 is also used to identify the test cases corresponding to each application scenario from the test service; identify the associated requests in each of the test cases; the step of calling the corresponding request interface set deployed for the test cases of the test service includes: calling the request interface deployed for each associated request in the test case to obtain the request interface set of the test case.

[0124] Optionally, the pre-release environment testing module 30 is also used to call the pre-release branch of the testing service if it is determined that the test result is passed; merge the branch code into the pre-release branch to obtain the merged code; obtain the test service corresponding to the merged code; deploy the pre-release test environment based on the test service to obtain the pre-release environment; and perform a pre-release test on the merged code in the pre-release environment.

[0125] Optionally, the pre-release environment testing module 30 is also used to obtain the official code branch of the software corresponding to the testing service if the pre-release test passes; merge the official code branch into the merged code to obtain the code to be released; determine whether there is an error in the code to be released; if it is determined that there is no error in the code to be released, merge the code to be released into the code framework of the official code branch to obtain the official release code of the software corresponding to the testing service.

[0126] Optionally, the pre-release environment test module 30 is also used to generate a test report based on the test information and display the test report to the test user; if the test user receives modification data based on the test report, all relevant data in the test report is updated based on the modification data to obtain the final test report.

[0127] The test management device provided by the present application adopts the test management method in the above embodiment, which can solve the technical problem that the staff needs to collect relevant information more frequently, reducing the efficiency of the test. Compared with the prior art, the beneficial effects of the test management device provided by the present application are the same as the beneficial effects of the test management method provided by the above embodiment, and the other technical features in the test management device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

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

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

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

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

[0132] The test management device provided by the present application adopts the test management method in the above embodiment, which can solve the technical problem that the staff needs to collect relevant information more frequently, reducing the efficiency of the test. Compared with the prior art, the beneficial effects of the test management device provided by the present application are the same as the beneficial effects of the test management method provided by the above embodiment, and the other technical features in the test management device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

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

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

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

[0136] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0137] The computer-readable storage medium may be included in the test management device; or may exist independently without being installed in the test management device.

[0138] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the test management device, the test management device: after determining to deploy the test service, marks the request interface corresponding to the test case of the test service; executes the corresponding request interface in sequence based on the associated request sequence in the test case, completes the test of the branch code corresponding to the test service in the test environment, and obtains the test result; if it is determined that the test result is passed, tests the merged code in the pre-release environment, and records the test information of the branch code, wherein the merged code is obtained after merging the branch code into the pre-release branch.

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

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

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

[0142] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned test management method, and can solve the technical problem that the staff needs to collect relevant information more frequently, which reduces the efficiency of the test. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the test management method provided in the above-mentioned embodiment, and will not be repeated here.

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

[0144] The computer program product provided by the present application can solve the technical problem that the staff needs to collect relevant information more frequently, which reduces the efficiency of testing. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the testing management method provided by the above embodiment, which will not be repeated here.

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

Claims

1. A test management method, characterized in that: The method includes: After the deployment of the testing service is determined, the request interface corresponding to the test case to be tested of the testing service is marked; Execute the corresponding request interfaces in sequence based on the associated request sequence in the test case, complete the test of the branch code corresponding to the test service in the test environment, and obtain the test result; If it is determined that the test result is passed, the merged code is tested in a pre-release environment, and test information for testing the branch code is recorded. The merged code is obtained after merging the branch code into the pre-release branch.

2. The method according to claim 1, characterized in that After the deployment of the testing service is determined, the step of marking the request interface corresponding to the test case to be tested of the testing service includes: After determining to deploy the test service, determining the service level of the test service; If the service level is the business domain level, detecting whether there is an undeployed service to be deployed in the test service; If it is determined that the service to be deployed exists, re-detection is performed after a preset time period until it is determined that there is no service to be deployed in the service to be tested, and the service to be tested is determined to have been deployed; Retrieve the corresponding request interface set deployed for the test case to be tested of the test service; The request interfaces in the request interface set corresponding to the test cases of the testing service are marked in sequence.

3. The method according to claim 2, characterized in that Before the step of calling the corresponding request interface set deployed for the test case to be tested of the test service, the following steps are also included: Identify the test cases corresponding to each application scenario from the test request service; Identify the associated requests in each of the test cases; The step of retrieving the corresponding request interface set deployed for the test case to be tested of the test service comprises: The request interface deployed for each associated request in the test case is retrieved to obtain the request interface set of the test case.

4. The method according to claim 1, characterized in that If it is determined that the test result is passed, the step of testing the merged code in the pre-release environment includes: If it is determined that the test result is passed, the pre-release branch of the test service is called; Merge the branch code into the pre-release branch to obtain a merged code; Obtaining the test service corresponding to the merged code; Deploy a pre-release test environment based on the test service to obtain a pre-release environment; The merged code is subjected to a pre-release test in the pre-release environment.

5. The method according to claim 4, characterized in that After the step of performing a pre-release test on the merged code in the pre-release environment, the following step is further included: If the pre-release test passes, the official code branch of the software corresponding to the test service is obtained; Merge the official code branch into the merged code to obtain the code to be released; Determine whether there is an error in the code to be released; If it is determined that there is no error in the code to be released, the code to be released is merged into the code framework of the official code branch to obtain the official release code of the software corresponding to the testing service.

6. The method according to claim 1, characterized in that If it is determined that the test result is passed, the merged code is tested in a pre-release environment, and the test information of the branch code is recorded, and the following steps are further included: Generate a test report based on the test information, and display the test report to the test user; If the modified data based on the test report is received from the test submitting user, all relevant data in the test report are updated based on the modified data to obtain a final test report.

7. A test management device, characterized in that: The device comprises: A trigger module is used to mark the request interface corresponding to the test case to be tested of the test service after determining the deployment of the test service; The test environment test module is used to execute the corresponding request interfaces in sequence based on the associated request sequence in the test case, complete the test of the branch code corresponding to the test service in the test environment, and obtain the test result; The pre-release environment testing module is used to test the merged code in the pre-release environment if it is determined that the test result is passed, and record the test information of the branch code. The merged code is obtained after merging the branch code into the pre-release branch.

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

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

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the test management method according to any one of claims 1 to 6 are implemented.

Images