CN112527587B - Verification progress determining method, device, equipment and readable storage medium - Google Patents

Abstract

The application discloses a verification progress determining method, a verification progress determining device, verification progress determining equipment and a readable storage medium. The method disclosed by the application comprises the following steps: acquiring verification plan data and functional coverage data corresponding to the verification plan data; associating the verification plan data with the functional coverage data to determine an entity hierarchy path of a coverage group or coverage point, and generating a functional coverage class file and an initial verification plan comprising the entity hierarchy path; analyzing the initial verification plan and the function coverage class file by using a test tool to obtain an operation result and function coverage information corresponding to each test case; and inputting the function coverage information, the initial verification plan and each operation result into a denoiser to output a verification progress marking result. According to the method and the device, the entity hierarchical path and the function coverage type file can be automatically determined, so that the verification progress can be efficiently and automatically determined. Accordingly, the verification progress determining device, the verification progress determining equipment and the readable storage medium provided by the application also have the technical effects.

Description

A verification progress determination method, device, equipment and readable storage medium

technical field

The present application relates to the technical field of chip logic function verification, and in particular to a verification progress determination method, device, equipment and readable storage medium.

Background technique

At present, in the verification process of chip logic functions, the verification process can be marked with the HVP Annotator, so as to track the overall progress of the verification. However, before using the anti-annotator to mark the verification process, the verifier needs to manually specify the entity-level path of the coverage group (covergroup) or coverage point (coverpoint) in the test platform (testbench), and also needs to manually write the calculation function coverage. Rate (function coverage) of the functional coverage code.

Usually, the verification progress is tracked based on the HVP (Hierarchical Verification Plan) tool, so the verification personnel also need to master the HVP language, and the corresponding editing software is also difficult to use. As a result, the production cycle of entity-level paths and functional coverage codes will become longer, making it difficult to track the verification progress in time, and it will also slow down the verification progress and cost more.

Therefore, how to efficiently determine the verification progress is a problem to be solved by those skilled in the art.

Contents of the invention

In view of this, the purpose of the present application is to provide a method, device, device and readable storage medium for determining the verification progress, so as to efficiently determine the verification progress. The specific plan is as follows:

In the first aspect, the present application provides a verification progress determination method, including:

Acquiring verification plan data and functional coverage data corresponding to the verification plan data;

Wherein, the verification plan data includes: coverage groups or coverage points that need to be verified, test features, test cases and test scores corresponding to the coverage groups or coverage points; the functional coverage data includes: the coverage groups or The class corresponding to the coverage point, the coverage group or coverage point corresponding to the test score;

associating the verification plan data with the functional coverage data to determine the physical hierarchy path of the coverage group or the coverage point, and generate a functional coverage class file and an initial verification plan including the physical hierarchy path;

Analyzing the initial verification plan and the functional coverage class file by using a test tool to obtain the running results and functional coverage information corresponding to each test case;

Inputting the functional coverage information, the initial verification plan and each running result into the de-marker, so as to output a verification progress marking result.

Preferably, said obtaining the verification plan data and the corresponding functional coverage data of the verification plan data include:

extracting said verification plan data from a verification plan template;

extracting said functional coverage data from a functional coverage template;

Wherein, the verification plan data is input by the user into the verification plan template, and the function coverage data is input by the user into the function coverage template.

Preferably, said associating said verification plan data with said functional coverage data to determine the entity-level path of said coverage group or said coverage point comprises:

Associating the verification plan data with the functional coverage data according to the class file, and determining the entity hierarchy path based on the functional coverage data.

Preferably, the initial verification plan is an hvp file.

Preferably, the testing tool is a simulation tool supporting SystemVerilog.

Preferably, before inputting the function coverage information, the initial verification plan and each operation result into the de-marker to output the verification progress marking result, it also includes:

Generate a hud file including the results of each run.

Preferably, it also includes:

Visually display the verification progress marking results.

In a second aspect, the present application provides a verification progress determination device, including:

An acquisition module, configured to acquire verification plan data and functional coverage data corresponding to the verification plan data; wherein, the verification plan data includes: coverage groups or coverage points that need to be verified, and the coverage groups or coverage points correspond to Test features, test cases, and test scores; the functional coverage data includes: the coverage group or coverage point corresponding to the class, the test score corresponding coverage group and coverage point;

An association module, configured to associate the verification plan data with the functional coverage data to determine the coverage group or the entity-level path of the coverage point, and generate a functional coverage class file and an initial verification including the entity-level path plan;

A parsing module, configured to parse the initial verification plan and the functional coverage class file using a test tool to obtain the corresponding running results and functional coverage information of each test case;

The marking module is configured to input the function coverage information, the initial verification plan and each running result into the de-marker, so as to output a verification progress marking result.

In a third aspect, the present application provides a verification progress determination device, including:

memory for storing computer programs;

A processor, configured to execute the computer program, so as to realize the verification progress determination method disclosed above.

In a fourth aspect, the present application provides a readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the method for determining the verification progress disclosed above is realized.

It can be known from the above solution that the present application provides a verification progress determination method, including: obtaining verification plan data and functional coverage data corresponding to the verification plan data; wherein, the verification plan data includes: coverage groups that need to be verified or Coverage points, test features, test cases and test scores corresponding to the coverage groups or coverage points; the functional coverage data includes: the coverage groups or classes corresponding to the coverage points, the coverage groups or test scores corresponding to the test scores Coverage point; associating the verification plan data with the functional coverage data to determine the coverage group or the physical hierarchy path of the coverage point, and generate a functional coverage class file and an initial verification plan including the physical hierarchy path; Utilize the test tool to analyze the initial verification plan and the function coverage class file to obtain the corresponding operation results and function coverage information of each test case; input the function coverage information, the initial verification plan and each operation result into the reverse label The device will output the result of the verification progress.

It can be seen that this application automatically obtains verification plan data and functional coverage data, and correlates verification plan data and functional coverage data, so as to determine the entity-level path of coverage groups or coverage points, and generate functional coverage files and initial verification including test paths plan; then use the test tool to analyze the initial verification plan and functional coverage class files to obtain the corresponding running results of each test case and functional coverage information (that is: the data required to calculate the functional coverage); finally, the functional coverage information, initial verification The plan and each operation result are input into the anti-marker, so that the verification progress marking result can be output. Among them, both the verification plan data and the functional coverage data include: test scores and corresponding coverage groups or coverage points; and the functional coverage data includes the classes corresponding to the coverage groups or coverage points, so a certain coverage group or coverage point can be determined accordingly in the class. At the same time, based on the verification plan data, the coverage groups or coverage points that need to be verified, the test features, test cases and test scores corresponding to the coverage groups or coverage points can be seen, so the initial verification plan can be generated accordingly. The function coverage class file is a statement. To use it in the test platform, the class needs to be instantiated. The test platform can determine where the class that needs to be instantiated is located in the test platform based on the entity hierarchy path.

This application can automatically generate the initial verification plan, automatically determine the entity-level path and function coverage class file of the coverage group or coverage point, so as to automatically determine the verification progress, without the need for the verification personnel to manually specify the entity-level path and manually write the function coverage code, so It can reduce the production cycle and cost of entity-level paths and functional coverage codes, track and improve the efficiency of determining the verification progress in time, and realize the efficient determination of the verification progress.

Correspondingly, the verification progress determination device, equipment and readable storage medium provided by the present application also have the above-mentioned technical effects.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present application, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a flowchart of a verification progress determination method disclosed in the present application;

Fig. 2 is a schematic diagram of a verification plan template disclosed in the present application;

FIG. 3 is a schematic diagram of a functional coverage template disclosed in the present application;

Fig. 4 is a schematic diagram of a verification progress determination scheme disclosed in the present application;

FIG. 5 is a schematic diagram of a verification progress determination device disclosed in the present application;

Fig. 6 is a schematic diagram of a verification progress determination device disclosed in the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some of the embodiments of the application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

