WO2019200800A1

WO2019200800A1 - Test effect display method for test case, electronic device, and storage medium

Info

Publication number: WO2019200800A1
Application number: PCT/CN2018/102100
Authority: WO
Inventors: 毛皓; 邹文涛; 王旭辉
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-04-17
Filing date: 2018-08-24
Publication date: 2019-10-24
Also published as: CN108763054A; CN108763054B

Abstract

The present application relates to a test effect display method for a test case, an electronic device, and a readable storage medium. The method comprises: analyzing a code of a system to be tested to obtain a static invoking structure among different methods in the code, and establishing different static method chaining according to the static invoking structure; displaying the static method chaining by the static invoking structure on the basis of a preset display rule; recording the method chaining flowing in the dynamic link test execution process when executing a dynamic link test for the system to be tested in a preset test case, and locating the static method chaining corresponding to the flown method chaining in the displayed different static method chaining and using same as a tested method chaining; and distinguishing and identifying the tested method chaining in the displayed different static method chaining and other untested static method chaining to display the test execution effect of the test case to a user. The present application achieves virtual display of the test case execution effect.

Description

Test effect display method, electronic device and storage medium of test case

Priority claim

The present application is based on the priority of the Chinese Patent Application entitled "Test Case Display Method, Electronic Device and Storage Medium", filed on April 17, 2018, with the application number CN 2018103450304, which is filed on April 17, 2018. The entire content is incorporated herein by reference.

Technical field

The present application relates to the field of computer technology, and in particular, to a test effect display method, an electronic device, and a readable storage medium for a test case.

Background technique

When testing a test system with a test case, it is sometimes necessary to test the dynamic link of the system to be tested. The dynamic link refers to a method chain and the like that are passed through a dynamic process in which a system to be tested initiates an http request to a web server. In the existing test solution, the user can only know the current method chain of the test case when performing the dynamic link test on the test system, and cannot let the user know the method chain hierarchy in the system to be tested, and the user cannot determine. The other method chains in the system to be tested are not executed, that is, the user cannot completely measure the execution effect when using the test case to test the test system.

Summary of the invention

The purpose of the present application is to provide a test case display method, an electronic device, and a readable storage medium, which are intended to fully display to a user the execution effect when using a test case to test a test system.

In order to achieve the above object, a first aspect of the present application provides an electronic device, where the electronic device includes a memory and a processor, and the memory stores a test effect display system of a test case executable on the processor. The test effect of the test case shows that the system is implemented by the processor to implement the following steps:

The code of the test system is analyzed, and a static call structure between each method in the system code to be tested is obtained, and each static method chain in the system code to be tested is established according to the static call structure;

Displaying each static method chain according to the static call structure according to a preset display rule;

Recording a method chain that the test case flows during dynamic link test execution during a dynamic test of the system to be tested in a preset test case, and finding and analyzing each static method chain displayed The static method chain corresponding to the method chain flowing through as the tested method chain;

The tested method chain and other untested static method chains in each static method chain displayed are differentiated to display the test execution effect of the test case to the user.

In addition, in order to achieve the above object, the second aspect of the present application further provides a test effect display method for a test case, and the test effect display method of the test case includes:

Further, in order to achieve the above object, a third aspect of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a test effect display system of a test case, and the test effect display system of the test case can be Executed by at least one processor to cause the at least one processor to perform the steps of the test effect presentation method of the test case as described above.

The test effect display method, system and readable storage medium of the test case proposed by the present application, by analyzing the code of the test system, obtaining a static call structure between each method in the system code to be tested, and according to the static call structure Establishing each static method chain in the system code to be tested; displaying each static method chain according to the static call structure; recording the test case when performing a dynamic link test on the system to be tested in a preset test case The method chain that flows through the dynamic link test execution process, and distinguishes between the method chain and other untested static method chains that are displayed in the dynamic link test execution process in each static method chain. To show the test results of the test case to the user. Since each static method chain of the system to be tested can be displayed in a static call structure, the user can intuitively know the method chain hierarchy in the system to be tested, and by testing in each static method chain displayed by the static call structure. In the case of the dynamic link test execution process, the method chain and other method chains are differentiated and identified, and the user can intuitively know the method chain of the currently executed test in the system to be tested and the method chain that has not yet executed the test, thereby realizing A visual demonstration of the performance of the test case, allowing the user to fully measure the performance of the test case when testing the test system.

