CN114968818A - Automated test management method, device, terminal device and storage medium - Google Patents

Abstract

The embodiment of the invention discloses an automatic test management method, an automatic test management device, terminal equipment and a storage medium, and relates to the technical field of automatic tests. The method comprises the following steps: extracting and deleting a JIRA test case library through a test script according to the test engineering to obtain a target test case; acquiring a trigger signal to execute a test project and obtain a test result file of a target test case; updating the test result to a corresponding target test case through the test script according to the test result file; calculating the test execution passing rate of the target test case according to the test result and comparing the test execution passing rate with the preset quality red line to obtain a comparison result; and displaying the test result and the comparison result by means of JIRA visualization. According to the method, the target test cases of different test platforms can be obtained through the test scripts, the test results of the test engineering are analyzed and then submitted to the JIRA for processing and displaying, so that the automatic tests of different platforms are managed, and convenience is brought to testers.

Description

Automated test management method, device, terminal device and storage medium

technical field

The present invention relates to the technical field of automated testing, and in particular, to an automated testing management method, device, terminal device and storage medium.

Background technique

Because the automated test methods and test script languages of different businesses and platforms are different, there is no unified automated test management method to manage automated tests on different platforms. For example, the existing commercial DevOps platform, Alibaba Cloud Effect and Blue Whale do not support unified management of all automated tests. The automation they provide supports c++, java and other unit tests, interface tests and UI tests only support the WEB side, and the desktop side. It is not supported by the automated test on the mobile terminal, that is, the existing automated test management method only supports the management of automated tests on the WEB side, and cannot manage automated tests on different platforms.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide an automated test management method, device, terminal device and storage medium, aiming to solve the problem that automated tests of different platforms cannot be managed by using the existing test management method.

In a first aspect, an embodiment of the present invention provides an automated test management method. The automated test management method includes: extracting and deleting a JIRA test case library through a test script according to a test project to obtain a target test case; obtaining a trigger signal to Execute the test project and obtain the test result file of the target test case; update the test result to the corresponding target test case through the test script according to the test result file; calculate the target test according to the test result The test execution pass rate of the use case is compared with the preset quality red line to obtain the comparison result; the test result and the comparison result are displayed visually with the help of JIRA.

In a second aspect, an embodiment of the present invention further provides an automated test management device, the device includes: a first extraction and deletion unit, configured to extract and delete the JIRA test case library through a test script according to a test project to obtain a target test case The acquisition execution unit is used to acquire the trigger signal to execute the test project and obtain the test result file of the target test case; the first update unit is used to update the test result to the corresponding test result file through the test script according to the test result file. In the target test case of The test results and the comparison results are displayed visually.

In a third aspect, an embodiment of the present invention further provides a terminal device, the terminal device includes a memory and a processor, the memory stores a computer program, and the processor implements the above method when executing the above computer program.

In a fourth aspect, an embodiment of the present invention further provides a storage medium, where the storage medium stores a computer program, and the computer program implements the foregoing method when executed by a processor.

The embodiments of the present invention provide an automated test management method, device, terminal device and storage medium, which include: extracting and deleting a JIRA test case library through a test script according to a test project to obtain a target test case; obtaining a trigger signal to execute The test project and the test result file of the target test case are obtained; the test result is updated to the corresponding target test case through the test script according to the test result file; the target test case is calculated according to the test result The pass rate of the test execution is compared with the preset quality red line to obtain the comparison result; the test result and the comparison result are displayed visually with the help of JIRA. The method can obtain the target test cases of different test platforms through test scripts, analyze the test results of the test project, and then submit them to JIRA for processing and display, which realizes the management of automated tests on different platforms and provides convenience for testers.

Description of drawings

In order to explain the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention, which are of great significance to the art For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic flowchart of an automated test management method provided by an embodiment of the present invention;

2 is a schematic block diagram of an automated test management apparatus provided by an embodiment of the present invention;