At present, the production cycle of entity-level paths and functional coverage codes will become longer, making it difficult to track the verification progress in time, and it will also slow down the verification progress and cost more. For this reason, the present application provides a verification progress determination scheme, which can efficiently determine the verification progress.

Referring to Figure 1, the embodiment of the present application discloses a verification progress determination method, including:

S101. Obtain verification plan data and functional coverage data corresponding to the verification plan data;

Among them, the verification plan data includes: coverage groups or coverage points to be verified, test features, test cases, and test scores corresponding to coverage groups or coverage points; functional coverage data includes: classes corresponding to coverage groups or coverage points, and test scores corresponding to Coverage groups or coverage points. Coverage groups or coverage points include the function points to be tested.

In a specific implementation manner, obtaining the verification plan data and the corresponding functional coverage data of the verification plan data includes: extracting the verification plan data from the verification plan template; extracting the function coverage data from the function coverage template; wherein, the verification plan data User-entered into the Verification Plan Template, functional coverage data is user-entered into the Functional Coverage Template. The verification plan template (as shown in Figure 2) and the function coverage template (as shown in Figure 3) are user-defined, and the specific data therein are filled in by the user.

In Figure 2, feature is the function point. In Figure 2, you need to fill in: feature, sub-feature of feature, name of sub-feature, description of feature (description), owner (owner), priority information (prio), test score (measure grp.source), test case ( measure test status. source), etc. Among them, the grp.source item only needs to be filled in with the format of class (representing the class name, such as focv1). covergroup (representing the coverage group name, such as cg1) [.coverpoint (representing the coverage point name, such as cp1) [.bin]]. Indicates which coverage group or coverage point the current feature or sub-feature belongs to. Namely: "focv1" is the name of a class. "cg1" is the name of a certain covergroup. "cp1" is the name of a certain coverpoint.

Among them, "[]" means optional, the items inside "[]" are optional, and the items outside "[]" are required. The first "focv1, cg1" of the grp.source item in Figure 2 does not have "[]", while the third "focv1, cg1, cp1" of the grp.source item in Figure 2 has "[]", [.cp1] is filled in "[]".

Verifiers do not need to know the entity-level path of the coverage group or coverage point in the entire test platform. The specific definition of class.covergroup[.coverpoint[.bin]] is shown in Figure 3.

In Figure 3, you need to fill in: the definition of the class to which the variable belongs (Instance), Parameter (variable, refers to a coverage group or coverage point), class naming, the name of the coverage group (Covergroup), the name of the coverage point (Covergroup Label), variable Constraint statement (Constraint Value), and key information (Tag) that may indicate the constraint, etc.

S102. Associating the verification plan data with the functional coverage data to determine the entity-level path of the coverage group or coverage point, and generate a functional coverage class file and an initial verification plan including the entity-level path.

In a specific embodiment, associating the verification plan data with the functional coverage data to determine the entity hierarchy path of the coverage group or coverage point includes: associating the verification plan data with the functional coverage data according to the class file, and determining the entity based on the functional coverage data hierarchical path. The entity hierarchy path refers to the path where the class entities representing coverage groups or coverage points are located in the test platform.

Wherein, both the verification plan data and the functional coverage data include: test scores and corresponding coverage groups or coverage points, based on which the test scores of the same coverage group or coverage points can be determined. The functional coverage data includes the class corresponding to the coverage group or coverage point, so the class of a certain coverage group or coverage point can be determined accordingly. At the same time, based on the verification plan data, the coverage groups or coverage points that need to be verified, the test features, test cases and test scores corresponding to the coverage groups or coverage points can be seen, so the initial verification plan can be generated accordingly.

In a specific implementation manner, the initial verification plan is an hvp file.

S103 , using the test tool to analyze the initial verification plan and the functional coverage class file, so as to obtain the running results and functional coverage information corresponding to each test case.

The function coverage class file is a statement. To use it in the test platform, the class needs to be instantiated. The test platform can determine where the class that needs to be instantiated is located in the test platform based on the entity hierarchy path.

