CN117332760A - Verification plan auxiliary editing method, electronic equipment and storage medium - Google Patents

Abstract

The invention relates to the field of chip verification, in particular to an auxiliary editing method for a verification plan, electronic equipment and a storage medium, wherein the auxiliary editing method comprises the steps of obtaining a hierarchical structure of the verification plan in a visual form editing area; extracting id and pid in the hierarchical structure, and generating a hierarchical title structure in the rich text editing area according to the id and the pid; acquiring a specification document spec of a verification plan; acquiring an id corresponding to a title and a design specification of an added verification point at a preset position under the appointed title, and binding the id of the appointed title and the added verification point design specification to obtain an auxiliary text of a verification plan; when a user designates a verification point in a table editing area, acquiring a unique identification id of the verification point; and acquiring the design specification of the target verification point bound by the verification point according to the auxiliary text of the id query verification plan, displaying the design specification of the target verification point in the rich text editing area, simplifying the operation steps of a user, and improving the efficiency of checking the design specification of the verification point.

Description

Verification plan auxiliary editing method, electronic equipment and storage medium

Technical Field

The present invention relates to the field of chip verification, and in particular, to a verification plan assisted editing method, an electronic device, and a storage medium.

Background

In the chip verification process, a verification plan needs to be designed, and user design is verified according to the verification plan. The verification plan system includes a canonical document spec, a coverage database, and a plurality of verification plans, each verification plan for counting coverage data of a partial coverage object in a user design. The canonical document is a hierarchical structure, for example, canonical indexes such as IO number, storage capacity, interaction mode and the like of a memory. Generating a verification plan according to the specification document spec, and refining each level of the specification document spec into each verification point. In order to extract coverage data of the verification plan corresponding to the user design, a targeted extraction of coverage statistics is required. The specific process comprises the following steps: firstly traversing the verification characteristics of the whole verification plan and the sub verification plans contained in the verification plan, searching the source object corresponding to the region expression defined in each verification characteristic in the coverage rate database, reversely marking the coverage rate data of the source object to each verification characteristic, and finally calculating the coverage rate of the current verification plan from bottom to top according to the coverage rate data of each verification point of each layer.

In the prior art for creating the verification plan, each large manufacturer often defines and designs a specific verification plan grammar and a matched verification plan editing tool according to the characteristics of the product. Only test data related to the calculation coverage rate is extracted from the generated verification plan, the design specification of the verification point in the specification document spec is completely discarded, when a user needs to check the design specification of the verification point, the specification document spec can only be opened to find a target verification point for comparison check, and the check process is complex and low in efficiency. Therefore, how to improve the efficiency of checking the design specification of the verification point is a technical problem to be solved.

Disclosure of Invention

Aiming at the technical problems, the invention adopts the following technical scheme:

in a first aspect, the present invention provides a verification plan auxiliary editing method, the method comprising the steps of:

s100, obtaining a hierarchical structure of the verification plan in the visualized table editing area, wherein each verification point in the hierarchical structure is provided with a unique identification id and a unique identification pid of a parent node of the verification point.

S200, extracting a unique identification id of each verification point and a unique identification pid of a parent node of the verification point in the hierarchical structure of the verification plan, and generating a hierarchical title structure in the rich text editing area according to the id and the pid.

S300, acquiring a specification document spec of the verification plan, wherein the specification document spec comprises design specifications of all verification points.

S400, obtaining the unique identification id corresponding to the title and the design specification of the verification point added at the preset position under the appointed title, and binding the unique identification id of the appointed title and the added design specification of the verification point to obtain the auxiliary text of the verification plan.

S500, when a user designates a verification point in a table editing area, acquiring a unique identification id of the verification point; and inquiring the auxiliary text of the verification plan according to the unique identification id of the verification point to obtain the design specification of the target verification point bound by the verification point, and displaying the design specification of the target verification point in the rich text editing area.

The present invention also provides a non-transitory computer readable storage medium having stored therein at least one instruction or at least one program loaded and executed by a processor to implement the above-described method.

Furthermore, the invention also provides an electronic device comprising a processor and the non-transitory computer readable storage medium.

The invention has at least the following beneficial effects:

through the association among the table editing area, the rich text editing area and the specification document spec, when a user clicks the verification point in the table editing area, the design specification text of the verification point is visually displayed in the rich text editing area, the operation steps of the user are simplified, and the efficiency of checking the design specification of the verification point is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a block diagram of a verification plan creation system according to an embodiment of the present invention;

FIG. 2 is a flowchart of a method for creating a reusable verification plan according to a second embodiment of the present invention;

FIG. 3 is a flowchart of a method for fast matching of overlay objects in a verification plan according to a third embodiment of the present invention;

fig. 4 is a flowchart of a verification plan assisted editing method according to a fourth embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.

Because of the differences in definition syntax and tools of each large vendor, it is difficult for a user to define a generic verification plan that can fit different platforms, whenever the user switches vendor tools, he needs to re-write the verification plan according to the vendor defined syntax or using proprietary tools. In order to solve the technical problem that a user needs to learn a complex grammar and has great difficulty in writing a verification plan, the invention provides a first embodiment.

Example 1

Referring to FIG. 1, a block diagram of a verification plan creation system is shown that includes a database, a visualized form editing area, and a hierarchical control area.

It should be noted that, the table editing area and the hierarchical control area are both visual window portions, and the content of the database is not visual.

Optionally, the table editing area is an excel table file or a wps table file, and other table files in the prior art are all within the protection scope of the present invention.

The hierarchical control area is a visual window, and a plurality of buttons are arranged in the hierarchical control area and are used for adding, deleting or modifying the hierarchical relationship among the nodes. The hierarchical control area is independent of the table editing area, and data of the hierarchical control area and the table editing area are derived from the database, so that hierarchical structures in the hierarchical control area, the table editing area and the database are changed at the same time.