FIG. 3 is a schematic block diagram of a terminal device according to an embodiment of the present invention;

4 is a display result obtained by an automated test management method provided by an embodiment of the present invention;

FIG. 5 is another display result obtained by an automated test management method provided by an embodiment of the present invention.

Detailed ways

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. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It is to be understood that the terms "comprising" and "package" when used in this specification and the appended claims are also to be understood that the terms used in this specification of the invention are for the purpose of describing particular embodiments only and not It is not intended to limit the invention. As used in this specification and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly dictates otherwise. form.

It should further be understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items .

As used in this specification and the appended claims, the term "if" may be contextually interpreted as "when" or "once" or "in response to determining" or "in response to detecting" . Similarly, the phrases "if it is determined" or "if the [described condition or event] is detected" may be interpreted, depending on the context, to mean "once it is determined" or "in response to the determination" or "once the [described condition or event] is detected. ]" or "in response to detection of the [described condition or event]".

JENKINS is an open source software project. It is a continuous integration tool developed based on Java. It is used to monitor continuous and repetitive work. It aims to provide an open and easy-to-use software platform that enables continuous integration of software projects.

JIRA is a project and transaction tracking tool produced by Atlassian, which is widely used in defect tracking, customer service, requirements collection, process approval, task tracking, project tracking and agile management.

The automated test management method in the embodiment of the present invention can be applied to terminal devices, such as smart devices such as mobile phones, tablet computers, notebook computers, and desktop computers. The function of automatic test management is realized by the application software installed on the terminal device.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of an automated test management method provided by an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps S1-S5.

S1, extract and delete the JIRA test case library through the test script according to the test project to obtain the target test case.

In the specific implementation, the JIRA test case library is extracted and deleted through the test script according to the test project to obtain the target test case. In one embodiment, the test cases of the test project are parsed and compared with the test case library of JIRA. Specifically, all the test cases of the test project are parsed through the PYTHON test script, and the JIRA test case library of the test project is obtained through the JIRA API (Application Programming Interface). The purpose of this step is to update the JIRA test case library through all the test cases of the test project to ensure the correctness of the target test cases in the test platform.

Further, if the test case of the test project is not in the test case library of JIRA, extract the test case to the test case library of JIRA, and delete all the non-existent test cases in the test case library of JIRA. The test case of the test project is obtained to obtain the target test case.

In one embodiment, the test cases in the JIRA test case library are provided with an automated reference field. If the reference field is consistent with the test case name in the test project, it indicates the same test case, and the test case in the test project is obtained through the PYTHON test script. The name of the test case is compared with the automatic reference field of the test case in the JIRA test case library. When the two are consistent, it means that the test case exists. At this time, the test case in the JIRA test case library is kept and not processed; when the two are inconsistent, delete it. Add the test case in the JIRA test case library and add the test case in the test project to the JIRA test case library; after the comparison, the test case library of JIRA will be the target test case of the test project, thus realizing automation Maintain test cases for the test project.

In one embodiment, the following steps are further included after step S1:

Query whether the JIRA test plan exists in the test project. Specifically, use the PYTHON test script to call the API of JIRA to query whether there is a JIRA test plan in the test project.

Further, if the JIRA test plan does not exist in the test project, the JIRA test plan is newly created. Specifically, if there is a JIRA test plan in the test project, it will not be processed. If there is no JIRA test plan in the test project, a new JIRA test plan will be created through the JIRA API. Among them, the JIRA test plan is used to display the test results.

Further, create a new test cycle under the JIRA test plan and import the target test case into the test cycle. Specifically, in one embodiment, a PYTHON test script is used to call the API of JIRA to create a new test cycle under the JIRA test plan (or a newly created JIRA test plan) (the name of the test cycle is generally month-day-hour-minute to avoid repeated name) in order to clearly display the test results for each test cycle. Use the PYTHON test script to call JIRA's API to import the target test cases under the test plan into the new test cycle, so as to associate the new test cycle with the target test cases of the test project, which is convenient for subsequent analysis and display of test results.