DRAWINGS

1 is a schematic diagram of an operating environment of a preferred embodiment of a test effect display system 10 of a test case of the present application;

FIG. 2 is a schematic flowchart diagram of an embodiment of a test effect display method of a test case of the present application.

detailed description

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

It should be noted that the descriptions of "first", "second" and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. . Thus, features defining "first" or "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.

The application provides a test effect display system for a test case. Please refer to FIG. 1 , which is a schematic diagram of an operating environment of a preferred embodiment of the test effect display system 10 of the test case of the present application.

In the embodiment, the test effect display system 10 of the test case is installed and operated in the electronic device 1. The electronic device 1 may include, but is not limited to, a memory 11, a processor 12, and a display 13. Figure 1 shows only the electronic device 1 with components 11-13, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.

The memory 11 is at least one type of readable computer storage medium, which in some embodiments may be an internal storage unit of the electronic device 1, such as a hard disk or memory of the electronic device 1. The memory 11 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in hard disk equipped on the electronic device 1, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 is configured to store application software and various types of data installed in the electronic device 1, such as program code of the test effect display system 10 of the test case. The memory 11 can also be used to temporarily store data that has been output or is about to be output.

The processor 12, in some embodiments, may be a central processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 11, for example The test effect display system 10 and the like of the test case are executed.

The display 13 in some embodiments may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like. The display 13 is configured to display information processed in the electronic device 1 and a user interface for displaying visualization, such as each static method chain in the system to be tested displayed in a static call structure, on the tested method chain, and not The static method chain of the test is used to distinguish the display interface after the identification. The components 11-13 of the electronic device 1 communicate with one another via a system bus.

The test effect display system 10 of the test case includes at least one computer readable instruction stored in the memory 11, the at least one computer readable instruction being executable by the processor 12 to implement various embodiments of the present application.

Wherein, the test effect display system 10 of the above test case is implemented by the processor 12 to implement the following steps:

Step S1: analyzing the code of the system to be tested, obtaining a static call structure between each method in the system code to be tested, and establishing each static method chain in the system code to be tested according to the static call structure.

Using the Java bytecode framework ASM package to analyze the class file of the test system code, analyze the static call structure between the various methods in the system code to be tested; and use the static call structure of the analysis to obtain the static of the system code to be tested. Method chain. Among them, ASM is a java bytecode manipulation framework, which can be used to dynamically generate classes or enhance the functionality of existing classes. Java classes are stored in .class files defined by strict formats. These class files have enough metadata to resolve all the elements in the class: class names, methods, properties, and Java bytecode (instructions). After reading the information from the class file, ASM can analyze the class information and parse the compiled class bytecode file. For example, the Asm package can be used to perform line-by-line analysis of the test system code, and obtain the calling relationship of each method between different classes in the system code to be tested. For example, each method in a class has a corresponding code block, and the calling relationship (ie, the calling structure) between the corresponding methods can be obtained according to the calling relationship between the code blocks. Further, the method chain is a combination of a plurality of methods having a calling relationship. According to the calling structure between each method in a class, a plurality of method chains in a class combined by a plurality of methods having a calling relationship may be obtained. As a static method chain.

Step S2, displaying each static method chain according to the static display structure according to a preset display rule.

In this embodiment, the static call structure of the analysis and the obtained static method chains of the system code to be tested are visually displayed according to preset display rules. For example, a method call structure tree with a master node and a child node may be constructed according to a static call structure between each method in the system code to be tested, and the corresponding tree structure division rule is: different classes for the system code to be tested, such as different functions. Modules are set to corresponding master nodes; each master node, ie, several methods under each class, sequentially form child nodes of each level according to the static call structure between the methods; wherein, the method calls a method of calling relationships in the structure tree Synthesize static method chains.

Step S3, when performing a dynamic link test on the system to be tested in a preset test case, recording a method chain that the test case flows through during the execution of the dynamic link test, and displaying each static method chain The static method chain corresponding to the method chain flowing through is found as the tested method chain.

Step S4, distinguishing between the tested method chain and other untested static method chains in each static method chain that is displayed, so as to display the test execution effect of the test case to the user.