Further, the table editing area comprises a plurality of extensible verification point entries, each verification point entry comprises a plurality of attribute fields, wherein each attribute field comprises a unique identification id field of a verification point, a unique identification pid field of a parent node of the verification point, a name field of the verification point, a coverage index type field counted by the verification point and a matching rule field; the unique identification id field of the verification point and the unique identification pid field of the parent node of the verification point are hierarchical relationship attribute fields.

Wherein the verification point is a verification plan or verification characteristic. The user design is typically relatively large, and multiple verification plans are created to verify the user design, each verification plan including verification of multiple verification features. The verification plans form a hierarchical structure, and the verification characteristics also form a hierarchical structure. Wherein the verification plan is also called a plan, the verification characteristic is also called a feature, and the verification characteristic is a verification object refined in the verification plan.

The coverage index type comprises row coverage rate, condition coverage rate, finite state machine coverage rate, assertion coverage rate and the like.

The name of the verification point is the name of the verification plan or the verification characteristic.

Wherein the matching rule is a matching rule specified by a user. When the verification is performed according to the verification plan, the corresponding coverage object is searched in the coverage database under the constraint of the matching rule according to the current verification characteristic, and the coverage data of the coverage object is reversely marked on the current verification characteristic. Optionally, the matching format of the matching rule is a full pathname or an object unique identifier that meets the coverage data interchange standard (Unified Coverage Interoperability Standard, uci) definition. The full path names include object names searched for each layer from a root node designed by a user to a current coverage object to be matched, wherein the object names of different layers are separated by separators, for example, the full path names: instance 1/instance 1.1/instance 1.1.2. Wherein the unique object identifier that meets the UCIS standard definition is matched according to a standard format specified in UCIS, e.g.,/24:work. Top/12:cg/14:cvpa/30:a/:0: #bin#.

Preferably, the matching format of the matching rule is an object unique identifier conforming to the UCIS standard definition. The matching rules are not affected by different definitions of different manufacturers, and are universal because the matching rules accord with the USCIS standard definition.

The set of the id and the pid can construct a parent-child relationship between verification points, namely, a hierarchical relationship between corresponding items can be obtained through configuration of the id and the pid. Specifically, the hierarchy of the validation scheme is defined by the values of id and pid for each validation point.

Optionally, the id is used to uniquely identify the verification plan or verification feature. id is a number or a character string with a hierarchical structure, and other codes or character rules for identifying the hierarchical structure in the prior art fall within the protection scope of the present invention. As one example, id 1.1.2.5, in turn, represents a four-level hierarchy.

Further, the hierarchical control region includes a tree structure aligned and visualized with each verification point entry, the tree structure being associated with the same database as the table editing region.

It should be noted that the tree structure in the hierarchical control area reflects the hierarchical relationship identified by the ids and pids in the table editing area. When creating the verification plan, when a user performs an operation in the hierarchical control area to establish an attribute structure, a unique identification id field of a verification point and a unique identification pid field of a verification point parent node are automatically generated in corresponding verification point entries in the table editing area.

Further, when the user performs an operation on the tree structure in the hierarchical control area, a data block having a corresponding hierarchical structure is generated in the database, and the hierarchical relationship attribute field in the visualized table editing area is generated at the same time.

The data block of each verification point comprises a unique identification id of the verification point, a unique identification pid of a parent node of the verification point, a name of the verification point, a coverage index type counted by the verification point and a matching rule. Optionally, each data block is a json data block, and each attribute in the data block is in a key value pair format.

The operations may be adding a node, deleting a node, modifying a node name, or modifying a hierarchical relationship between nodes. The operation mode of dragging can be adopted when the chromatographic relationship between the nodes is modified.

Because the hierarchical structure of the verification plan can be easily operated in the visualized hierarchical control area, and when the hierarchical structure between the nodes needs to be changed, the hierarchical structure can be easily changed in the visualized hierarchical control area, so that the difficulty of creating the verification plan is greatly reduced.

Further, when the user designates the attribute fields of the verification points in the table editing area, data information of all the attribute fields of the data block corresponding to the verification points is generated in the database, and then a verification plan is obtained. It should be noted that, the table editing area and the hierarchical control area are two independent visual windows and can be displayed side by side.

The invention can complete the creation of the verification plan by using the table file without defining a set of complex grammar for the verification plan and developing a set of special editor for editing the verification plan.

As a preferred embodiment, the end row and end column of the form edit section are specified in order to preserve additional information provided by the user when making the canonical document spec. Specifically, according to the execution sequence of the verification plan, a start row and a start column of the table editing area are designated, a first designated end row mark appearing after the start row is an end row, and a first designated end column mark appearing after the start column is an end column; the continuous area surrounded by the starting row and the ending row, the starting column and the ending column is an effective area, and the content outside the effective area does not participate in the test. Forms, pictures or other remark information in the specification document spec can be added outside the effective area, so that the extra information is ensured not to participate in the test under the condition of keeping the extra information, and great convenience is provided for test users.

Optionally, the mark of the specified ending line and the mark of the specified ending column appear in pairs, the mark of the specified ending line is a blank line and the mark of the specified ending column is a blank column, or the mark of the specified ending line and the mark of the specified ending column are both specified codes or characters, and the codes or characters can be the same or different and are specified by a user.

As a preferred embodiment, the system further includes configuration information, the configuration information including coverage index configuration information and attribute configuration information, the configuration information being stored independently, the configuration information being stored at a location different from the location of the table edit section.

Wherein the coverage index configuration information is used to configure each coverage index type field in the verification plan created in the table edit section. The coverage index configuration information comprises configuration items of coverage indexes of each type, and each configuration item comprises a name of the type of the coverage index, the type of coverage index data and a data aggregation mode. Each configuration entry is used to configure the data type and aggregation manner of each type of coverage index, etc. Other configuration information for configuring coverage in the prior art also falls within the scope of the present invention.

