CN110554962A - Regression testing process covering method, server and computer readable storage medium - Google Patents

Abstract

The present invention relates to a software testing technology, and discloses a process coverage method for regression testing. The method includes: scanning the jump logic corresponding to each page code of an application program according to a preset seed page; sorting out all jumps according to the scanning results Behaviors, and display all the jump behaviors in a tree structure; traverse through the tree structure to obtain all possible functional processes; obtain the corresponding relationship between the page code and the test case; pass the page The code associates the test case with the functional process; according to the corresponding relationship between the test case and the functional process, a test script corresponding to the functional process that needs to be covered by the regression test is obtained. The invention also provides a server and a computer-readable storage medium. The invention can avoid missing testing to cause software defects, or waste manpower and time due to excessive testing range, and improve software quality and testing efficiency.

Description

Process coverage method for regression testing, server and computer-readable storage medium

technical field

The invention relates to the technical field of software testing, in particular to a process coverage method for regression testing, a server and a computer-readable storage medium.

Background technique

At present, in the process of software product development, due to too many parameter and performance optimizations or changes, developers sometimes do not remember the parts they changed, which affects which pages cover which processes. Or, in the case of multiple people making changes, multiple developers do not know what other people have changed, causing some changes to affect or change parts of the process.

Therefore, when regression testing a product, it is difficult to ensure that the test covers the entire process. Usually, either the scope of the test is set small, and missing tests cause software defects; or the scope of the test is too large, wasting too much manpower but not covering the new process. In every regression test, it is difficult to determine whether there is a modification and cannot accurately locate the test scope, which may affect the software quality.

Contents of the invention

In view of this, the present invention proposes a regression testing process coverage method, server and computer-readable storage medium to solve at least one of the above-mentioned technical problems.

First of all, in order to achieve the above object, the present invention proposes a process coverage method for regression testing, which method includes steps:

Scan the jump logic corresponding to each page code of the application according to the preset seed page;

Organize all jump behaviors according to the scanning results, the jump behaviors include the logical relationship between the pages before and after the jump, and display all the jump behaviors in a tree structure;

Traverse through the tree structure to obtain all possible functional processes;

Obtain the corresponding relationship between the page code and the test case;

Associating the test case with the functional process through the page code; and

According to the corresponding relationship between the test case and the functional process, a test script corresponding to the functional process that needs to be covered by the regression test is obtained.

Optionally, in the step of scanning the jump logic corresponding to each page code of the application program according to the preset seed page:

When no code change is detected, using the home page of the application as the seed page;

When the change code is detected, the page where the change code is located is used as the seed page.

Optionally, the all jump behavior includes starting from the seed page and searching for all jump logic associated therewith.

Optionally, in the step of displaying all jumping behaviors, displaying all jumping behaviors in a tree structure through a visual plug-in or Java code.

Optionally, the step of traversing the tree structure to obtain all possible functional processes includes:

The tree structure is traversed according to the page level, and each path in the tree structure is obtained through the logical relationship between parent and child pages, and the functions corresponding to each page of a path are connected together to form a functional flow.

Optionally, when the seed page is the home page of the application, all functional processes of the application are obtained through traversal;

When the seed page is the page where the change code is located, what is traversed is the functional flow affected by the change code.

Optionally, the step of obtaining the corresponding relationship between the page code and the test case includes:

Inject the set statistical code at the corresponding position of the page code, when the test is executed, the code runs to the injection position, executes the corresponding statistical code, generates a coverage statistical report, and records the executed test case coverage start line and end line , so as to analyze and obtain the corresponding relationship between the test case and the page code.

Optionally, the step of obtaining the test script corresponding to the functional flow that needs to be covered by the regression test according to the correspondence between the test case and the functional flow includes:

Obtaining all functional processes that need to be covered by the regression test, obtaining test cases corresponding to the functional processes, obtaining automated test scripts corresponding to the test cases, and automatically combining all the obtained test scripts.

In addition, in order to achieve the above object, the present invention also provides a server, including a memory and a processor, the memory stores a regression test process coverage system that can run on the processor, and the regression test process coverage system When the system is executed by the processor, the steps of the above-mentioned regression testing process coverage method are realized.