In this embodiment, when testing a test system using a test case, it is sometimes necessary to test the dynamic link of the system to be tested. The dynamic link refers to a method chain that passes through a dynamic process in which a system to be tested initiates an http request to a web server. Record the method chain that the test case flows through during the execution of the dynamic link test, and find the static method chain corresponding to the method chain flowing through in the static call structure and the static method chain of the system code to be tested. The static method chain corresponding to the method chain flowing through is distinguished from other static method chains in each static method chain of the system code to be tested (eg, different colors are respectively labeled, highlighted, marked, etc.). For example, in each static method chain of the system code to be tested displayed in the method call structure tree, the static method chain corresponding to the method chain through which the dynamic link of the system to be tested is tested is lit or green. The annotation display is displayed, and the other static method chains displayed in the method call structure tree are not lit or marked in red. In this way, the user can intuitively know the effect of the test case execution by calling the structure tree through the displayed method, by distinguishing the static method chain corresponding to the method chain flowing through the displayed system to be tested and the static call structure of the entire system to be tested. The user can intuitively know the currently executed method chain and the method chain that has not been executed, so as to realize the visual display case execution effect, so that the user can statically call the structure and dynamic link test between the methods in the system code to be tested. These two aspects are a complete measure of the effectiveness of test case execution.

In this embodiment, the static call structure between the methods in the system code to be tested is obtained by analyzing the code of the system to be tested, and each static method chain in the system code to be tested is established according to the static call structure; each static method is The chain is displayed according to the static call structure; when the dynamic test of the system to be tested is performed on the preset test case, the method chain that the test case flows during the execution of the dynamic link test is recorded, and The method chain and other untested static method chains flowing in the dynamic link test execution process in each static method chain are displayed to distinguish the test results of the test cases to the user. Since each static method chain of the system to be tested can be displayed in a static call structure, the user can intuitively know the method chain hierarchy in the system to be tested, and by testing in each static method chain displayed by the static call structure. In the case of the dynamic link test execution process, the method chain and other method chains are differentiated and identified, and the user can intuitively know the method chain of the currently executed test in the system to be tested and the method chain that has not yet executed the test, thereby realizing A visual demonstration of the performance of the test case, allowing the user to fully measure the performance of the test case when testing the test system.

In an optional embodiment, on the basis of the foregoing embodiment of FIG. 1, when the test effect display system 10 of the test case is executed by the processor 12 to implement the step S2, the method specifically includes:

Using the Graphviz package, each static method chain is drawn according to the static call structure to generate a scalable vector graphic for visual display.

In this embodiment, when the static call structure and the static method chain corresponding to the method chain flowing through are displayed, the Graphviz package can be used to generate svg for visual display. Among them, Graphviz is an open source graphics rendering tool developed by AT&T Labs Research. It uses a specific DSL (domain specific language): dot as the scripting language, then uses the layout engine to parse the script and complete the automatic layout. It can be easily used to draw a structured graphical network. Graphviz provides a rich export format, such as commonly used image formats, SVG, PDF and so on. In this embodiment, graphviz is used to draw and display a static call structure, which can effectively ensure the quality and speed of the generated image. And the final display format in this embodiment adopts svg (scalable vector graphics) format, Internet Explorer 9, Firefox, Google Chrome, Opera and Safari all support SVG, so it is more convenient for users to open static display of viewing display through web browser. The structure and the static method chain corresponding to the method chain flowing through it flexibly display the effect of the case visualization for the user and are more practical.

In an optional embodiment, when the test effect display system 10 of the test case is executed by the processor 12 to implement the step S3, the method includes:

Configure the Java bytecode toolkit as a javassist or Java proxy. Javassist is an open source java bytecode manipulation tool that mainly modifies and processes the compiled class files. In this embodiment, the javassist toolkit is first configured as a javaagent proxy. When the web (website) server is started, the javaagent agent is used to intercept the class file before loading or loading the software system to be tested, and the bytecode is modified. Enhance the method (chain) in the software system code to be recorded in order to record information about the method (chain) (such as name, number, etc.); and enhance the filter of the software system to be tested to capture information related to the http request. . For example, during the execution of the test case, the http request entering the software system under test can be recorded, and the method (chain) through which the http request to the test software system passes is saved. The test cases in this case include interface test cases, WEB (web) test cases, and so on. The test case can be a personalized test case written in a targeted manner, or it can be a common test case.

In an optional embodiment, when the test effect display system 10 of the test case is executed by the processor 12, the following steps are also implemented:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.