Optionally, the coverage index type is named row coverage, condition coverage, finite state machine coverage, assertion coverage, etc. Other names of coverage indicator types in the prior art are also within the scope of the present invention.

Optionally, the built-in coverage index data types are ratio data ratio, integer data int, real data real, and other data types in the prior art also fall within the protection scope of the present invention.

Optionally, the data aggregation mode is sum, average, minimum min, or maximum max. The user may also add custom aggregators to define the data aggregation manner.

Optionally, the coverage index configuration information further includes a weight of coverage. Wherein the weights are used to adjust the specific gravity of the corresponding coverage in the calculation process.

Optionally, the coverage index configuration information further includes a target expression of the coverage index. Wherein the target expression is used to define a minimum value of coverage. For example, setting the target expression to 90% of the full coverage (gold > 0.9), then the verification passes when the coverage of the verification plan is greater than 90%.

Wherein the attribute configuration information includes an attribute name, an attribute data type, and a flag identifying whether the attribute value needs to be passed down. Optionally, the attribute data type is character string data, integer data or real number, and other data types in the prior art are also within the scope of the present invention.

Optionally, the configuration information is stored in a database, and all verification plans share the same global configuration information. Global shared reuse of configuration information can be achieved by configuring global configuration information independently, rather than repeating definitions in the verification plan each time.

Optionally, the configuration information is respectively and independently stored in a table file, and multiplexing is realized by copying the table file. The configuration information is stored in the database as global configuration or in an independent table file, multiplexing is realized by copying the table file, and the purpose of multiplexing the configuration information can be achieved by both the two realization modes. When some configurations need to be added, modified and deleted, only the configuration file needs to be modified, and the corresponding grammar in each verification plan does not need to be modified as in the prior art.

As a preferred embodiment, when a single verification feature comprises a plurality of matching rules, the different matching rules are separated by a specified separator. Optionally, the specified separator is comma or semicolon, and other separators for separating two matching rules in the prior art fall within the scope of the present invention.

As a preferred embodiment, the system further comprises: when the user performs the change operation on the tree structure in the hierarchical control area, the data information of the hierarchical relation attribute field of the data block in the database is updated, and the hierarchical relation attribute field in the visualized table editing area is updated at the same time.

As a preferred embodiment, the verification data in the verification plan is extracted at the time of verification according to the verification plan. Optionally, the third party tool or VBA directly reads the content of the table editing area, extracts the data in the verification plan area to generate an intermediate format, and inputs the intermediate format to the coverage rate reverse marking program for matching calculation. Or directly exporting the csv file, and inputting the csv file to a coverage rate reverse labeling program for matching calculation.

As a preferred embodiment, the table editing area further comprises a coverage index field; when a single verification point includes a plurality of matching rules, the coverage index and the matching rules are configured in order. For example, a single verification point includes three matching rules, each matching rule verification generates one coverage indicator, and the coverage indicators are ranked according to the ranking of the three matching rules.

The use of a form edit field to create a verification plan is also beneficial in that functions integrated in the form tool can assist in creating the verification plan, such as copy-and-paste, bold highlighting, etc.

The embodiment can complete the creation of the verification plan just by using the form file, does not need to specially define a set of grammar and editor, can complete the creation of the verification plan by directly filling or dragging the content without learning complex grammar, and reduces the threshold of the user for creating the verification plan. However, when the system automatically extracts the data in the verification plan created by the table file, and after obtaining the verification plan data file capable of being used for finding coverage rate in the user design, the verification plan data file includes a large number of data blocks, if the user needs to adjust the hierarchical structure among the data blocks, the large number of data blocks need to be changed, which is not only easy to make mistakes, but also easy to cause data blocking, and if the data blocks needing to be changed include a plurality of repeated data blocks in the verification plan data file, the difficulty of changing needs to be increased, and the invention provides a second embodiment for solving the above problem.

Example two

Referring to FIG. 2, there is shown a flowchart of a reusable validation program creation method, the method comprising the steps of:

s100, storing hierarchical structure information of each verification point in the verification plan in a structure data block of a structure file, and storing non-hierarchical structure information of each verification point in an associated data block of an associated file to respectively obtain the structure file and the associated file of each verification plan. The structure file and the association file are verification plan data files.

Further, the structure file includes a plurality of structure data blocks, and the hierarchical structure information of each structure data block includes a unique identification id of the verification point and a unique identification pid of a parent node of the verification point. It should be noted that, the second embodiment is an improvement based on the first embodiment, and concepts of the verification point, the unique identifier id of the verification point, and the unique identifier pid of the parent node of the verification point in the second embodiment are the same as those in the first embodiment, and are not described again. It should be noted that, the data of each verification point is stored in two independent json format data blocks respectively: the structure data block and the association data block. And reflects the hierarchical structure among the verification point entries through the binding relation between the id and the pid. The structure file can rapidly load the whole hierarchy structure of the plan and support the operations of adding, deleting and checking the hierarchy structure.

Further, the association file includes a plurality of associated data blocks, and the non-hierarchical information of each associated data block includes a unique identification id of the verification point and a matching rule. When the unique identification id of the verification point in the associated data block is the same as the unique identification id of the verification point in the structural data block, the associated data block and the structural data block are two parts of data of the same verification point. The structure data block carries position structure information of the verification point in the hierarchical structure, and the associated data block carries non-hierarchical structure information such as matching information of the verification point. The matching rule is the same as that in the first embodiment, and will not be described again. When the verification point is a verification plan, the matching rule in the associated data block is null.

Further, there is one and only one root node in each structure file; and the associated data blocks in the associated file are mapped and associated with the structural data blocks in the structural file through the unique identification id of the verification point.