Further, in order to achieve the above purpose, the present invention also provides a computer-readable storage medium, the computer-readable storage medium stores a process coverage system for regression testing, and the process coverage system for regression testing can be controlled by at least one processor Execute, so that the at least one processor executes the steps of the above-mentioned regression testing process coverage method.

Compared with the prior art, the regression test process coverage method, server and computer-readable storage medium proposed by the present invention can sort out the functional process related to the page code according to the seed page and page jump logic, and then according to the page code, test The corresponding relationship between use cases and functional processes is obtained to obtain the corresponding test scripts covering the whole process of regression testing. The invention can avoid software defects caused by missed testing, or waste manpower and time due to excessive testing range, and improve software quality and testing efficiency.

Description of drawings

Fig. 1 is a schematic diagram of an optional hardware architecture of the server of the present invention;

Fig. 2 is the program module schematic diagram of the preferred embodiment of the process coverage system of regression test of the present invention;

Fig. 3 is a schematic diagram of a tree structure showing page jump behavior in the present invention;

Fig. 4 is a schematic diagram of a flowchart of an associated page code, a test case and a functional flow in the present invention;

Fig. 5 is a flow diagram of a preferred embodiment of the process coverage method of regression testing of the present invention;

The realization of the purpose of the present invention, functional characteristics and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

It should be noted that the descriptions involving "first", "second", etc. in the present invention are only for descriptive purposes, and should not be understood as indicating or implying their relative importance or implicitly indicating the number of indicated technical features . Thus, the features defined as "first" and "second" may explicitly or implicitly include at least one of these features. In addition, the technical solutions of the various embodiments can be combined with each other, but it must be based on the realization of those skilled in the art. When the combination of technical solutions is contradictory or cannot be realized, it should be considered that the combination of technical solutions does not exist , nor within the scope of protection required by the present invention.

Referring to FIG. 1 , it is a schematic diagram of an optional hardware architecture of the server 2 of the present invention.

In this embodiment, the server 2 may include, but is not limited to, a memory 11 , a processor 12 , and a network interface 13 that can communicate with each other through a system bus. It should be noted that FIG. 1 only shows the server 2 with components 11-13, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.

Wherein, the server 2 may be a computing device such as a rack server, a blade server, a tower server or a cabinet server, and the server 2 may be an independent server or a server cluster composed of multiple servers.

The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), Magnetic Memory, Magnetic Disk, Optical Disk, etc. In some embodiments, the storage 11 may be an internal storage unit of the server 2 , such as a hard disk or memory of the server 2 . In some other embodiments, the memory 11 can also be an external storage device of the server 2, such as a plug-in hard disk equipped on the server 2, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital , SD) card, flash memory card (Flash Card), etc. Certainly, the storage 11 may also include both an internal storage unit of the server 2 and an external storage device thereof. In this embodiment, the memory 11 is generally used to store the operating system and various application software installed on the server 2 , such as program codes of the regression testing process coverage system 200 , and the like. In addition, the memory 11 can also be used to temporarily store various types of data that have been output or will be output.

The processor 12 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chips in some embodiments. This processor 12 is generally used to control the overall operation of said server 2 . In this embodiment, the processor 12 is configured to run program codes stored in the memory 11 or process data, for example, run the process coverage system 200 of the regression test and the like.

The network interface 13 may include a wireless network interface or a wired network interface, and the network interface 13 is generally used to establish a communication connection between the server 2 and other electronic devices.

So far, the hardware structure and functions of the related equipment of the present invention have been introduced in detail. In the following, various embodiments of the present invention will be proposed based on the above description.

First, the present invention proposes a process coverage system 200 for regression testing.

Referring to FIG. 2 , it is a program module diagram of a preferred embodiment of the regression testing process coverage system 200 of the present invention.

In this embodiment, the regression testing process coverage system 200 includes a series of computer program instructions stored in the memory 11. When the computer program instructions are executed by the processor 12, the regression testing of each embodiment of the present invention can be implemented. The process override operation. In some embodiments, the regression testing process coverage system 200 can be divided into one or more modules based on the specific operations implemented by each part of the computer program instructions. For example, in FIG. 2 , the regression testing process coverage system 200 can be divided into a scanning module 201 , a display module 202 , a traversal module 203 , an acquisition module 204 , an association module 205 , and a coverage module 206 . in:

The scanning module 201 is configured to scan the jump logic corresponding to each page code of the application program according to the preset seed page, and record the current page and pages that can be jumped.

Specifically, in the process of developing software such as application programs, regression testing is required. Regression testing needs to cover the full flow of use cases for the application. In addition, the application program often needs to be modified or optimized, and the code change will affect the functional process of the application program, and it is necessary to focus on the regression test of the affected functional process. In this embodiment, however, the process coverage during the regression test can be confirmed based on the page jump logic corresponding to the page code.

The changed codes include newly added codes, modified codes, and the like. In automated testing, take the GIT (distributed version control system) side as an example. When new code modifications or new handover deployments are detected on GIT, the content of code modifications can be viewed through the command line git diff to detect new codes. Or modify the code, you can locate the location of the changed code.

Trigger the script scanning operation, scan the page code through a pre-compiled script (such as nodejs or Python) according to the preset seed page, obtain the jump logic corresponding to each page code, and record the current page and the page that can be jumped. For example, pages can be redirected through methods such as location.href or c.native.forward. In this embodiment, when no code change is detected, the home page of the application is used as the seed page. When a change code is detected, the page where the change code is located is used as the seed page.

The display module 202 is configured to sort out all jumping behaviors according to the scanning results, and display the jumping behaviors in a tree structure.

Specifically, the jump behavior is the logical relationship between the pages before and after the jump, which may include the parent page and the rotor page. The page logic relationship is determined through the page logic jump method. All jumping behaviors refer to searching for all jumping logics associated with the seed page starting from the seed page.

Each page has a page identifier, and each page identifier has arrow points during the jump process, and the relationship between jump nodes can be obtained through these arrow points.

In this embodiment, the logical relationship of the page is displayed in a tree structure through a visual plug-in or Java code, and the visual plug-in may be echart or highChart. For example, FIG. 3 is a schematic diagram showing a tree structure displaying page jumping behavior.

The traversal module 203 is configured to traverse through the tree structure to obtain all possible functional processes.

Specifically, still taking the above-mentioned FIG. 3 as an example, the process of traversing the tree structure is traversing according to the page level, and the path result after traversing is, for example, the home page H-A-A1, or the home page H-A-A2, etc. The functional flow refers to the function corresponding to the jump logic of each page. Each path in the tree structure can be obtained through the logical relationship between parent and child pages (such as A and A1 parent and child pages). Each page has a main function, such as The real-name authentication page is a function of authenticating ID card information, and the page functions of a path are connected together to form a functional process.

When the seed page is the home page of the application, all the functional processes of the application are obtained through traversal. When the seed page is the page where the change code is located, what is traversed is the functional flow affected by the change code.

The acquiring module 204 is configured to acquire the corresponding relationship between page codes and test cases.

Specifically, there is a one-to-many relationship between page codes and test cases, and very few have a one-to-one relationship. Generally speaking, the page code may be H5 code, Java code, etc.

(1) Acquisition of the corresponding relationship between H5 codes and test cases:

In the source code, the karma+istanbul framework is used to analyze the code coverage rate. When the test case is executed on the APP side, the code function will be called, and the corresponding class library will generate a corresponding coverage report, recording the start line and end line of the test case executed on the APP side. . The core of this technology is to inject the set statistical code at the corresponding position of the source code. When the test code is executed, the code runs to the injection position, and the corresponding statistical code will be executed to generate a coverage statistical report, so that the test case can be analyzed and obtained. Correspondence between application page codes.

(2) Acquisition of the corresponding relationship between Java code and test cases:

In the source code, the jacoco framework is used to analyze the code coverage. The class library files used are different, and the technical core is similar to the H5 code.

The associating module 205 is used for associating test cases with the functional flow.

