A software testing process management, testing method, device and electronic device

Abstract

The present invention discloses a software test process management, a test method, a device and an electronic device. The test method is applied to the quality assurance side and includes: receiving test cases associated with external users through a use case container of a target requirement; sending the test cases to a development platform so that the development platform tests the code on a target requirement feature branch based on the test cases; sending a second request message to a transaction tracking side so that the transaction tracking side returns a test result of the target requirement based on the second request message; saving the received test result and sending the test result to a test process management side so that the test process management side updates the test progress on a test branch. The technical solution provided by the present invention ensures the archiving of test cases and test results and improves the reliability of software testing.

Description

Technical Field

[0001] The present invention relates to the field of software testing, and particularly to a software testing process management, testing method, device and electronic device. Background Art

[0002] Currently, software projects and requirements within each company will be tested by testers before being released to the application market. However, current testing lacks standardized management. For the testing of many projects and requirements, it is solely based on the experience of testers. Test cases and test results are not archived and stored, and no products are left during the testing process, which brings great challenges to the retesting and regression of this module in the future. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a software testing process management, testing method, device and electronic device, thereby ensuring the archiving of test cases and test results and improving the reliability of software testing.

[0004] According to a first aspect, the present invention provides a software testing process management method, which is applied to a testing process management terminal. The method includes: receiving an external user instruction, and creating a test branch for recording the test progress of a target requirement based on the external user instruction; after the successful creation of the test branch, sending a notification message to a quality assurance terminal, so that the quality assurance terminal creates a use case container for associating test cases of the target requirement based on the notification message, and the use case container is used to archive the test cases.

[0005] Optionally, before sending the notification message to the quality assurance terminal, the method further includes: sending a request message to a transaction tracking terminal, so that the transaction tracking terminal returns the requirement identification information of the target requirement based on the request message, and the transaction tracking terminal is used to track the test results of the target requirement; generating the notification message based on the requirement identification information.

[0006] Optionally, the generating the notification message based on the requirement identification information includes: packaging the requirement identification information, software identification, system type to which the software belongs, test branch name and test person in charge identification to generate the notification message.

[0007] Optionally, after the quality assurance terminal creates a use case container for associating test cases of the target requirement based on the notification message, the quality assurance terminal sends a second notification message to the client of the test person in charge based on the test person in charge identification.

[0008] Optionally, the method further includes: sending a third notification message to a development platform, so that the development platform creates a feature branch for developing the target requirement.

[0009] According to a second aspect, the present invention provides a software testing method, which is applied to a quality assurance end. The method includes: receiving test cases associated with external users through a use case container of a target requirement; sending the test cases to a development platform so that the development platform tests the code on a target requirement feature branch based on the test cases; sending a second request message to a transaction tracking end so that the transaction tracking end returns a test result of the target requirement based on the second request message; saving the received test result and sending the test result to a test process management end so that the test process management end updates the test progress on a test branch.

[0010] Optionally, the method further includes: receiving a test progress update result returned by the test process management end; checking whether all the test cases in the use case container are tested based on the test progress update result; if the testing is completed, generating a test report based on the test result of the target requirement; if the testing is not completed, returning to the step of sending the test cases to the development platform so that the development platform tests the code on the target requirement feature branch based on the test cases.

[0011] According to a third aspect, the present invention provides a software testing device, which is applied to a quality assurance end. The device includes: a use case association module for receiving test cases associated with external users through a use case container of a target requirement; a test module for sending the test cases to a development platform so that the development platform tests the code on a target requirement feature branch based on the test cases; a request result module for sending a second request message to a transaction tracking end so that the transaction tracking end returns a test result of the target requirement based on the second request message; a progress update module for saving the received test result and sending the test result to a test process management end so that the test process management end updates the test progress on a test branch.

[0012] According to a third aspect, an embodiment of the present invention provides an electronic device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the method described in the first aspect or any optional implementation manner of the first aspect.

[0013] According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores computer instructions for causing a computer to execute the method described in the first aspect or any optional implementation manner of the first aspect.

[0014] The technical solution provided by this application has the following advantages:

[0015] The technical solution provided by this application sets up a test branch for recording the test process and a use case container for saving and associating test cases through the test process management terminal and the quality assurance terminal respectively, and combines the transaction tracking terminal to track the test results during the test process. When the test is in progress, the test progress is recorded in detail based on the test branch, the tester is forced to associate and retain the test cases based on the use case container, the test results of the target requirement are tracked in combination with the transaction tracking terminal, and the test results are obtained and archived at the quality assurance terminal. Thereby, it avoids the lack of test basis for the target requirement during subsequent retesting and regression, and ensures the reliability of the target requirement test. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The features and advantages of the present invention will be more clearly understood by referring to the accompanying drawings. The drawings are schematic and should not be construed as imposing any limitation on the present invention. In the drawings:

[0017] Figure 1 Shows a schematic diagram of the steps of a software test process management method in one embodiment of the present invention;

[0018] Figure 2 Shows a flowchart of a software test process management method in one embodiment of the present invention;

[0019] Figure 3 Shows a schematic diagram of the steps of a software test method in one embodiment of the present invention;

[0020] Figure 4 Shows a flowchart of a software test method in one embodiment of the present invention;

[0021] Figure 5 Shows a schematic diagram of the structure of a software test device in one embodiment of the present invention;

[0022] Figure 6 Shows a schematic diagram of the structure of an electronic device in one embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0024] Please refer to Figure 1 and Figure 2, in one embodiment, a software test process management method is applied to a test process management terminal and specifically includes the following steps:

[0025] Step S101: Receive an external user instruction and create a test branch based on the external user instruction for recording the test progress of the target requirement.

[0026] Step S102: After the test branch is successfully created, send a notification message to the quality assurance terminal so that the quality assurance terminal creates a use case container for associating with the test cases of the target requirement based on the notification message, and the use case container is used to file the test cases.

[0027] Specifically, before the test is carried out, a test management system is first established based on the test flow management terminal and the quality assurance terminal. When the R & D personnel receive the requirement document from the product personnel, a test branch is first created on the test flow management terminal according to the target requirement for recording the test progress. Among them, the test flow management terminal includes but is not limited to a server and a personal computer. In order to make the test cases be compulsorily filed and the test be automated, a quality assurance terminal is also set up. When the test branch of the target requirement is created, it means that the preparation work of the recording process is completed. The test flow management terminal will call the interface of the quality assurance terminal and send a notification message to the quality assurance terminal. After receiving the notification message, the quality assurance terminal parses the notification message to obtain which requirement the current test belongs to, and then creates a use case container for associating with the test cases of the target requirement (in this embodiment, the use case container is also called test execution). On the one hand, it ensures the strong filing of the test cases and improves the test reliability. On the other hand, when the external testers associate the test cases in the test container, the test is automatically executed, improving the test submission efficiency.

[0028] Specifically, in one embodiment, before step S102, the following steps are further included:

[0029] Step 1: Send a request message to the transaction tracking terminal so that the transaction tracking terminal returns the requirement identification information of the target requirement based on the request message, and the transaction tracking terminal is used to track the test results of the target requirement.

[0030] Step 2: Generate a notification message based on the requirement identification information.

[0031] Specifically, the test status and test results obtained during the test process are implemented through the transaction tracking terminal. In this embodiment, the transaction tracking terminal is a device such as a personal computer or a server on which a transaction tracking component is deployed. The project and transaction tracking tool Jira produced by Atlassian is used. This tool is widely used in work areas such as defect tracking, customer service, requirement collection, process approval, task tracking, project tracking, and agile management. The transaction tracking terminal tracks the target requirement and needs to establish a dependency with the feature branch of the target requirement in the development platform. The requirement identification information of the target requirement is recorded in the transaction tracking terminal, especially the requirement ID of the target requirement. Therefore, in order to ensure the uniqueness of the use case container established in the quality assurance terminal in this embodiment and avoid the quality assurance terminal creating multiple duplicate use case containers in multiple tests for the same requirement, which may cause test confusion, before the test process management terminal sends a notification message to the quality assurance terminal, it first obtains the requirement identification information of the target requirement, such as the requirement ID, from the transaction tracking terminal, and then generates a notification message based on this requirement ID, so that when the quality assurance terminal creates a use case container according to the notification message, it binds the requirement ID. Thus, in the subsequent test process, if the same requirement is tested again, the quality assurance terminal will judge whether the use case container already exists according to the requirement identification information. If it exists, it will not create it repeatedly and directly enter the test, avoiding the generation of test errors, redundant data, and improving the test efficiency.