The root node in the structure file defining the verification plan is the plan, the root node in the structure file defining the sub-plan is the sub-plan, and the root node in the file defining the sub-verification characteristic is the sub-verification characteristic. Specifically, in the structure file defining the verification plan, the root node is the verification plan, the child nodes of the root node are different verification points, each verification point may further have a child verification point, and so on.

S200, acquiring the name of a verification module to be nested designated by a user and a target nested verification point in a verification plan; the hierarchical structure information of the verification modules to be nested is stored in a structure data block of a structure file, and the non-hierarchical structure information is stored in an associated data block of an associated file.

Wherein the verification module is a sub-verification plan or sub-verification feature. And the information of the verification modules to be nested is also respectively stored in the structure file and the associated file. It should be noted that, the verification module is the same as the verification plan in storage mode, and the sub-verification plan also includes data blocks of multiple verification points, and a hierarchical structure is provided between the verification points. Similarly, the sub-verification feature also includes a data block including a plurality of verification points and has a hierarchical structure between the verification points.

The target nested verification point is a father node of the verification module to be nested.

S300, creating a target structure data block, wherein the verification point of the target structure data block is a verification module to be nested, the unique identification pid of the father node of the verification point is bound with the target nested verification point, and an index attribute is added into the target structure data block and is used for designating the name of the verification module to be nested.

When the verification plan is large, only the structure file is loaded; when the user views the detailed attribute, the content in the associated file is loaded once or through id distribution, so that the loading speed of the verification plan can be improved.

When the user only modifies the hierarchical structure of the verification plan, only the structure file is required to be updated, and the content of the associated file is not required to be modified; similarly, the modification of attributes of non-hierarchical information does not modify the content of the structured file. For large verification plans, the prior art defines all the attributes of each verification point into one file through a custom grammar, so that the hierarchical structure cannot be modified and the problems of multiplexing cannot be solved. By adopting the method provided by the second embodiment, the size of the data block to be moved can be reduced to the greatest extent, thereby achieving the effects of improving the speed and reducing the memory overhead and solving the problem of blocking.

In the second embodiment, the verification plan is defined by adopting the data block, so that the universality of the verification plan is improved, and a user does not need to be familiar with a special grammar defined by a certain manufacturer or rely on a custom editor provided by the manufacturer to write the verification plan. And can also be supported by Web applications without additional data conversion. Meanwhile, through a flattened data format, the coupling relation between a plan (plan) and verification characteristics (feature) in a verification plan is reduced, so that the plan and the verification characteristics have reusability, the problem of blocking is solved, and the problem that when the reused plan or verification characteristics need to be modified, only one data block needs to be modified is solved, and the problem that a repeated module needs to be uniformly modified is solved.

As a preferred embodiment, before S100, further includes:

s10, creating an original verification plan in a table editing area according to user specification to obtain an original verification plan table file; the table editing area comprises a plurality of extensible verification point entries, each verification point entry comprises a plurality of attribute fields, wherein each attribute field comprises a unique identification id field of a verification point, a unique identification pid field of a parent node of the verification point, a name field of the verification point, a coverage index type field counted by the verification point and a matching rule field; the unique identification id field of the verification point and the unique identification pid field of the parent node of the verification point are hierarchical relationship attribute fields.

S20, configuring coverage rate indexes in a coverage rate index editing area to obtain a coverage rate index configuration file, wherein the coverage rate index file is independent of an original verification plan table file; the coverage index configuration information comprises configuration items of coverage indexes of each type, each configuration item comprises a name of the type of the coverage index, the type of coverage index data and a data aggregation mode, and other configuration information for configuring coverage in the prior art also falls into the protection scope of the invention.

S30, configuring attributes in the attribute editing area to obtain an attribute configuration file, wherein the attribute configuration file is independent of an original verification plan table file and a coverage rate index configuration file; wherein the attribute configuration information includes an attribute name, an attribute data type, and a flag identifying whether the attribute value is passed down.

It should be noted that, the contents, coverage index configuration information, and attribute configuration information included in the table editing area and the table editing area are the same as those in the first embodiment, and are not described again.

S40, extracting data in the original verification plan table file according to the specified keywords to obtain a verification plan data file, wherein the verification plan data file comprises hierarchical structure information and non-hierarchical structure information. And extracting data in the original verification plan table file through the keywords of the hierarchical structure information and the keywords of the non-hierarchical structure information to obtain the verification plan data file. The verification plan data file is used for searching the user design file to acquire corresponding coverage rate data.

As a preferred embodiment, when the types of the verification points included in the data blocks in the structure file are not unique, all the structure data blocks in the structure file further include the types of the verification points or unique identifiers of the types of the verification points, and the types of the verification points include the unique identifiers of the verification points of different types and the unique identifiers when each type of the verification points is used as a child node. As an example, when the verification point of the data block in the structure file may be a verification characteristic or a verification plan, the verification point type includes four types of verification characteristic, sub-verification characteristic, verification plan and sub-verification plan, the unique identifier of the verification characteristic is configured as 1, the unique identifier of the sub-verification characteristic is configured as 2, the unique identifier of the verification plan is configured as 3 and the unique identifier of the sub-verification plan is configured as 4.

As a preferred embodiment, the data blocks in the association file may also include a coverage indicator type specifying which type of coverage indicator needs to be collected by the verification point. When the verification point is the verification characteristic, if the verification point does not comprise the coverage index type, the corresponding coverage index in the matching rule is collected; and when the verification point is the verification plan, if the verification point does not comprise the coverage index type, collecting coverage indexes corresponding to all verification characteristics under the verification plan.

Based on the same inventive concept as the method of the second embodiment, the second embodiment also provides a non-transitory computer readable storage medium having stored therein at least one instruction or at least one program loaded and executed by a processor to implement the method provided by the second embodiment.

The second embodiment also provides an electronic device comprising a processor and the non-transitory computer readable storage medium.