Specifically, the obtaining module 204 can obtain the corresponding relationship between the page code and the test case, and the scanning module 201, the display module 202 and the traversing module 203 can obtain the corresponding relationship between the page code and the functional flow, so further association The test case and the functional flow. Especially for the changed code, it can be obtained which pages are affected and which processes are covered, the scope of influence of the changed code can be accurately located, and the test cases corresponding to these functional processes can be found.

For example, the change code occurs on page A, and the affected functional processes are A-A1, A-A2, A-A3, corresponding to test case 1 and test case 2, then the change code and test case 1 and test case 2 can be obtained Test case 2, and the correspondence between the three parts of the functional process A-A1, A-A2, and A-A3.

In this embodiment, a flow chart may be used to associate the page code, test case and functional flow. For example, FIG. 4 is a schematic diagram of a flowchart associating the page code, the test case and the functional flow.

The coverage module 206 is configured to obtain a test script corresponding to a functional flow that needs to be covered by the regression test according to the correspondence between the test case and the functional flow.

Specifically, all test cases can be divided and written into different automated test scripts (see FIG. 4 ), and test cases correspond to test scripts one-to-one, for example, through titles.

When performing regression testing, UI automation scripts are used, and a path needs to be selected for UI automation use case execution. A page jump logic such as H-A-A1 or H-A-A2 represents a functional process. In this embodiment, all the functional processes that need to be covered by the regression test can be obtained according to the corresponding relationship obtained in the above steps, the test cases corresponding to the functional processes can be obtained, and the automated test scripts corresponding to the test cases can be obtained, according to All the functional processes described above can be automatically combined with all the obtained automated test scripts, and the obtained test scripts can fully cover all the functional processes of the application program.

When a certain piece of code is modified or added (changed code), after locating the functional flow affected by it according to the changed code, it is only necessary to test the functional flow affected by it during regression testing, and the test script can Cover all functional processes it affects. When the test process obtains the association between the code and the test case, add a test case or modify some test cases according to the coverage report, and then add an automated test script or modify the automated test script, according to the functional flow of the test script that affects the changed code Take a focus test.

The regression test process coverage system provided in this embodiment can sort out the functional process related to the page code according to the seed page and the page jump logic, and then obtain the regression test according to the corresponding relationship among the page code, test case, and functional process The whole process covers the corresponding test script, or accurately locates the part of the functional process affected by the changed code, so that the test script covers this part of the functional process during the regression test. This system can avoid software defects caused by missed testing, or waste manpower and time due to excessive testing range, and improve software quality and testing efficiency.

In addition, the invention also proposes a process coverage method for regression testing.

Referring to FIG. 5 , it is a schematic flowchart of a preferred embodiment of the process coverage method for regression testing in the present invention. In this embodiment, according to different requirements, the execution order of the steps in the flowchart shown in FIG. 5 may be changed, and some steps may be omitted.

The method includes the following steps:

Step S500, scan the jump logic corresponding to each page code of the application program according to the preset seed page, and record the current page and pages that can be jumped.

Specifically, in the process of developing software such as application programs, regression testing is required. Regression testing needs to cover the full flow of use cases for the application. In addition, the application program often needs to be modified or optimized, and the code change will affect the functional process of the application program, and it is necessary to focus on the regression test of the affected functional process. In this embodiment, however, the process coverage during the regression test can be confirmed based on the page jump logic corresponding to the page code.

The changed codes include newly added codes, modified codes, and the like. In automated testing, take the GIT side as an example. When a new code modification or new handover deployment is detected on GIT, the content of the code modification can be viewed through the command line git diff, and the new code or modified code can be detected. Change the location of the code.

Trigger the script scanning operation, scan the page code through a pre-compiled script (such as nodejs or Python) according to the preset seed page, obtain the jump logic corresponding to each page code, and record the current page and the page that can be jumped. For example, pages can be redirected through methods such as location.href or c.native.forward. In this embodiment, when no code change is detected, the home page of the application is used as the seed page. When a change code is detected, the page where the change code is located is used as the seed page.

Step S502, organize all jumping behaviors according to the scanning results, and display the jumping behaviors in a tree structure.