[0032] Specifically, in one embodiment, step two above specifically includes the following steps:

[0033] Step three: Package the requirement identification information, software identification, system type to which the software belongs, test branch name, and test responsible person identification to generate a notification message. Specifically, in addition to the requirement information, the notification message is also generated based on the software identification, system type to which the software belongs, test branch name, and test responsible person identification, further improving the accuracy of the quality assurance terminal to uniquely create a use case container.

[0034] Specifically, in one embodiment, based on step three above, after the quality assurance terminal creates a use case container for associating test cases of the target requirement based on the notification message, the following steps are further included:

[0035] Step four: The quality assurance terminal sends a second notification message to the client of the test responsible person based on the test responsible person identification. Specifically, the notification message is generated based on the test responsible person identification. When the use case container is successfully created, the quality assurance terminal sends a second notification message to give feedback to the test responsible person. The devices receiving the second notification message include but are not limited to the personal computer, mobile phone, and tablet computer of the test responsible person. Ensure that the use case container is successfully created. If the test responsible person has not received the second notification message within the preset time period, inform the R & D department to repeat the creation step of the test branch to ensure the accurate and reliable creation of the use case container.

[0036] Specifically, in one embodiment, a software test process management method provided by an embodiment of the present invention further includes:

[0037] Step Five: Send a third notification message to the development platform so that the development platform creates a feature branch for developing the target requirement. Specifically, in this embodiment, while sending a notification message to the quality assurance end, the test process management end also sends a third notification message to the development platform (such as the version management system Gitlab) so that the development platform automatically creates a feature branch for developing software functions that meet the target requirements, thus saving the steps for R & D personnel to manually create feature branches and further improving the test efficiency. In addition, a use case container input box is provided in the pop-up window for creating the feature branch, allowing testers or R & D personnel to modify the link of the use case container.

[0038] Please refer to Figure 3 and Figure 4 In one implementation manner, a software test method is applied to the test process management end and specifically includes the following steps:

[0039] Step S201: Receive test cases associated by external users through the use case container of the target requirement.

[0040] Step S202: Send the test cases to the development platform so that the development platform tests the code on the feature branch of the target requirement based on the test cases.

[0041] Step S203: Send a second request message to the transaction tracking end so that the transaction tracking end returns the test result of the target requirement based on the second request message.

[0042] Step S204: Save the received test result and send the test result to the test process management end so that the test process management end updates the test progress on the test branch.

[0043] Specifically, an external user (tester) associates test cases with the quality assurance platform to automatically start the test process. The quality assurance platform sends the test cases to the development platform. The development platform tests the code on the target requirement feature branch based on the test cases associated by the external user to determine whether there are defects in the code. The transaction tracking terminal will track the status during the code test in real time and record the corresponding defects. After the code test is completed, the quality assurance platform sends a second request message to the transaction tracking terminal to request the test results of the previous test, thus avoiding manual filling errors in the test. After receiving the test results returned by the transaction tracking terminal, the quality assurance platform saves the defects recorded in the test results for subsequent retest comparison and defect query. Then, it sends the test results to the test process management terminal so that the test process management terminal can update the test progress on the test branch. This ensures the accurate and complete archiving of test results, test progress, and test cases, thereby improving the reliability of software testing.

[0044] Specifically, in one embodiment, a software test process management method provided by an embodiment of the present invention further includes the following steps:

[0045] Step Six: Receive the test progress update result returned by the test process management terminal.

[0046] Step Seven: Check whether all the test cases in the case container have been tested based on the test progress update result.

[0047] Step Eight: If the test is completed, generate a test report based on the test results of the target requirement.