S2: Acquire a trigger signal to execute the test project and obtain a test result file of the target test case.

In a specific implementation, a trigger signal is acquired to execute the test project and obtain a test result file of the target test case. Specifically, after obtaining the target test case and importing the target test case into the new test cycle, the test project can be executed. In one embodiment, the trigger signal may be set as a signal for timing triggering of JENKINS, or the trigger signal of JENKINS may be set according to actual conditions, which is not specifically limited herein.

S3, update the test result to the corresponding target test case through the test script according to the test result file.

In a specific implementation, the test result is updated to the corresponding target test case through a test script according to the test result file. In one embodiment, step S3 specifically includes the following steps.

Parse the test result file to obtain a test result of the target test case, wherein the test result includes a test failure. Specifically, the test result file (XML file) is parsed through the PYTHON test script to obtain the test result of the target test case. The test results for each test case include test failure, pass, ignore, number of passed cases, total number of test cases, total lines of code, and lines of coverage to prepare for the presentation of subsequent test results.

Further, the test result is updated to the corresponding target test case through a test script. Specifically, in one embodiment, the test results of each test case are obtained after parsing the test results through the PYTHON test script, and then the test results are updated to the corresponding target test cases through the API of JIRA, thereby realizing the target test case and the test The results are automatically associated. At this time, the overall execution record of the test project can be seen under the newly created test cycle.

Further, if the test result is a test failure, submit the test failure defect to JIRA through a test script and associate the test failure defect with the corresponding target test case.

Specifically, in one embodiment, when the test result of the target test case is a test failure, the test failure defect is synchronously submitted to JIRA through the API of JIRA, thereby realizing the automatic submission of the test failure defect.

S4: Calculate the test execution pass rate of the target test case according to the test result and compare it with a preset quality red line to obtain a comparison result.

In a specific implementation, the test execution pass rate of the target test case is calculated according to the test result and compared with a preset quality red line to obtain a comparison result. In one embodiment, step S4 includes the step of: calculating a test execution pass rate, code coverage rate, test execution times, and test execution case numbers according to the test results and writing them into the JIRA test plan.

In a specific implementation, the test execution pass rate, code coverage rate, test execution times, and test execution use cases are calculated according to the test results and written into the JIRA test plan. Specifically, in one embodiment, the calculation of the test result is realized by the PYTHON test script, wherein, the test execution pass rate=the number of passed use cases/the total number of test cases, the code coverage rate=covered code lines/total code lines; and the test execution The pass rate, code coverage rate, number of test executions, and the number of test execution cases are written into the corresponding fields in the test plan through the JIRA API to display the test results.

In one embodiment, step S4 further includes the following steps:

The test execution pass rate is written into the TXT file; specifically, in one embodiment, in order to facilitate JENKINS to obtain data, the test execution pass rate calculated in step S3 is written into the TXT file through the PYTHON test script.

Further, the test execution pass rate in the TXT file is obtained and compared with the preset quality red line to obtain a comparison result.

In a specific implementation, the test execution pass rate in the TXT file is obtained and compared with a preset quality red line to obtain a comparison result. Specifically, in one embodiment, JENKINS obtains the test execution pass rate value in the TXT file and compares it with the preset quality red line set by JENKINS. When the preset quality red line is reached, the JENKINS test project passes, otherwise the test project is tested If it fails or is interrupted, it means that the test project fails.

S5, the test results and the comparison results are displayed visually by means of JIRA.

In a specific implementation, the test results and the comparison results are displayed visually by means of JIRA. Specifically, in an embodiment, please refer to FIG. 4 to FIG. 5 . From FIG. 5 , the test results and comparison results of the test project can be clearly obtained, including automatic submission of defects, defect status distribution, and test execution under different test cycles. The pass rate and the number of automatic update test cases; from Figure 5, the total number of test cases, the number of automatically submitted defects and the code coverage rate under different test projects can be clearly obtained.