Specifically, the jump behavior is the logical relationship between the pages before and after the jump, which may include the parent page and the rotor page. The page logic relationship is determined through the page logic jump method. All jumping behaviors refer to searching for all jumping logics associated with the seed page starting from the seed page.

Each page has a page identifier, and each page identifier has arrow points during the jump process, and the relationship between jump nodes can be obtained through these arrow points.

In this embodiment, the logical relationship of the page is displayed in a tree structure through a visual plug-in or Java code, and the visual plug-in may be echart or highChart. For example, FIG. 3 is a schematic diagram showing a tree structure displaying page jumping behavior.

Step S504, traversing through the tree structure to obtain all possible functional processes.

Specifically, still taking the above-mentioned FIG. 3 as an example, the process of traversing the tree structure is traversing according to the page level, and the path result after traversing is, for example, the home page H-A-A1, or the home page H-A-A2, etc. The functional flow refers to the function corresponding to the jump logic of each page. Each path in the tree structure can be obtained through the logical relationship between parent and child pages (such as A and A1 parent and child pages). Each page has a main function, such as The real-name authentication page is a function of authenticating ID card information, and the page functions of a path are connected together to form a functional process.

When the seed page is the home page of the application, all the functional processes of the application are obtained through traversal. When the seed page is the page where the change code is located, what is traversed is the functional flow affected by the change code.

Step S506, obtaining the corresponding relationship between the page code and the test case.

Specifically, there is a one-to-many relationship between page codes and test cases, and very few have a one-to-one relationship. Generally speaking, the page code may be H5 code, Java code, etc.

(1) Acquisition of the corresponding relationship between H5 codes and test cases:

In the source code, the karma+istanbul framework is used to analyze the code coverage rate. When the test case is executed on the APP side, the code function will be called, and the corresponding class library will generate a corresponding coverage report, recording the start line and end line of the test case executed on the APP side. . The core of this technology is to inject the set statistical code at the corresponding position of the source code. When the test code is executed, the code runs to the injection position, and the corresponding statistical code will be executed to generate a coverage statistical report, so that the test case can be analyzed and obtained. Correspondence between application page codes.

(2) Acquisition of the corresponding relationship between Java code and test cases:

In the source code, the jacoco framework is used to analyze the code coverage. The class library files used are different, and the technical core is similar to the H5 code.

Step S508, associating the test case with the functional flow.

Specifically, the corresponding relationship between the page code and the test case can be obtained according to step S506, and the corresponding relationship between the page code and the functional process can be obtained according to steps S500-S504, therefore, the test case and the functional process can be further associated. Especially for the changed code, it can be obtained which pages are affected and which processes are covered, the scope of influence of the changed code can be accurately located, and the test cases corresponding to these functional processes can be found.

For example, the change code occurs on page A, and the affected functional processes are A-A1, A-A2, A-A3, corresponding to test case 1 and test case 2, then the change code and test case 1 and test case 2 can be obtained Test case 2, and the correspondence between the three parts of the functional process A-A1, A-A2, and A-A3.

In this embodiment, a flow chart may be used to associate the page code, test case and functional flow. For example, FIG. 4 is a schematic diagram of a flowchart associating the page code, the test case and the functional flow.

Step S510, according to the corresponding relationship between the test case and the functional flow, obtain the test script corresponding to the functional flow that needs to be covered by the regression test.

Specifically, all test cases can be divided and written into different automated test scripts (see FIG. 4 ), and test cases correspond to test scripts one-to-one, for example, through titles.

When performing regression testing, UI automation scripts are used, and a path needs to be selected for UI automation use case execution. A page jump logic such as H-A-A1 or H-A-A2 represents a functional process. In this embodiment, all the functional processes that need to be covered by the regression test can be obtained according to the corresponding relationship obtained in the above steps, the test cases corresponding to the functional processes can be obtained, and the automated test scripts corresponding to the test cases can be obtained, according to All the functional processes described above can be automatically combined with all the obtained automated test scripts, and the obtained test scripts can fully cover all the functional processes of the application program.