[0048] Step Nine: If the test is not completed, return to the step of sending the test cases to the development platform so that the development platform tests the code on the target requirement feature branch based on the test cases.

[0049] Specifically, in this embodiment, the quality management platform also receives the progress update result sent by the test process management terminal after each test case is tested. Thus, it determines whether all the test cases in the case container have been tested based on the progress update result. If the test is not completed, it continues to enable the development platform to perform code testing based on the link of the case container. If the test is completed, it obtains the case count and the system platforms with defects, such as the IOS and Android platforms. It automatically fills them into the input box for passing the test and generates a test report. It is sent to the tester's client in forms including but not limited to emails, text messages, and application pop-ups. This further ensures the integrity and reliability of software testing.

[0050] Through the above steps, the technical solution provided by this application sets up a test branch for recording the test process and a use case container for saving and associating test cases on the test process management end and the quality assurance end respectively, and combines with the transaction tracking end to track the test results during the test process. When the test is in progress, the test progress is recorded in detail based on the test branch, the testers are forced to associate and retain the test cases based on the use case container, the test results of the target requirement are tracked in combination with the transaction tracking end, and the test results are obtained and archived on the quality assurance end. Thereby avoiding the situation that there is no test basis for the target requirement during subsequent retesting and regression, and ensuring the reliability of the target requirement test.

[0051] As Figure 5 shown, this embodiment also provides a software testing device, which includes:

[0052] A use case association module 201, configured to receive the test cases associated by external users through the use case container of the target requirement. For the detailed content, refer to the relevant description of step S201 in the above method embodiment, and details will not be described herein again.

[0053] A test module 202, configured to send the test cases to the development platform, so that the development platform tests the code on the target requirement feature branch based on the test cases. For the detailed content, refer to the relevant description of step S202 in the above method embodiment, and details will not be described herein again.

[0054] A request result module 203, configured to send a second request message to the transaction tracking end, so that the transaction tracking end returns the test results of the target requirement based on the second request message. For the detailed content, refer to the relevant description of step S203 in the above method embodiment, and details will not be described herein again.

[0055] A progress update module 204, configured to save the received test results and send the test results to the test process management end, so that the test process management end updates the test progress on the test branch. For the detailed content, refer to the relevant description of step S204 in the above method embodiment, and details will not be described herein again.

[0056] The software testing device provided by the embodiment of the present invention is used to execute the software testing method provided by the above embodiment, and its implementation manner and principle are the same. For the detailed content, refer to the relevant description of the above method embodiment, and details will not be described herein again.

[0057] Through the collaborative cooperation of the above-mentioned various components, the technical solution provided by this application sets up a test branch for recording the test process and a use case container for saving and associating test cases at the test process management end and the quality assurance end respectively, and combines the transaction tracking end to track the test results during the test process. When the test is in progress, the test progress is recorded in detail based on the test branch, the testers are forced to associate and retain the test cases based on the use case container, the test results of the target requirements are tracked in combination with the transaction tracking end, and the test results are obtained and filed at the quality assurance end. Thereby, it avoids the lack of test basis for the target requirements during subsequent retesting and regression, and ensures the reliability of the target requirements test.

[0058] Figure 6 An electronic device according to an embodiment of the present invention is shown. The device includes a processor 901 and a memory 902, which can be connected by a bus or other means. Figure 6 Taking the connection by bus as an example.

[0059] The processor 901 can be a central processing unit (CPU). The processor 901 can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. chips, or a combination of the above various types of chips.

[0060] The memory 902, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the above method embodiments. The processor 901 executes various functional applications and data processing of the processor by running the non-transitory software programs, instructions, and modules stored in the memory 902, that is, implements the methods in the above method embodiments.

[0061] The memory 902 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created by the processor 901 and the like. In addition, the memory 902 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory 902 may optionally include a memory remotely provided with respect to the processor 901, and these remote memories can be connected to the processor 901 through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0062] One or more modules are stored in the memory 902 and, when executed by the processor 901, execute the methods in the above method embodiments.

[0063] For specific details of the above electronic device, reference may be made to the corresponding relevant descriptions and effects in the above method embodiments for understanding, and details will not be repeated here.