It should be noted that the trigger signal is obtained through JENKINS to trigger the test project to execute the test through the test script, thereby realizing the automatic management of target test cases of different test platforms, automatic execution of test projects, automatic submission of defects to JIRA, and update of test results. To target test cases, associate target test cases with test failure defects, and realize fully automated closed-loop management of test engineering, which provides great convenience for testers and improves test efficiency.

An embodiment of the present invention provides an automated test management method, which includes: extracting and deleting a JIRA test case library through a test script according to a test project to obtain a target test case; obtaining a trigger signal to execute the test project and obtain the The test result file of the target test case; update the test result to the corresponding target test case through the test script according to the test result file; calculate the test execution pass rate of the target test case according to the test result and compare it with the prediction. A quality red line is set for comparison to obtain comparison results; the test results and the comparison results are visualized by means of JIRA. The method can obtain the target test cases of different test platforms through test scripts, analyze the test results of the test project, and then submit them to JIRA for processing and display, which realizes the management of automated tests on different platforms and provides convenience for testers.

FIG. 2 is a schematic block diagram of an automated test management apparatus provided by an embodiment of the present invention. As shown in FIG. 2 , corresponding to the above automated test management method, the present invention further provides an automated test management apparatus 100 . The automated test management apparatus 100 includes a unit for executing the above-mentioned automated test management method, and the apparatus can be configured in a desktop computer, a tablet computer, a laptop computer, and other terminal devices. Specifically, referring to FIG. 2 , the automated test management apparatus 100 includes a first extraction and deletion unit 101 , an acquisition and execution unit 102 , a first update unit 103 , a calculation and comparison unit 104 , and a display unit 105 .

The first extracting and deleting unit 101 is used for extracting and deleting the JIRA test case library through the test script according to the test project to obtain the target test case; the obtaining and executing unit 102 is used for obtaining the trigger signal to execute the test project and obtain. The test result file of the target test case; the first update unit 103 is used to update the test result to the corresponding target test case through the test script according to the test result file; the calculation and comparison unit 104 is used for The test execution pass rate of the target test case is calculated according to the test result and compared with a preset quality red line to obtain a comparison result; the display unit 105 is configured to visually display the test result and the comparison result by means of JIRA.

In one embodiment, the first extraction and deletion unit 101 includes: an analysis and comparison unit and a second extraction and deletion unit.

The parsing and comparison unit is used for parsing the test case of the test project and comparing it with the test case library of JIRA; the second extracting and deleting unit is used if the test case of the test project is not in the test case library of JIRA , the test case is extracted to the test case library of JIRA, and the test cases that are not of the test project in the test case library of JIRA are deleted to obtain the target test case.

In an embodiment, the first extracting and deleting unit 101 further includes: a query unit, a new unit, and an import unit.

The query unit is used to query whether the JIRA test plan exists in the test project, and the new unit is used to create the JIRA test plan if the JIRA test plan does not exist in the test project; the The import unit is used to create a new test cycle under the JIRA test plan and import the target test case into the test cycle.

In an embodiment, the first updating unit 103 includes: a parsing unit and a second updating unit.

The parsing unit is configured to parse the test result file to obtain the test result of the target test case, wherein the test result includes a test failure; the second update unit is configured to update the test result to corresponding to the target test case.

In an embodiment, the first updating unit 103 further includes: a submitting unit.

The submitting unit is configured to submit the test failure defect to JIRA through a test script and associate the test failure defect with the corresponding target test case if the test result is a test failure.

In one embodiment, the calculating and comparing unit 104 includes: a calculating and writing unit.

The calculation and writing unit is configured to calculate the test execution pass rate, code coverage rate, test execution times, and test execution case numbers according to the test results, and write them into the JIRA test plan.

In an embodiment, the calculating and comparing unit 104 further includes: a writing unit and an obtaining and comparing unit.