One of the core functions of the verification plan is to quickly find the corresponding coverage object in the coverage database through the region expression specified by the user, and acquire the coverage data of the coverage object. After obtaining the verification plan data file generated in the second embodiment, how to quickly find the corresponding coverage object is a technical problem to be solved.

Example III

Referring to fig. 3, a flowchart of a method for fast matching coverage objects in a verification plan is provided, the method includes the following steps:

p100, acquiring an index database according to user design, wherein the user design comprises overlay objects with different design levels, the index database comprises index files of the overlay objects with different design levels in the user design, and each overlay object with the design level corresponds to one index file; the index file of each design level includes the name of the overlay object, the overlay object type, and the unique identification id of the overlay object.

Wherein the overlay object includes an overlay domain and an overlay item. For example, the overlay Object is an Object in the UCIS standard. The overlay domain is the object of all the sub-nodes in the design hierarchy designed by the user, and the overlay domain is Scope in UCIS standard. The coverage item is an object of all leaf nodes in a design hierarchy designed by a user and is a coverage in UCIS standard.

In order to improve the retrieval efficiency, different index databases are required to be created for objects with different design levels, so all the overlay objects are divided into three groups: a first layer of overlay fields, a second layer of overlay fields, and a third layer of overlay items. The first layer overlay domain includes module, instance, overlay group, assertion of assent, etc. The second layer coverage is another coverage supporting a search function in addition to the first layer coverage. The third layer of coverage is coverage supporting the search function.

The overlay object types are different in different user design levels, for example, in a first layer overlay domain, and the overlay object types are module, instance, overlay group, assertion server, and the like.

P200, acquiring a verification plan designed by a user, and extracting all area expressions in the verification plan; and generating a data matching mode according to the region expression, wherein the data matching mode comprises basic information of the coverage object and matching conditions of different layers, the matching conditions comprise the type of the coverage object, the matching mode and the matching rule, and the basic information comprises an action instruction.

Wherein the region expression is a string of characters conforming to a specified rule for locating one or more overlay objects in the original user design. The format of the region expression includes two types: the first is [ overlay object type ]: [ object full name ], and the second is the unique identification in uci. The object full name in the first type is the complete hierarchy name of the object, and the different hierarchies are separated by specifying separators, for example: instance: top. Sub1.Sub2. The first area expression has strong readability, and a user can conveniently write out the area expression according to the design; however, the object type of the name cannot be intuitively known only by the name of each layer, and additional overhead is required to establish the mapping relationship between the name and the object type. The second region expression can know the type corresponding to the changed object through the id of the overlay object type in the uci standard, for example: the method has the advantages that the universality is strong, because type information (type id) is already contained in each layer of information, the mapping relation between names and object types is not needed to be established, the readability is poor, the UCIS standard is needed to be familiar, and the user writing of region expressions is difficult.

When the coverage rate data is calculated according to the verification plan created by the user, all the area expressions in the verification plan are extracted, the object id corresponding to each area expression is queried in the index database, the coverage rate data of the object is found in the memory through the object id, and finally the coverage rate data of each node is aggregated onto each feature and play from bottom to top according to the hierarchical structure of the verification plan, so that the coverage rate data of each feature and play are obtained. In this process, since the verification plan grammar and the format of the region expression defined by different platforms are different, in order to improve the universality, the invention defines a set of data matching modes of the middle layer, which are used for storing basic information required by matching the coverage object, and generating an index database based on the data format. Verification plans of different manufacturers can be used for achieving multiplexing of the matching search scheme by extracting corresponding information and generating a data matching mode of the middle layer.

Wherein, for each region expression, the corresponding data matching mode comprises basic information and matching conditions of different layers. The basic information in the data matching mode and the matching condition of each layer are in a key value pair format. The data matching pattern must include basic information and matching conditions of the first layer coverage area. The data matching pattern may further include matching conditions of the second layer coverage and matching conditions of the third layer coverage. The user can customize more attributes as desired.

The basic information is mainly used for describing a matching rule, the basic information comprises an action command, the action command is used for identifying operations, such as an include operation and an include operation, of the data matching mode for execution, the include operation corresponds to coverage object matching of a verification plan, the include operation corresponds to a function excluded from coverage indexes, and a user can define more operations according to requirements. The basic information can also comprise a custom name and an annotation, wherein the custom name is used for identifying an identifier of the current data matching mode; when all the data matching modes are required to be stored in the database and reused, the data matching modes can be deleted and revised in the database according to the custom names; this attribute may not be specified if reuse is not a concern.

As a preferred embodiment, in P200: when the matching condition is a matching condition of the first layer coverage or the second layer coverage, the coverage object type is a coverage type. When the matching condition is a matching condition of the third layer coverage item, the coverage object type is a coverage item type. That is, the matching conditions of the first layer coverage area and the second layer coverage area each include the coverage object type, the matching manner, and the matching rule.

Optionally, the matching condition of the coverage area of the first layer may further include a coverage index type.

Optionally, the matching mode is character string matching, UCIS unique ID matching, regular expression matching or wildcard matching.

Wherein the matching rule is matching content specified by the user.

Wherein, the matching condition of the second layer coverage area and the matching condition of the third layer coverage item are both selectable conditions. For example, when the region expression is defined as an asset, only the matching condition of the first layer coverage is required to be specified, and the matching condition of the second layer coverage and the matching condition of the third layer coverage are not required to be defined; when the overlay object type in the matching condition of the first layer overlay domain is a model or an instance, a second overlay domain of the overlay index type may be specified in the matching condition of the second layer overlay domain.

And P300, searching unique identification ids of all the coverage objects meeting the matching conditions in an index database according to the names and the types of the coverage objects, and acquiring coverage rate data through the unique identification ids of the coverage objects.

The query method is different depending on the configuration of the index database.