[0064] Those skilled in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The implemented program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the above method embodiments. Among them, the storage medium can be a magnetic disk, an optical disc, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (abbreviation: HDD), or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above types of memories.

[0065] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A software testing process management method, characterized in that, Applied to the test process management side, the method includes: Receiving an external user instruction and creating a test branch for recording the test progress of the target requirement based on the external user instruction; Sending a request message to the transaction tracking side so that the transaction tracking side returns the requirement identification information of the target requirement based on the request message, and the transaction tracking side is used to track the test result of the target requirement; Generating a notification message based on the requirement identification information; After the test branch is successfully created, sending the notification message to the quality assurance side so that the quality assurance side creates a use case container for associating the test cases of the target requirement based on the notification message, and the use case container is used to file the test cases; The quality assurance side sends the test cases to the development platform so that the development platform tests the code on the feature branch of the target requirement based on the test cases; the quality assurance side sends a second request message to the transaction tracking side so that the transaction tracking side returns the test result of the target requirement based on the second request message; the quality assurance side saves the received test result and sends the test result to the test process management side so that the test process management side updates the test progress on the test branch; after receiving the test result returned by the transaction tracking side, the quality assurance side saves the defects recorded in the test result.

2. The method according to claim 1, wherein The generating the notification message based on the requirement identification information includes: Packaging the requirement identification information, software identification, system type to which the software belongs, test branch name, and test responsible person identification to generate the notification message.

3. The method according to claim 2, characterized in that, After the quality assurance side creates a use case container for associating the test cases of the target requirement based on the notification message, the quality assurance side sends a second notification message to the client of the test responsible person based on the test responsible person identification.

4. The method according to claim 1, wherein The method further includes: Sending a third notification message to the development platform so that the development platform creates a feature branch for developing the target requirement.

5. A software testing method, characterized in that, Applied to the quality assurance side, the method includes: Receiving the test cases associated by the external user through the use case container of the target requirement, and the use case container is used to file the test cases. The use case container is created based on the notification message, and the notification message is generated by the test process management side based on the requirement identification information. The requirement identification information is that the test process management side sends a request message to the transaction tracking side, and the transaction tracking side returns the requirement identification information of the target requirement based on the request message. The transaction tracking side is used to track the test result of the target requirement; sending the test cases to the development platform so that the development platform tests the code on the feature branch of the target requirement based on the test cases; Sending a second request message to the transaction tracking side so that the transaction tracking side returns the test result of the target requirement based on the second request message; Save the received test results and send the test results to the test process management terminal so that the test process management terminal can update the test progress on the test branch; after the quality assurance terminal receives the test results returned by the transaction tracking terminal, save the defects recorded in the test results.

6. The method according to claim 5, characterized in that, The method further includes: Receive the test progress update result returned by the test process management terminal; Check whether all the test cases in the test case container have been tested based on the test progress update result; If the testing is completed, generate a test report based on the test results of the target requirement; If the testing is not completed, return to the step of sending the test cases to the development platform so that the development platform can test the code on the target requirement feature branch based on the test cases.

7. A software testing device, characterized in that Applied to the quality assurance terminal, the device includes: A use case association module, configured to receive test cases associated by an external user through a use case container of a target requirement. The use case container is used to file the test cases. The use case container is created based on a notification message, and the notification message is generated by the test process management terminal based on requirement identification information. The requirement identification information is that the test process management terminal sends a request message to the transaction tracking terminal, and the transaction tracking terminal returns the requirement identification information of the target requirement based on the request message. The transaction tracking terminal is used to track the test results of the target requirement; A test module, configured to send the test cases to the development platform so that the development platform can test the code on the target requirement feature branch based on the test cases; A request result module, configured to send a second request message to the transaction tracking terminal so that the transaction tracking terminal returns the test results of the target requirement based on the second request message; A progress update module, configured to save the received test results and send the test results to the test process management terminal so that the test process management terminal can update the test progress on the test branch; after the quality assurance terminal receives the test results returned by the transaction tracking terminal, save the defects recorded in the test results.

8. An electronic device, characterized in that, Including: A memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the method according to any one of claims 1-6.

Images