The writing unit is configured to write the test execution pass rate into the TXT file; the acquisition and comparison unit is configured to acquire the test execution pass rate in the TXT file and compare it with a preset quality red line to obtain a comparison result.

The above-mentioned automated test management apparatus can be implemented in the form of a computer program, and the computer program can run on the terminal device as shown in FIG. 3 .

Referring to FIG. 3 , the terminal device 300 includes a processor 302 , a memory and a network interface 305 connected through a system bus 301 , wherein the memory may include a non-volatile storage medium 303 and an internal memory 304 .

The nonvolatile storage medium 303 can store an operating system 3031 and a computer program 3032 . The computer program 3032, when executed, can cause the processor 302 to perform an automated test management method.

The processor 302 is used to provide computing and control capabilities to support the operation of the entire terminal device 300 .

The internal memory 304 provides an environment for running the computer program 3032 in the non-volatile storage medium 303. When the computer program 3032 is executed by the processor 302, the processor 302 can execute an automated test management method.

The network interface 305 is used for network communication with other devices. Those skilled in the art can understand that the structure shown in FIG. 3 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the terminal device 300 to which the solution of the present application is applied. The specific terminal device 300 may include more or fewer components than shown, or combine certain components, or have a different arrangement of components.

Wherein, the processor 302 is used to run the computer program 3032 stored in the memory to realize the following steps:

Extract and delete the JIRA test case library through the test script according to the test project to obtain the target test case; obtain the trigger signal to execute the test project and obtain the test result file of the target test case; pass the test according to the test result file The script updates the test results to the corresponding target test cases; calculates the test execution pass rate of the target test cases according to the test results and compares them with the preset quality red line to obtain the comparison results; visualizes the test results with the help of JIRA Test results and said comparison results.

In one embodiment, extracting and deleting the JIRA test case library through the test script according to the test project to obtain the target test case includes: parsing the test case of the test project and comparing the test case library of JIRA; If the test case of the test project is not in the test case library of JIRA, then extract the test case to the test case library of JIRA, and delete the tests in the test case library of JIRA that are not of the test project use case to get the target test case.

In one embodiment, after extracting and deleting the JIRA test case library through the test script according to the test project to obtain the target test case, the method further includes: querying whether the JIRA test plan exists in the test project, if the If the JIRA test plan does not exist in the test project, create the JIRA test plan; create a new test cycle under the JIRA test plan and import the target test case into the test cycle.

In one embodiment, the updating of the test results to the corresponding target test cases through a test script according to the test result files includes: parsing the test result files to obtain the test results of the target test cases, The test result includes test failure; the test result is updated to the corresponding target test case through a test script.

In one embodiment, after updating the test result to the corresponding target test case through the test script according to the test result file, the method further includes: if the test result is a test failure, the test is failed by the test script. The defect is submitted to JIRA and the test failure defect is associated with the corresponding target test case.

In one embodiment, calculating the test execution pass rate of the target test case according to the test result and comparing it with a preset quality red line to obtain the comparison result includes: calculating the test execution pass rate according to the test result, Code coverage, number of test executions, and number of test execution cases are written into the JIRA test plan.

In one embodiment, the calculating the test execution pass rate of the target test case according to the test result and comparing it with a preset quality red line to obtain the comparison result further includes: writing the test execution pass rate into a TXT file; The test execution pass rate in the TXT file is obtained and compared with the preset quality red line to obtain the comparison result.

It should be understood that, in this embodiment of the present application, the processor 302 may be a central processing unit (Central Processing Unit, CPU), and the processor 302 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), off-the-shelf Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. Wherein, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor or the like.

It can be understood by those skilled in the art that all or part of the processes in the methods for implementing the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a storage medium, which is a storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the above-described method embodiments.

Therefore, the present invention also provides a storage medium. The storage medium may be a storage medium. The storage medium stores a computer program. When executed by the processor, the computer program causes the processor to execute any of the above-mentioned embodiments of the automated test management method of the present invention.