In a specific implementation manner, the testing tool is a simulation tool supporting SystemVerilog, such as VCS.

S104. Input the function coverage information, the initial verification plan and each operation result into the anti-marker, so as to output a verification progress marking result.

In a specific implementation, before inputting the function coverage information, the initial verification plan and each running result into the anti-marker to output the verification progress marking result, it also includes: generating a hud file including each running result, that is, generating a .hud file suffix for text files to suit the HVP tool.

In a specific implementation manner, the verification progress marking result is displayed visually, and the overall progress of the current verification can be tracked by viewing the verification progress marking result, so as to ensure the orderly progress and correction of the entire verification project. Among them, you can use Verdi or DVE to view, and you can also use Excel to view. Verdi or DVE can edit and manipulate HVP files.

It can be seen that this embodiment can automatically generate the initial verification plan, automatically determine the entity-level path and function coverage class file of the coverage group or coverage point, thereby automatically determining the verification progress, without the verification personnel manually specifying the entity-level path, and without manually writing the function coverage Therefore, it can reduce the production cycle and cost of entity-level paths and functional coverage codes, track and improve the efficiency of determining the verification progress in time, and realize the efficient determination of the verification progress.

Referring to Figure 4, the embodiment of the present application discloses a verification schedule determination scheme, which is designed based on the HVP tool, realizes the automatic generation of the initial verification plan, and can automatically determine the entity-level path and function of the coverage group or coverage point Overwrite the class file, and then use the anti-marker to determine the verification progress, effectively tracking the entire process of verification.

First, customize the HVP Excel template. HVP Excel templates include: verification plan template and functional coverage template (as shown in Figure 2 and Figure 3). The user fills in the template with relevant information required by the template.

Run the xhvp tool to process the completed template above to achieve: obtain the verification plan data from the completed template above, and the functional coverage data corresponding to the verification plan data; correlate the verification plan data with the functional coverage data to determine the coverage Entity-level paths for groups or coverage points, and generate functional coverage class files (described in System Verilog language to adapt to HVP tools) and initial verification plans including entity-level paths (such as hvp files to adapt to HVP tools); utilize test tools (such as VCS) parse the initial verification plan and functional coverage class files to obtain the corresponding running results (such as .hud files) and functional coverage information of each test case; input the functional coverage information, initial verification plan and each running result into the reverse labeler , to indicate the result by outputting the verification progress. Wherein, the method provided by this application is implemented in the xhvp tool, and the xhvp tool may be a script implemented in languages such as perl, C/C++ or python.

xhvp will parse the information of each row and column corresponding to the plan page and fcov page in the HVP Excel template (as shown in Figure 2 and Figure 3), and correlate them, so as to output the function coverage class file and the initial verification plan. At the same time, the xhvp tool obtains the running results and functional coverage information corresponding to each test case output by VCS, and inputs the functional coverage information, initial verification plan and .hud file into the anti-marker to output the verification progress marking results. The running results corresponding to each test case are output by VCS, and the xhvp tool extracts the output into an easy-to-use .hud file.

Wherein, the function coverage class file is automatically integrated into the test platform, so that the test platform instantiates the function coverage class file (which can be realized by calling the sample method in the function coverage class file). At this point, the coverage group or coverage point is a variable, and the coverage group or coverage point is encapsulated into a class file, so calling the corresponding class file can trigger the collection of the coverage group or coverage point, no need to write code.

In this embodiment, we define an HVP Excel template that is easy for the verification personnel to understand and fill in. The verification personnel do not need to understand the HVP language, nor do they need to care about the entity hierarchy path of the class corresponding to the coverage group or coverage point in the test platform, nor do they need to write Functional coverage code, which is automatically generated by the tool xhvp. In addition, external user data (that is, the running results corresponding to each test case) is also automatically extracted through the xhvp tool in this process to generate a text file.

This embodiment realizes the automatic generation of verification plan and function coverage. In this process, the user only needs to fill in the HVPExcel template, which avoids errors and debugging time that may be introduced by manual code writing, and also improves the efficiency of verification review, and is not easy to miss possible key points, thus speeding up the project verification progress.