As a preferred embodiment, an index table is built for the first layer coverage area prior to P100 using one of two creation approaches: first kind: and respectively creating a plurality of first-layer index table files for each overlay domain type in the first-layer overlay domain, wherein each first-layer index table file comprises an index data block of each overlay domain object, and each index data block comprises the name of the overlay domain and the unique identifier of the overlay domain object in the memory. Second kind: creating a first-layer index table file for the first-layer overlay domain, wherein the first-layer index table file comprises index data blocks of each overlay domain object, and each index data block comprises the name of the overlay domain, the type of the overlay domain and the unique identification of the overlay domain object in the memory.

As a preferred embodiment, an index table is built for the second layer coverage area prior to P100 using one of two creation approaches: first kind: creating a plurality of second-layer index table files for each coverage index type in the second-layer coverage domain respectively, wherein each second-layer index table file comprises an index data block of each coverage domain object, and each index data block comprises a name of the coverage domain, a unique identifier of a father node, the type of the coverage domain and a unique identifier of the coverage domain in a memory. Second kind: creating a second-layer index table file for the second-layer overlay domain, wherein the second-layer index table file comprises index data blocks of each overlay domain object, and each index data block comprises the name of the overlay domain, the unique identifier of a father node, the type of the overlay domain and the unique identifier of the overlay domain in the memory;

as a preferred embodiment, the index table is built for the third layer coverage before P100 using the following creation method: creating a third-layer index table file for the coverage index type specified in the third-layer coverage item, wherein the third-layer index table file comprises index data blocks of each coverage domain object, and each index data block comprises the name of the coverage item, the unique identification of a father node, the type of the coverage item and the unique identification of the coverage item in the memory. It should be noted that, because the number of the overlay items may be very large, if indexes are built for all the overlay items in the design, the size of the index database will be increased, which affects the speed of generating the index database and the query efficiency, so that the index database is generally searched directly in the memory, and if the user designates to build the index table, the index table file can be built for the overlay items with a small number of overlay items and the search content being the character strings with strong readability.

As a preferred embodiment, the P300 further comprises: when a first layer index file and a second layer index file are created, a thread pool is created, each matching mode is queried sequentially by using multithreading, and the querying step of each matching mode comprises the following steps:

and P310, for the matching condition of the first layer coverage in the matching mode, searching the unique identification of the first layer coverage object meeting the matching condition of the first layer coverage in the first layer index file according to the type of the first layer coverage and the name of the first layer coverage.

And P320, if the matching mode does not comprise the matching condition of the second layer coverage area, finishing searching, and returning the unique identification of the found first layer coverage object meeting the matching condition of the first layer coverage area. If the matching mode comprises the matching condition of the second layer coverage, the unique identifier of the second layer coverage object meeting the matching condition of the second layer coverage is searched in the second layer index file through the unique identifier of the first layer coverage object meeting the matching condition of the first layer coverage, the name of the second layer coverage and the type of the second layer coverage.

And P330, if the matching mode does not comprise the matching condition of the third layer coverage, ending the search, and returning the unique identification of the found second layer coverage object meeting the matching condition of the second layer coverage. If the matching condition of the third layer coverage item is included in the matching mode, searching the unique identifier of the third layer coverage object meeting the matching condition of the third layer coverage item in the third layer index file or the memory through the unique identifier of the second layer coverage object meeting the matching condition of the second layer coverage field, the name of the third layer coverage item and the type of the third layer coverage item.

As a preferred embodiment, the P300 further comprises: when a plurality of first layer index files and a plurality of second layer index files are created, all data matching modes are grouped according to the coverage object types of the first layer coverage domain, and a single process is used for searching the plurality of first layer index files and the plurality of second layer index files according to each group of data matching modes.

According to the method, an index database is established for different design layers and different types of coverage objects according to a certain rule, and concurrent searching is carried out on each type of region expression. Compared with the traditional method that the whole original user design structure is traversed, the performance of matching each area expression one by one through the regular expressions is greatly improved. Meanwhile, the grammar and the region expression format of the verification plan created by different platforms can be suitable for the universal data matching mode, so that the universality is strong.

The third embodiment of the present invention also provides a non-transitory computer readable storage medium, where the storage medium may be provided in an electronic device to store at least one instruction or at least one program related to a method for implementing one of the method embodiments, where the at least one instruction or the at least one program is loaded and executed by the processor to implement the method provided in the foregoing embodiments.

The third embodiment of the invention also provides an electronic device, which comprises a processor and the non-transitory computer readable storage medium.

A third embodiment of the invention also provides a computer program product comprising program code for causing an electronic device to carry out the steps of the method according to various exemplary embodiments of the invention as described in the specification, when said program product is run on the electronic device.

In order to solve the technical problem of how to improve efficiency of checking design specifications of verification points, the present invention provides a fourth embodiment.

Example IV

Referring to fig. 1, a verification plan auxiliary editing method includes the following steps:

and T100, acquiring a hierarchical structure of the verification plan in the visualized table editing area, wherein each verification point in the hierarchical structure is provided with a unique identification id and a unique identification pid of a parent node of the verification point.

Wherein the verification plan includes a visualized form editing area, a hierarchical control area, and a rich text editing area. The visualized form editing area, the hierarchical control area and the rich text editing area are three different areas, wherein the form editing area is a list of each verification point item in the verification plan, and the user can edit the list. The hierarchical control area is a hierarchical structure between verification points synchronized with verification plan verification points in the form editing area. The rich text editing area edits and visualizes the hierarchical structure of the verification plan and the design specification text of each verification point in the specification document spec through the rich text editor, the hierarchical structure of the verification plan is synchronous with the hierarchical structure in the table editing area, and when a user clicks the corresponding verification point in the table editing area, the hierarchical control area or the rich text editing area, a visualized window in the rich text editing area can directly position and display the design specification text of the corresponding verification point in the specification document spec. The step of displaying the hierarchical structure of the verification plan and generating the design specification text of each verification point in the specification document spec in the rich text editing area refers to the subsequent steps, and will not be described again.