The storage medium is a physical, non-transitory storage medium, such as a U disk, a removable hard disk, a read-only memory (Read-Only Memory, ROM), a magnetic disk or an optical disk and other physical storage that can store program codes. medium.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and other division methods may be used in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.

The steps in the method of the embodiment of the present invention may be adjusted, combined and deleted in sequence according to actual needs. Units in the apparatus of the embodiment of the present invention may be combined, divided, and deleted according to actual needs. In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a storage medium. Based on this understanding, the technical solution of the present invention is essentially or a part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a terminal device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the invention. Thus, even if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of various equivalents within the technical scope disclosed by the present invention. Modifications or substitutions should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (10)

1. An automated test management method, comprising:

extracting and deleting a JIRA test case library through a test script according to the test engineering to obtain a target test case;

acquiring a trigger signal to execute the test project and obtain a test result file of the target test case;

updating the test result to the corresponding target test case through the test script according to the test result file;

calculating the test execution passing rate of the target test case according to the test result and comparing the test execution passing rate with a preset quality red line to obtain a comparison result;

the test results and the comparison results are presented by means of JIRA visualization.

2. The automated test management method according to claim 1, wherein the extracting and deleting the jita test case library by the test script according to the test engineering to obtain the target test case comprises:

analyzing the test case of the test engineering and comparing the test case with a JIRA test case library;

if the test case of the test engineering is not in the JIRA test case library, extracting the test case into the JIRA test case library, and deleting the JIRA test case which is not in the test engineering in the JIRA test case library to obtain the target test case.

3. The automated test management method according to claim 2, wherein after the extracting and deleting the jita test case library by the test script according to the test engineering to obtain the target test case, the method further comprises:

querying whether the JIRA test plan exists in the test project;

if the JIRA test plan does not exist in the test project, newly establishing the JIRA test plan;

and newly building a test period under the JIRA test plan and introducing the target test case into the test period.

4. The automated test management method according to claim 3, wherein the updating of the test result to the corresponding target test case through the test script according to the test result file comprises:

analyzing the test result file to obtain a test result of the target test case, wherein the test result comprises a test failure;

and updating the test result to the corresponding target test case through the test script.

5. The automated test management method according to claim 4, wherein after the test result is updated to the corresponding target test case by the test script according to the test result file, the method further comprises:

if the test result is test failure, submitting the test failure defect to JIRA through the test script and associating the test failure defect with the corresponding target test case.

6. The method according to claim 5, wherein the calculating a test execution passing rate of the target test case according to the test result and comparing the test execution passing rate with a preset quality red line to obtain a comparison result includes:

and calculating the test execution passing rate, the code coverage rate, the test execution times and the test execution case number according to the test result, and writing the test execution passing rate, the code coverage rate, the test execution times and the test execution case number into the JIRA test plan.

7. The automated test management method according to claim 6, wherein the calculating a test execution passing rate of the target test case according to the test result and comparing the test execution passing rate with a preset quality red line to obtain a comparison result further comprises:

writing the test execution passing rate into a TXT file;

and acquiring the test execution passing rate in the TXT file and comparing the test execution passing rate with a preset quality red line to obtain a comparison result.

8. An automated test management apparatus, comprising:

the first extraction and deletion unit is used for extracting and deleting the JIRA test case library through the test script according to the test engineering so as to obtain a target test case;

the acquisition execution unit is used for acquiring a trigger signal to execute the test project and obtain a test result file of the target test case;

the first updating unit is used for updating the test result to the corresponding target test case through the test script according to the test result file;

the calculation comparison unit is used for calculating the test execution passing rate of the target test case according to the test result and comparing the test execution passing rate with a preset quality red line to obtain a comparison result;

a presentation unit for visually presenting the test result and the comparison result by means of JIRA.

9. A terminal device, characterized in that the terminal device comprises a memory having stored thereon a computer program and a processor implementing the method according to any of claims 1-7 when executing the computer program.

10. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.

Images