In this embodiment, the prompt information may be sent to the user for the test result in the display interface. For example, if there is no bug in the method chain test flowing through, the red identifier may be turned into a green logo or a highlight reminder, or sent to the user. SMS and other warnings. Otherwise, stay red. Users can more intuitively know the test results of the corresponding method chain when each test case is executed.

When there is a code change, for example, when a certain type (such as a function module) in the system code to be tested changes, the test system needs to be tested by the test case, if the test case flows through the dynamic link test execution process. The static method chain corresponding to the method chain is displayed in the method call structure tree (such as the red mark), and further, the static method chain that has not been tested by the test case in the class may be identified ( For example, the standard yellow), for the user to select the corresponding test case for the static method chain of the standard yellow for targeted testing. In this way, the user can clarify the case execution process and the case omission process to improve the test results of the test system when the code changes.

As shown in FIG. 2, FIG. 2 is a schematic flowchart of an embodiment of a test effect display method of a test case of the present application. The test effect display method of the test case includes the following steps:

Step S10, analyzing the code of the system to be tested, obtaining a static call structure between each method in the system code to be tested, and establishing each static method chain in the system code to be tested according to the static call structure.

Step S20, displaying each static method chain according to the static display structure according to a preset display rule.

Step S30, when performing a dynamic link test on the system to be tested in a preset test case, recording a method chain that the test case flows during the execution of the dynamic link test, and displaying each static method chain The static method chain corresponding to the method chain flowing through is found as the tested method chain.

Step S40: Perform a differentiated identification on the tested method chain and other untested static method chains in each static method chain that is displayed, so as to display the test execution effect of the test case to the user.

In an optional embodiment, based on the foregoing embodiment, the step S20 includes:

In an optional embodiment, the step S30 includes:

In an optional embodiment, the method further includes:

In addition, the present application further provides a computer readable storage medium storing a test effect display system of a test case, the test effect display system of the test case being executable by at least one processor, so that The at least one processor performs the steps of the test effect display method of the test case in the above embodiment, and the specific implementation processes of the steps S10, S20, and S30 of the test effect display method of the test case are as described above, and Let me repeat.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and can also be implemented by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

The preferred embodiments of the present application have been described above with reference to the drawings, and are not intended to limit the scope of the application. The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments. Additionally, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

A person skilled in the art can implement the present application in various variants without departing from the scope and spirit of the present application. For example, the features as one embodiment can be used in another embodiment to obtain another embodiment. Any modifications, equivalent substitutions and improvements made within the technical concept of the application should be within the scope of the application.

Claims

An electronic device, comprising: a memory, a processor, wherein the memory stores a test effect display system of a test case executable on the processor, and the test effect of the test case is displayed The system implements the following steps when executed by the processor:

The code of the test system is analyzed, and a static call structure between each method in the system code to be tested is obtained, and each static method chain in the system code to be tested is established according to the static call structure;

Displaying each static method chain according to the static call structure according to a preset display rule;

Recording a method chain that the test case flows during dynamic link test execution during a dynamic test of the system to be tested in a preset test case, and finding and analyzing each static method chain displayed The static method chain corresponding to the method chain flowing through as the tested method chain;

The tested method chain and other untested static method chains in each static method chain displayed are differentiated to display the test execution effect of the test case to the user.
The electronic device according to claim 1, wherein the code of the system to be tested is analyzed, a static call structure between each method in the system code to be tested is obtained, and a system to be tested is established according to the static call structure. The steps of each static method chain in the code include:

Using the Java bytecode framework ASM package to analyze the class file of the test system code line by line, and obtain the calling relationship of each method in each class of the system code to be tested as a static call structure;

A method chain that combines several methods with calling relationships in a class is used as a static method chain.
The electronic device according to claim 2, wherein the step of displaying each static method chain according to the static display structure based on a preset presentation rule comprises:

Using the Graphviz package, each static method chain is drawn according to the static call structure to generate a scalable vector graphic for visual display.
The electronic device according to claim 1, wherein when the dynamic test of the system to be tested is performed on a preset test case, the test case is recorded during the execution of the dynamic link test. The steps of the method chain include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The electronic device according to claim 2, wherein when the dynamic test of the system to be tested is performed on a preset test case, the test case is recorded during the execution of the dynamic link test. The steps of the method chain include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The electronic device according to claim 3, wherein when the predetermined test case performs a dynamic link test on the system to be tested, the test case is recorded during the execution of the dynamic link test The steps of the method chain include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The electronic device according to claim 1, wherein the processor is further configured to execute a test effect display system of the test case to implement the following steps:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
The electronic device according to claim 2, wherein the processor is further configured to execute a test effect display system of the test case to implement the following steps:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
The electronic device according to claim 3, wherein the processor is further configured to execute a test effect display system of the test case to implement the following steps:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
A test result display method for a test case, characterized in that the test effect display method of the test case includes:

The code of the test system is analyzed, and a static call structure between each method in the system code to be tested is obtained, and each static method chain in the system code to be tested is established according to the static call structure;

Displaying each static method chain according to the static call structure according to a preset display rule;

Recording a method chain that the test case flows during dynamic link test execution during a dynamic test of the system to be tested in a preset test case, and finding and analyzing each static method chain displayed The static method chain corresponding to the method chain flowing through as the tested method chain;

The tested method chain and other untested static method chains in each static method chain displayed are differentiated to display the test execution effect of the test case to the user.
The test effect display method of the test case according to claim 10, wherein the code of the system to be tested is analyzed, and a static call structure between each method in the system code to be tested is obtained, and according to the static call The steps of constructing each static method chain in the system code to be tested include:

Using the Java bytecode framework ASM package to analyze the class file of the test system code line by line, and obtain the calling relationship of each method in each class of the system code to be tested as a static call structure;

A method chain that combines several methods with calling relationships in a class is used as a static method chain.
The test effect display method of the test case according to claim 11, wherein the step of displaying each static method chain according to the static display structure based on the preset display rule comprises:

Using the Graphviz package, each static method chain is drawn according to the static call structure to generate a scalable vector graphic for visual display.
The test effect display method of the test case according to claim 10, wherein the test case is recorded in a dynamic link test when a dynamic test of the system to be tested is performed on a preset test case. The steps of the method chain flowing through the execution process include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The test effect display method of the test case according to claim 11, wherein the test case is recorded in a dynamic link test when a dynamic test of the system to be tested is performed on a preset test case. The steps of the method chain flowing through the execution process include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The test effect display method of the test case according to claim 12, wherein the test case is recorded in a dynamic link test when a dynamic test of the system to be tested is performed on a preset test case. The steps of the method chain flowing through the execution process include:

Configuring a Java bytecode tool as a Java proxy, starting in a preset web server, and performing a dynamic link test on the software system to be tested by using a preset test case, using the Java proxy to the software system to be tested The filter is enhanced to capture an HTTP request entering the software system under test and utilize the Java proxy to record the method chain through which the HTTP request to the software system under test passes.
The test effect display method of the test case according to claim 10, further comprising:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
The test effect display method of the test case according to claim 11, further comprising:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
The test effect display method of the test case according to claim 12, further comprising:

When the test case has a test abnormality in the method chain flowing through the dynamic link test execution process, the method chain in which the test abnormality appears in each static method chain is marked according to a preset abnormal identifier manner, so as to be displayed to the user. Shows a method chain with test exceptions.
A computer readable storage medium, wherein the computer readable storage medium stores a test effect display system of a test case, and the test effect display system of the test case is executed by the processor to implement the following steps:

The code of the test system is analyzed, and a static call structure between each method in the system code to be tested is obtained, and each static method chain in the system code to be tested is established according to the static call structure;

Displaying each static method chain according to the static call structure according to a preset display rule;

Recording a method chain that the test case flows during dynamic link test execution during a dynamic test of the system to be tested in a preset test case, and finding and analyzing each static method chain displayed The static method chain corresponding to the method chain flowing through as the tested method chain;

The tested method chain and other untested static method chains in each static method chain displayed are differentiated to display the test execution effect of the test case to the user.
The computer readable storage medium according to claim 19, wherein the code of the system to be tested is analyzed to obtain a static call structure between each method in the system code to be tested, and is established according to the static call structure. The steps of each static method chain in the system code to be tested include:

Using the Java bytecode framework ASM package to analyze the class file of the test system code line by line, and obtain the calling relationship of each method in each class of the system code to be tested as a static call structure;

A method chain that combines several methods with calling relationships in a class is used as a static method chain.