The table editing area, the hierarchical control area, the verification point, and the like are the same as those of the first embodiment, and are not described again.

And T200, extracting a unique identification id of each verification point and a unique identification pid of a parent node of the verification point in the hierarchical structure of the verification plan, and generating a hierarchical title structure in the rich text editing area according to the id and the pid.

It should be noted that the extraction of id and pid is the id and pid of each verification point extracted from the table edit area. Since the binding between id and pid creates a hierarchy between the verification points, the rich text editing area is also able to create a hierarchy with the name of each verification point as a title of a different hierarchy.

And T300, acquiring a specification document spec of the verification plan, wherein the specification document spec comprises design specifications of all verification points. The canonical document is a hierarchical structure, for example, canonical indexes such as IO number, storage capacity, interaction mode and the like of a memory.

And T400, acquiring a unique identification id corresponding to the title and a design specification of the verification point added at a preset position under the specified title, and binding the unique identification id of the specified title and the added design specification of the verification point to obtain an auxiliary text of the verification plan.

In the process of generating the verification plan, the design specification of each verification point in the specification document spec needs to be added under the corresponding title in the rich text editing area.

The unique identification id of the specified title and the added verification point design specification are bound, so that the added design specification and the specified title can be synchronized, and the operation synchronization for the title is applied to the added design specification. For example, the added design specification sync changes when the hierarchical structure of the specified title changes, and the added design specification sync is deleted or moved when the specified title is deleted or moved.

T500, when a user designates a verification point in the table editing area, acquiring a unique identification id of the verification point; and inquiring the auxiliary text of the verification plan according to the unique identification id of the verification point to obtain the design specification of the target verification point bound by the verification point, and displaying the design specification of the target verification point in the rich text editing area.

Through the association among the table editing area, the rich text editing area and the standard document spec, when a user clicks the verification point in the table editing area, the design standard text of the verification point in the standard document spec is visually displayed in the rich text editing area, the operation steps of the user are simplified, and the efficiency of checking the design standard of the verification point is improved.

As a preferred embodiment, T400 further comprises the step of adding a title to the auxiliary text of the verification plan:

T401, obtaining the unique identification id of the title selected by the user, the unique identification id of the next title of the selected title, the hierarchy where the inserted target title is located and the text of the target title.

It should be noted that the next title may be at the same title level as the selected title, or may be at a different level from the selected title. For example, a first level is denoted by 1, a second level is denoted by 1.1 and is a child node of the first level 1, and so on. When the selected title is 1.1 and the next title is 1.1.1, the next title is the child node of the selected title, both at different levels. When the selected title is 1.1 and the next title is 1.2, the next title is the peer node of the selected title, both at the same level. Or when the selected title is 1.1 and the next title is 2, the next title is the node of the upper level of the selected title, and the nodes are in different levels.

And T402, obtaining the target position of the target title inserted by the user according to the unique identification id of the selected title, the unique identification id of the next title and the hierarchy where the target title is located.

It should be noted that, the unique id of the selected title and the unique id of the next title can determine that the target title needs to be inserted between the two titles, and then the hierarchy of the target title can be obtained according to the hierarchy where the target title is located, so as to obtain the target position of the target title. For example, when the title is selected as 1.1 and the next title is 1.2, when the level at which the target title is located is the third level, then the child node with the target title of 1.1 may be, for example, 1.1.1 located between 1.1 and 1.2; when the hierarchy of the object header is the second layer, then the peer node of the object header 1.1 may be, for example, 1.3 located between 1.1 and 1.2.

And T403, creating a target area at the target position, and inserting a target title text into the target area to obtain an updated auxiliary text.

It should be noted that the target area may be designated as a blank line area.

When the user triggers the operation of adding the title, the title can be added to the auxiliary text of the verification plan through the steps of T401-T403, so that the user is convenient to allow the title to be added to the auxiliary text on the basis of ensuring the synchronization with the hierarchical structure in the verification plan, and the added title is required to be explained not to be synchronized into the hierarchical structure of the verification plan.

As a preferred embodiment, T400 further comprises the step of tracking the auxiliary text modification content:

and T410, when the user triggers a specified operation event in the rich text editing area, acquiring the operation event type of the operation event and the currently selected node.

Optionally, the operation event is a mouse trigger designating button event or a keyboard pressing designating key event, etc.

Optionally, the operation event type is a delete key or a rollback key, etc.

The current selected node is the node position where the current cursor is located.

T420, configuring different type tags and tag styles for different operation event types.

Optionally, when the operation event type is insert, insert tags are configured at both ends of the insert content. When the operation event type is delete, delete tags are configured at both ends of the inserted content. When the patterns of the inserted labels or the deleted labels are displayed or hidden, the label patterns are configured in the corresponding labels.

T430, when the operation event type is a delete key or a rollback key, and when the selected content is not empty, adding a type tag outside the selected content; when the selected content is empty and is a rollback key, adding a deletion tag outside the selected content; and displaying the modification trace in the visual window according to the label style configured in the type label.

Optionally, the rich text editor uses html language. When configuring the insert tag or delete tag, the insert tag or delete tag is added at both ends of the user content. For example, the user content is "< p > hello word", the insertion tag is "< ins class=" track-ins ">/inst" ", and" < ins class= "track-ins" > < p > hello word "</inst >", is obtained after the insertion tag is added to both ends of the user content. In the inserted label ins is the label name of the inserted label, class is the key of the class, label style is defined in track-ins, e.g. the color of the inserted font, whether there is an underline or not, etc.

Through the above-mentioned steps T410-T430 implementing the function of tracking the auxiliary text modification content based on html, the content modified by the user can be displayed in the specified tag style, and the history modification trace is kept.

As a preferred embodiment, in T420, when the user triggers receiving the revision command, the currently selected selection area of the user is obtained, all the inserted tags and the deleted tags in the currently selected selection area are traversed, and the inserted tags and the deleted tags outside the selected content are deleted.