When a certain piece of code is modified or added (changed code), after locating the functional flow affected by it according to the changed code, it is only necessary to test the functional flow affected by it during regression testing, and the test script can be Cover all functional processes it affects. During the test process, when the code is associated with the test case, new test cases are added or some test cases are modified according to the coverage report, and then automated test scripts are added or modified. According to the functional flow of the test scripts affecting the changed code Take a focus test.

The regression test process coverage method provided in this embodiment can sort out the functional process related to the page code according to the seed page and the page jump logic, and then obtain the regression test according to the corresponding relationship between the page code, test case, and functional process The whole process covers the corresponding test script, or accurately locates the part of the functional process affected by the changed code, so that the test script covers this part of the functional process during the regression test. The method can avoid software defects caused by missed testing, or waste manpower and time due to excessive testing range, and improve software quality and testing efficiency.

The present invention also provides another embodiment, that is, to provide a computer-readable storage medium, the computer-readable storage medium stores a regression test process coverage program, and the regression test process coverage program can be processed by at least one The processor executes, so that the at least one processor executes the steps of the above-mentioned regression testing process coverage method.

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

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process conversion made by using the description of the present invention and the contents of the accompanying drawings, or directly or indirectly used in other related technical fields , are all included in the scope of patent protection of the present invention in the same way.

Claims (10)

1. A method of flow overlay for regression testing, the method comprising the steps of:

Scanning jump logic corresponding to each page code of the application program according to a preset seed page;

Sorting all the skipping behaviors according to the scanning result, wherein the skipping behaviors comprise logical relations existing in the pages before and after skipping, and displaying all the skipping behaviors in a tree structure;

Traversing through the tree structure to obtain all possible functional processes;

Acquiring the corresponding relation between the page code and the test case;

Associating the test case with the functional flow through the page code; and

And obtaining a test script corresponding to the functional flow to be covered by the regression test according to the corresponding relation between the test case and the functional flow.

2. The regression testing process coverage method of claim 1, wherein in the step of scanning jump logic corresponding to each page code of the application program according to a preset seed page:

When no change code is detected, taking a home page of the application program as the seed page;

And when the change code is detected, taking the page where the change code is as the seed page.

3. the flow overlay method of regression testing of claim 1 or 2 wherein said all-jump behavior comprises looking up all-jump logic associated with said seed page starting from said seed page.

4. the flow overlay method of regression testing as claimed in claim 1, wherein in the step of exhibiting all jump behaviors, all jump behaviors are exhibited in a tree structure by a visual plug-in or Java code.

5. the regression testing process coverage method of claim 1, wherein said step of traversing through said tree structure to obtain all possible functional processes comprises:

Traversing the tree structure according to page levels, and acquiring each path in the tree structure through the logical relationship of parent pages and child pages, wherein the function corresponding to each page of one path is connected together to form a functional flow.

6. The process coverage method of regression testing of claim 2, wherein:

When the seed page is the home page of the application program, all functional processes of the application program are obtained through traversal;

and when the seed page is the page where the change code is located, the functional flow influenced by the change code is obtained through traversal.

7. the regression test flow covering method according to claim 1, wherein the step of obtaining the correspondence between the page code and the test case comprises:

and injecting a set statistical code into a position corresponding to the page code, when a test is executed, the code runs to the injection position, the corresponding statistical code is executed, a coverage statistical report is generated, and the coverage starting line and the coverage ending line of the executed test case are recorded, so that the corresponding relation between the test case and the page code is analyzed and obtained.

8. The regression test process coverage method according to claim 1, wherein the step of obtaining a test script corresponding to the functional process to be covered by the regression test according to the correspondence between the test case and the functional process includes:

obtaining all functional flows which need to be covered by the regression test, obtaining a test case corresponding to the functional flows, obtaining an automatic test script corresponding to the test case, and automatically combining all the obtained test scripts.

9. A server, characterized in that the server comprises a memory, a processor, the memory having stored thereon a regression tested process coverage system executable on the processor, the regression tested process coverage system when executed by the processor implementing the steps of the regression tested process coverage method according to any of claims 1-8.

10. A computer-readable storage medium storing a regression-tested process coverage system executable by at least one processor to cause the at least one processor to perform the steps of the regression-tested process coverage method of any one of claims 1-8.