A device for determining a verification progress provided in an embodiment of the present application is introduced below. The device for determining a verification progress described below and the method for determining a verification progress described above may refer to each other.

Referring to Figure 5, the embodiment of the present application discloses a verification progress determination device, including:

The acquisition module 501 is configured to acquire verification plan data and functional coverage data corresponding to the verification plan data; wherein, the verification plan data includes: coverage groups or coverage points that need to be verified, test features corresponding to the coverage groups or coverage points, test cases and Test scores; functional coverage data include: classes corresponding to coverage groups or coverage points, coverage groups and coverage points corresponding to test scores;

The association module 502 is used for associating the verification plan data with the functional coverage data, so as to determine the physical hierarchy path of the coverage group or coverage point, and generate the functional coverage class file and the initial verification plan including the physical hierarchy path;

The analysis module 503 is used to analyze the initial verification plan and the functional coverage class file by using the test tool, so as to obtain the operation results and functional coverage information corresponding to each test case;

The marking module 504 is configured to input the function coverage information, the initial verification plan and each running result into the de-marker, so as to output the verification progress marking result.

In a specific implementation manner, the acquisition module is specifically used for:

The verification plan data is extracted from the verification plan template; the function coverage data is extracted from the function coverage template; wherein, the verification plan data is input by the user into the verification plan template, and the function coverage data is input by the user into the function coverage template.

In a specific implementation manner, the association module is specifically used for:

Associating the verification plan data with the functional coverage data according to the class file, and determining the entity hierarchy path based on the functional coverage data.

In a specific implementation manner, the initial verification plan is an hvp file.

In a specific implementation manner, the test tool is a simulation tool supporting SystemVerilog.

In a specific embodiment, it also includes:

The generation module is used to generate the hud file including each running result.

In a specific embodiment, it also includes:

The display module is used to visually display the results of verification progress marking.

For the more specific working process of each module and unit in this embodiment, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

It can be seen that this embodiment provides a verification progress determination device, which can automatically generate an initial verification plan, automatically determine the entity-level path and function coverage class file of a coverage group or coverage point, thereby automatically determining the verification progress without manual verification by the verification personnel. Specifying entity-level paths eliminates the need to manually write functional coverage codes. Therefore, the production cycle and cost of entity-level paths and functional coverage codes can be reduced, and the efficiency of verification progress can be tracked in a timely manner to improve the efficiency of verification progress.

The following is an introduction to a device for determining a verification progress provided in an embodiment of the present application. The device for determining a verification progress described below and the method and device for determining a verification progress described above may refer to each other.

Referring to Figure 6, the embodiment of the present application discloses a verification progress determination device, including:

Memory 601, used to store computer programs;

The processor 602 is configured to execute the computer program, so as to implement the method disclosed in any of the foregoing embodiments.

A readable storage medium provided by an embodiment of the present application is introduced below. The readable storage medium described below and the verification progress determination method, device, and equipment described above may refer to each other.

A readable storage medium is used to store a computer program, wherein when the computer program is executed by a processor, the method for determining the verification progress disclosed in the foregoing embodiments is implemented. Regarding the specific steps of the method, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

"First", "second", "third", "fourth" and the like referred to in the present application, if any, are used to distinguish similar objects and not necessarily to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, e.g. a process, method or apparatus comprising a series of steps or elements is not necessarily limited to those steps or elements explicitly listed , but may include other steps or elements not explicitly listed or inherent to the process, method or apparatus.

It should be noted that the descriptions in this application involving "first", "second" and so on are for descriptive purposes only, 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 application.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known readable storage medium.

In this paper, specific examples are used to illustrate the principles and implementation methods of the application. The descriptions of the above embodiments are only used to help understand the method and core idea of the application; meanwhile, for those of ordinary skill in the art, according to the application There will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be construed as limiting the application.

Claims (8)