As a preferred embodiment, in T420, when the type tag is a reject revision, acquiring a currently selected selection area of the user, and traversing all inserted tags and deleted tags in the currently selected selection area; when traversing to the inserted label, acquiring a parent node label of the inserted label, and deleting the inserted label and the content marked by the inserted label from the parent node label; and when traversing to delete the tag, deleting the delete tag, and retaining the content marked by the delete tag.

As a preferred embodiment, T400 may also obtain verification plan assistance text according to the following steps: and acquiring a unique identification id corresponding to the title and a row number range of target content selected by a user in the specification document spec, and binding the row number range with the unique identification id of the corresponding verification point to obtain an auxiliary text of the verification plan. It should be noted that, this way is to directly link the spec document spec with the auxiliary text, when the design specification of the verification point needs to be obtained, the range of the rank number bound by the verification point needs to be obtained from the auxiliary text, and then the corresponding target content is checked in the spec document spec according to the range of the rank number. The step does not need to paste the content in the standard document into the auxiliary text, and the auxiliary text is equivalent to providing an index, can be directly associated to the standard document, and can be more directly and comprehensively viewed. In the T400, the unique identification id corresponding to the title is bound with the added verification point design specification, namely, the content in the specification document is directly pasted into the auxiliary text, when the design specification of the verification point needs to be acquired, the corresponding design specification is directly displayed in the rich text editing area through id association, and the viewing efficiency is higher than that of binding line and column numbers.

Embodiments of the present invention also provide a non-transitory computer readable storage medium that may be disposed in an electronic device to store at least one instruction or at least one program for implementing one of the methods embodiments, the at least one instruction or the at least one program being loaded and executed by the processor to implement the methods provided by the embodiments described above.

Embodiments of the present invention also provide an electronic device comprising a processor and the aforementioned non-transitory computer-readable storage medium.

Embodiments of the present invention also provide a computer program product comprising program code for causing an electronic device to carry out the steps of the method according to the various exemplary embodiments of the invention as described in the specification, when said program product is run on the electronic device.

While certain specific embodiments of the invention have been described in detail by way of example, it will be appreciated by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the invention. Those skilled in the art will also appreciate that many modifications may be made to the embodiments without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.

Claims (10)

1. A method of verification plan assisted editing, the method comprising the steps of:

t100, acquiring a hierarchical structure of a verification plan in a visual table editing area, wherein each verification point in the hierarchical structure is provided with a unique identification id and a unique identification pid of a parent node of the verification point;

t200, extracting a unique identifier id of each verification point and a unique identifier pid of a parent node of the verification point in the hierarchical structure of the verification plan, and generating a hierarchical title structure in a rich text editing area according to the ids and the pids;

t300, acquiring a specification document spec of a verification plan, wherein the specification document spec comprises design specifications of all verification points;

t400, obtaining a unique identification id corresponding to the title and a design specification of an added verification point at a preset position under the appointed title, and binding the unique identification id of the appointed title and the added verification point design specification to obtain an auxiliary text of a verification plan;

t500, when a user designates a verification point in the table editing area, acquiring a unique identification id of the verification point; and inquiring the auxiliary text of the verification plan according to the unique identification id of the verification point to acquire the design specification of the target verification point bound by the verification point, and displaying the design specification of the target verification point in the rich text editing area.

2. The method of claim 1, wherein T400 further comprises the step of adding a title to the auxiliary text of the verification plan:

t401, obtaining the unique identification id of the title selected by the user, the unique identification id of the next title of the selected title, the level where the inserted target title is located and the text of the target title;

t402, obtaining the target position of the target title inserted by the user according to the unique identification id of the selected title, the unique identification id of the next title and the hierarchy where the target title is located;

and T403, creating a target area at the target position, and inserting a target title text into the target area to obtain an updated auxiliary text.

3. The method of claim 1, wherein T400 further comprises the step of tracking auxiliary text modification content:

t410, when a user triggers a specified operation event in the rich text editing area, acquiring the operation event type and the currently selected node of the operation event;

t420, configuring different type labels and label styles for different operation event types;

t430, when the operation event type is a delete key or a rollback key, and when the selected content is not empty, adding a type tag outside the selected content; when the selected content is empty and is a rollback key, adding a deletion tag outside the selected content; and displaying the modification trace in the visual window according to the label style configured in the type label.

4. A method according to claim 3, wherein the type tags include insert tags and delete tags.

5. The method of claim 3, wherein in T420, when the user triggers receiving the revision command, a currently selected selection area of the user is acquired, all inserted tags and deleted tags in the currently selected selection area are traversed, and inserted tags and deleted tags outside the selected content are deleted.

6. The method of claim 3, wherein in T420, when the type tag is a reject revision, obtaining a currently selected selection area of the user, traversing all inserted tags and deleted tags within the currently selected selection area; when traversing to the inserted label, acquiring a parent node label of the inserted label, and deleting the inserted label and the content marked by the inserted label from the parent node label; and when traversing to delete the tag, deleting the delete tag, and retaining the content marked by the delete tag.

7. The method of claim 1, wherein the rich text editing area edits and visualizes, via a rich text editor, the hierarchy of the verification plan and the design specification text for each verification point in the specification document spec.

8. The method of claim 1, wherein T400 is further operable to obtain the verification plan assistance text in accordance with the steps of: and acquiring a unique identification id corresponding to the title and a row number range of target content selected by a user in the specification document spec, and binding the row number range with the unique identification id of the corresponding verification point to obtain an auxiliary text of the verification plan.

9. A non-transitory computer readable storage medium having stored therein at least one instruction or at least one program loaded and executed by a processor to implement the method of any one of claims 1-8.

10. An electronic device comprising a processor and the non-transitory computer readable storage medium of claim 9.