1. A verification progress determination method, characterized in that, comprising: Acquiring verification plan data and functional coverage data corresponding to the verification plan data; Wherein, the verification plan data includes: coverage groups or coverage points that need to be verified, test features, test cases and test scores corresponding to the coverage groups or coverage points; the functional coverage data includes: the coverage groups or The class corresponding to the coverage point, the coverage group or coverage point corresponding to the test score; the coverage group or the coverage point is a variable, and the coverage group or the coverage point is encapsulated into a class file, and the call The class file can trigger the collection of the coverage group or the coverage point; associating the verification plan data with the functional coverage data to determine the physical hierarchy path of the coverage group or the coverage point, and generate a functional coverage class file and an initial verification plan including the physical hierarchy path; Analyzing the initial verification plan and the functional coverage class file by using a test tool to obtain the running results and functional coverage information corresponding to each test case; Input the functional coverage information, the initial verification plan and each operation result into the de-marker, so as to output the verification progress marking result; Wherein, the acquisition of verification plan data and the functional coverage data corresponding to the verification plan data include: extracting said verification plan data from a verification plan template; extracting said functional coverage data from a functional coverage template; Wherein, the verification plan data is input by the user into the verification plan template, and the function coverage data is input by the user into the function coverage template; Wherein, the associating the verification plan data and the functional coverage data to determine the entity-level path of the coverage group or the coverage point includes: Associate the verification plan data and the functional coverage data according to the class file, and determine the entity-level path based on the functional coverage data; the entity-level path refers to: characterize a coverage group or a coverage point in a test platform The path where the class entity is located. Based on the entity hierarchy path, the position of the class that needs to be instantiated in the test platform can be determined. 2. The verification progress determination method according to claim 1, wherein the initial verification plan is a hvp file. 3. The verification progress determination method according to claim 2, wherein the test tool is a simulation tool supporting SystemVerilog. 4. The verification progress determination method according to claim 3, characterized in that, before inputting the function coverage information, the initial verification plan and each operation result into the anti-marker to output the verification progress marking result, include: Generate a hud file including the results of each run. 5. The verification progress determination method according to claim 4, further comprising: Visually display the verification progress marking results. 6. A verification progress determination device, characterized in that it comprises: An acquisition module, configured to acquire verification plan data and functional coverage data corresponding to the verification plan data; wherein, the verification plan data includes: coverage groups or coverage points that need to be verified, and the coverage groups or coverage points correspond to The test features, test cases and test scores; the functional coverage data includes: the coverage group or coverage point corresponding to the class, the test score corresponding coverage group and coverage point; the coverage group or the coverage point is variable, and the coverage group or the coverage point is encapsulated into a class file, calling the class file can trigger the collection of the coverage group or the coverage point; An association module, configured to associate the verification plan data with the functional coverage data, to determine the entity-level path of the coverage group or the coverage point, and generate a functional coverage class file and an initial verification including the entity-level path plan; A parsing module, configured to parse the initial verification plan and the functional coverage class file using a test tool to obtain the corresponding running results and functional coverage information of each test case; A marking module, configured to input the function coverage information, the initial verification plan and each operation result into the de-marker, so as to output the verification progress marking result; Wherein, the acquisition module is specifically used for: extracting said verification plan data from a verification plan template; extracting said functional coverage data from a functional coverage template; Wherein, the verification plan data is input by the user into the verification plan template, and the function coverage data is input by the user into the function coverage template; Wherein, the association module is specifically used to: associate the verification plan data and the function coverage data according to the class file, and determine the entity-level path based on the function coverage data; the entity-level path refers to: The path in the test platform where the class entity representing the coverage group or coverage point is located, and the position of the class that needs to be instantiated in the test platform can be determined based on the entity hierarchy path. 7. A verification progress determination device, characterized in that it comprises: memory for storing computer programs; A processor, configured to execute the computer program, so as to realize the verification progress determination method according to any one of claims 1 to 5. 8. A readable storage medium, characterized by being used to store a computer program, wherein when the computer program is executed by a processor, the verification progress determination method according to any one of claims 1 to 5 is realized.

Images