Method and system for measuring and reporting test coverage of logic designs

[0002] This application is related by common inventorship and subject matter to co-pending applications titled “Method and System for Efficiently Generating Parameterized Bus Transactions” and “Method and System for Generating a Design-Specific Test Case From a Generalized Set of Bus Transactions”. Until such time as the foregoing applications are assigned application numbers by the U.S. Patent and Trademark Office, they may be respectively referenced by the following applicant: Ser. Nos. 09/638,268 and 09/638,757. The listed applications are assigned to International Business Machines Corporation and are entirely incorporated herein by this reference.

[0003] The present invention relates to the testing of logic designs in simulation or hardware, and more particularly to a method and system for measuring and reporting the extent of test coverage of a design-under-test (DUT) in terms of its bus transactions.

[0004] A process known as verification comprises applying test cases to a DUT and checking the results against expected results to determine whether the DUT functions correctly. Functional verification of logic designs which interface to standardized buses typically involves the use of a software tool known as a bus functional model (BFM). A BFM emulates a bus protocol to apply a test case in simulation to a DUT modeled by a hardware description language (HDL).

[0005] The BFMs allow verification engineers to write test cases as bus transactions. The bus transactions may be expressed in bus functional language (BFL) statements which are decoded and executed by the BFMs using a logic simulator. For example, a standardized BFM transaction test case for a 32 bit data slave design that uses read and write transactions with address, data, and control signal information could comprise BFL statements appearing as follows (comments indicated by “//”):

[0006] In the foregoing example, read and write are two different transaction types, while address, byte enable, and data are parameters of the respective transaction types. The parameters were used to specify data to be written to an address, and to subsequently read the address to determine whether the data was correctly written.

[0007] In order to verify that a DUT completely complies with a standardized bus interface, all possible bus transactions must be performed to ensure that the DUT-to-bus interface operates under all legal bus conditions. This process, also known as regression testing, entails the enumeration of all possible and legal transaction combinations to ensure a complete and correct design.

[0008] The testing of a DUT for bus compliance can be a complex and time-consuming procedure, requiring considerable computer resources. Numerous bus transactions and varied test scenarios must typically be applied. Often, executing a complete set of tests that exhausts all the possible bus transactions of a DUT at one time is impracticable. More typically, test cases must be applied in limited batches. Accordingly, tracking of the extent of test coverage for a design over a testing period to ensure that complete test coverage has been achieved becomes a difficult chore that slows the regression testing or verification process.

[0009] In view of the foregoing, a method and system for conveniently measuring and reporting the extent of test coverage is needed.

[0010] In a method and system according to the invention, incremental test coverage information from an application of a test case to a DUT is collected. The incremental test coverage information, along with cumulative test coverage information, is automatically correlated with a set of valid bus transactions corresponding to the DUT to determine the extent of the test coverage for the DUT.

[0011] In an embodiment, the correlation process uses a DUT configuration file which describes the DUT in a condensed syntax. The correlation process automatically generates possible bus transactions for the DUT from the syntax. Rules included in the syntax filter out selected ones of the possible bus transactions to produce the set of valid transactions. The valid transactions are compared with the incremental and cumulative test coverage information to determine which valid bus transactions have or have not been applied in testing the DUT.

[0012] In view of the foregoing, the present invention provides a convenient and easy-to-use measure of test coverage. The invention allows a user to apply relatively small sets of tests and incrementally build toward total coverage. A user can combine the information of multiple test case applications, either in simulation or hardware, and measure not only what percentage of coverage has been achieved, but what remaining transactions are needed to accomplish full coverage.

[0013] FIGS. 1A-1C illustrate the invention in functional block diagram form in terms of a processing or information flow;

[0014] FIGS. 2A-2C show process flows for correlating and reporting test coverage data according to the invention; and

[0015] FIG. 3 shows a computer system for practicing the invention.

[0016] Referring now to FIG. 1A, a DUT configuration file 100 describing a DUT in terms of the bus transactions that it executes may be processed by a generator program 101 to produce a test case 102 comprising one or more bus transactions. The DUT configuration file may be expressed in a condensed or compact syntax, described in greater detail below, which allows for a description of the bus transactions of a particular bus architecture or of a DUT to be expressed in an economical form suitable for being expanded or enumerated by the generator program. The generator program forms transaction parameter combinations and tests them against rules to determine whether a combination should be included in a test case, as described in more detail hereinafter.

[0017] The test case 102 is typically expressed as bus functional language statements as in the example given above. As shown in FIG. 1B, the test case may be applied by a BFM or hardware device 103 to a DUT 106 for verification; reference numeral 105 refers to either a logic simulator for simulating an HDL model of the DUT, or a hardware environment including a physical embodiment of the DUT 106. Known monitoring or trace mechanisms can capture the bus transactions applied by the test case in an incremental test coverage file 104.

[0018] Subsequently, as shown in FIG 1C, the incremental test coverage file 104 may be processed by a correlator 107 according to the invention. The correlator 107 produces a cumulative test coverage file 108, which is provided as a feedback input to the correlator along with the incremental test coverage file. A coverage report 109, detailing the extent of test coverage achieved for the DUT 106, along with remaining transactions or test cases needed to accomplish full coverage, may be generated from the cumulative test coverage file 108.

[0019] In operation, the correlator correlates or compares the information in the incremental test coverage file 104 and the cumulative test coverage file 108 with information that it derives from the DUT configuration file 100. Similarly to the generator 101 described above, the correlator forms transaction parameter combinations and tests them against rules as specified in the DUT configuration file. The parameter combinations and rules are specific to a particular DUT and describe a DUT-to-bus interface for the bus architecture that is or will be used with the DUT. More specifically, the correlator forms possible parameter combinations as defined in the configuration file, and the rules filter out parameter combinations that are invalid for a particular DUT. Thus, those parameter combinations that are allowed by the rules represent all the valid transactions for the DUT.

[0020] In comparing the valid transactions derived from the DUT configuration file with the information in the incremental test coverage file 104 and cumulative test coverage file 108, the correlator determines which of the valid transaction set of the DUT have been applied in test cases, and which have not. It also detects invalid or unknown bus transactions. The correlator outputs this information cumulatively to the cumulative test coverage file 108. Thus, an extent of test coverage of the DUT, up to the point of a particular execution of the correlator, and those remaining transactions, if any, which are needed to effect complete coverage can be readily determined and reported in a coverage report 109.

[0021] As noted above, a condensed or compact syntax for the configuration file according to the invention allows for a description of a DUT, in terms of the bus transactions it performs, to be expressed in an economical form with a minimum of effort and probability of coding error. The DUT file may, among other uses, be used by the generator 101 to generate a test case 102. The correlator 107 functions similarly to generator in that it generates possible bus transactions filtered by rules, but includes the function of correlating or comparing generated bus transactions to the incremental and cumulative test coverage files to determine test coverage.

[0022] A description of a possible embodiment of the configuration file syntax follows. Comments are indicated by “//”. It is noted that the form of the syntactical statements described is arbitrary and merely representative of functionality which could be implemented in a wide variety of symbolic formulations suitable for being parsed by a parsing routine.

[0023] configuration [name]

[0024] This syntactical statement specifies a bus architecture type. Each bus architecture is characterized by a set of transactions, and typically a subset of those transactions constitutes an interface with a given DUT.

[0025] path [device_path]

[0026] This syntactical statement specifies a logical path in a testing system hierarchy to a device or software entity, such as a BFM, that is used to apply a test case to a DUT.

[0027] device_type[name]

[0028] This syntactical statement specifies a type of device in a given bus architecture, such as a slave, master or arbiter, used to apply a test case to a DUT.

[0029] trans_type

[0030] [command1] [command2] [command3] . . .

[0031] end_trans_type

[0032] This syntactical statement specifies bus transaction types (“command”). Examples include “read” and “write”. The correlator will generate bus transactions of the transaction types and including parameter combinations as determined by a command statement, discussed below.

[0033] generate

[0034] // specification of a list of transaction types

[0035] list [command1] [command2] [command3] . . .

[0036] // specification of an integer=n, where n is a number of transaction types to be selected at random from the trans_type list

[0037] uniform [integer]

[0038] end generate

[0039] This syntactical statement specifies a way in which bus transaction types are generated by the correlator program. In the list format, a user lists transaction types. The correlator will generate all the possible combinations of the listed transaction types, along with associated parameters as specified by the command statement described below.

[0040] An alternative format for the generate syntactical statement is to specify the keyword uniform followed by an integer. This format will cause the specified integer number of transaction types to be selected at random from the list set forth in the trans_type statement.

[0041] command

[0042] // for an enumerated list

[0043] [parameter name] [enum] [item1] [item2] [item3] . . .

[0044] // for a range of values, or a uniform random distribution within a range

[0045] [parameter name] [uniform or range] [min_value] [max_value] [step]

[0046] /step_value]

[0047] // for type range: step and step_value are optional

[0048] end command

[0049] This syntactical statement allows a user to specify all of the parameters, and all of the possible parameter values for each parameter, that are valid for a given bus architecture.

[0050] Following the command identifier are parameter combination specifications. Possible formats for specifying parameter combinations include enum, uniform, and range, as shown. For parameter combination specifications of type enum, the parameter values follow the keyword enum in the form of an enumeration list. As discussed in greater detail below, when the correlator processes a parameter combination specification of the enum type, it will combine each of the listed parameter values with other parameter specifications of the command statement using an enumeration routine. Depending upon applied rules, the correlator will filter out invalid combinations.

[0051] For parameter combination specifications of type uniform and range, a user specifies minimum (min_value) and maximum (max_value) values following the corresponding keyword. For specifications of type uniform, the correlator will choose a random value between the minimum and maximum values when generating parameter combinations.

[0052] For specifications of type range, a user may choose a step value or increment between the minimum and maximum values. This is accomplished through the use of the step keyword followed by a value indicating the step value (step_value). When processing parameter combination specifications of type range, the correlator sets the parameter to the minimum range value and then increments the value by the specified step value to generate parameter combinations. The step and step_value keywords are optional. If step and step_value are not included within the parameter combination specification, then the step_value defaults to 1 and all possible values within the minimum and maximum values are generated.

[0053] Different formats may be used for range and uniform specifications, including decimal, binary, and hexadecimal. To specify a format, special characters may be included before the min_value and max_value keywords. Hexadecimal may be chosen by including an “x” character and binary by including a “b”. Preferably, decimal is the default.

[0054] Examples:

[0055] x10 // hexadecimal value, equal to 16 decimal

[0056] b10 // binary value, equal to 2 decimal

[0057] 10 // decimal value

[0058] rule [include or exclude] [rule_name] // optional rule specifications

[0059] [eq or ne] [parameter name] [item 1] [item2] [item3]

[0060] [lt or gt] [parameter name] [value]

[0061] [eq or ne] [parameter name] [mask] [mask_value] [value] [test_value]

[0062] end_rule

[0063] This syntactical statement allows a user to restrict the total set of bus transactions generated, as defined by the command specifications, to be used in determining test coverage. Rules may specify the actions exclude or include to exclude or include, respectively, a combination of parameters and parameter values for the bus transactions, based upon the results of tests specified by the user. The tests include different types of relational operators, such as: equal (eq), not equal (ne), less than (lt), or greater than (gt).

[0064] In the first format shown above for specifying a test (the line reading [eq or ne] [parameter name] [item 1] [item2] [item3]), each combination of a list item ([item 1], [item2], or [item3]) with [parameter name] is compared to a generated combination using the specified relational operator [eq or ne]. Each test returns a true condition or a false condition.

[0065] In the second format shown (the line reading [lt or gt] [parameter name] [value]), [parameter name] is compared with [value] using the specified relational [lt or gt]. Each test returns a true condition or a false condition.

[0066] In the third format shown, tests may be specified using a mask format. With the mask format, the value specification is masked with the mask_value specification. The result is then tested against test_value using the appropriate relational operator (eq or ne).

[0067] If all the tests specified in a rule return a true condition, then the specified action is performed. That is, if all tests return a true condition and the rule specifies include, the parameter combination is used by the correlator as a valid transaction. If the rule specifies exclude, the parameter combination is not used.

[0068] If any test returns a false condition, then the action opposite to the action specified is performed. That is, if any test returns a false condition and the action specified is include, the parameter combination is excluded. If the action specified is exclude, the parameter combination is included as a valid transaction.

[0069] If more than one rule is stated in a configuration file, a first logical AND operation is performed with the conditions returned by evaluating all the tests specified for exclude actions. A logical OR operation is performed with the conditions returned by evaluating all the tests specified for include actions.

[0070] Then, a second logical AND operation is performed with results of the first logical AND and the logical OR operations. The second logical AND operation returns a true or false condition to determine whether to include the parameter combination or combinations for which rules are specified.

[0071] If no rules are included in a configuration file, all the parameter combinations corresponding to the command statement specification are generated or enumerated. As described above, the iterations statement may limit the number of transactions generated.

[0072] rule [NA] [parameter name] (optional)

[0073] [eq or, ne] [parameter name] [item1] [item2] [item3]

[0074] [lt or gt] [parameter name] [value]

[0075] [eq or ne] [parameter name] [mask] [mask_value] [value] [test_value]

[0076] end_rule

[0077] This syntactical statement allows for the omitting of certain parameters under specific conditions during parameter generation. The tests under the NA (Not Applicable) formulation use relational operators as in the include/exclude rules described above.

[0078] In order for a parameter to be evaluated as Not Applicable and therefore excluded as a valid transaction by the correlator, all the tests specified must return a true condition. If this true condition occurs, the parameter name specified in [parameter name] is excluded from a currently selected list of parameter values generated by the correlator. The NA formulation for a rule serves to filter single parameters located within the currently selected list.

[0079] end_configuration

[0080] This syntactical statement denotes the ending of the configuration file.

[0081] In an embodiment, the incremental test coverage and cumulative test coverage files comprise BFL statements as shown above in the example in the background description. Another example follows:

[0082] Incremental Test Coverage File

[0083] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0084] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0085] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0086] write(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0087] The above BFL statements represent bus transactions captured during the application of test case.

[0088] Cumulative Test Coverage File

[0089] [FOUND][40]:read(addr=ff, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0090] [DUPLICATE][40]:read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0091] [MISSING][0]:read(addr=dd, data=dddddddd, req_delay=2, ctr_assert_delay=2)

[0092] [UNKNOWN]:write(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0093] The above lines represent BFL statements to which identifying information has been added by the correlator. The identifier “FOUND” indicates that the correlator found a match for a valid transaction that it generated in the incremental test coverage or cumulative test coverage file, meaning that the transaction has been applied and may be incremented to a tally of test coverage.

[0094] The identifier “DUPLICATE” indicates that the correlator encountered a transaction that it had already identified as “FOUND”.

[0095] The identifier “MISSING” indicates that the correlator generated a valid transaction for which it found no match in the incremental test coverage or cumulative test coverage files, meaning that this is a transaction that must be applied in a test case to obtain complete coverage.

[0096] The identifier “UNKNOWN” indicates that the correlator encountered a transaction in the incremental test coverage or cumulative test coverage files that it did not recognize.

[0097] FIGS. 2A-2C show a process flow for the correlator 101, given a DUT configuration file 100 specified in the above-described syntax, a incremental test coverage file 104 and a cumulative test coverage file 108 as input.

[0098] As shown in block 200 of FIG. 2A, the correlator reads in the cumulative test coverage file 108. The correlator loops through the cumulative test coverage file to recover only those lines identified as “FOUND” and discard the rest, as shown in blocks 202 through 204. The “FOUND” entries represent cumulative test coverage up to the current execution of the correlator.

[0099] Then, as shown in blocks 206-207, the correlator reads in the incremental test coverage file 104 and merges it with the “FOUND” entries.

[0100] The correlator then proceeds to generate the valid bus transactions of the DUT and correlate or compare the generated transactions with the merged incremental and cumulative test coverage files. Referring now to FIG. 2B, as shown in block 208, initially the correlator parses the configuration file 100 and initializes parameter values. All range specifications are set to their respective lower limits, or min_values, and all enumeration lists are set to their first listed item.

[0101] In order to systematically enumerate each possible parameter combination, the correlator assigns a significance level to each parameter combination specification in a command statement, based on its place in a sequence within the command statement. In an embodiment, the parameter combination specification last in the sequence is the least significant, the next-to-last parameter combination specification is next-to-least significant, and so on up to the first or most significant specification in the sequence.

[0102] As shown in block 209, enumeration or generation of parameter combinations begins with the level of least significance (initially the “next” significance level is the least significant level). As shown in block 210, the correlator combines parameter values at each significance level, at their current state, to form a parameter combination.

[0103] As each parameter combination in the command statement is generated, it is checked against any rules which may be defined in the configuration file, as shown in block 211. If the generated parameter combination is not excluded by a rule, the parameter combination is correlated or compared with the BFL in the merged cumulative and incremental test coverage files, as shown in block 212. If the combination is excluded by a rule, the flow proceeds to block 214.

[0104] FIG. 2C shows a process flow for a possible implementation of block 212. As shown in block 218, the correlator compares a valid bus transaction parameter combination with the merged cumulative and incremental test coverage files. As shown in blocks 219, 220, 222 and 223, if there is a match with a record in the cumulative or incremental test coverage files, the correlates determines whether the record is a duplicate or not, adds the information to the record accordingly, and outputs it to the correlator output 108.

[0105] Otherwise, as shown in block 221, it is determined if a valid parameter combination is missing from the incremental and cumulative test coverage files, or if a record is present in the incremental or cumulative test coverage files that does not correspond to a valid parameter combination. If the parameter combination is valid but missing, this information is added to the valid parameter combination and the combination is outputted it to the correlator output, as shown in blocks 224 and 108. If a parameter combination is detected in the incremental or cumulative test coverage files for which there is no match with a valid combination, it is designated “UNKNOWN” and written to the correlator output as shown in blocks 225 and 108.

[0106] Returning now to FIG. 2B, at block 214, the correlator checks for whether an upper limit of a specified range has been reached within the current significance level. In the case of an enumeration list, the correlator checks for whether all items of the list have been visited or traversed.

[0107] As shown in block 215, if within the current significance level the upper limit of a range has not been reached or all the items of an enumeration list have not been traversed, the parameter value of the range is updated (by step_value if specified or by 1 if not) or the next list item is fetched or visited. Then, the resulting parameter combination is checked against the rules, if any.

[0108] When the upper limit of a range is reached or all list items of an enumeration list have been traversed, the correlator moves up to the next significance level. As shown in block 216, if all significance levels have been processed, the correlator is finished and exits. If not, as shown in block 217 the correlator resets all levels of lesser significance than the next level to be processed to their initial values, i.e., to the lower limit of a range or to the first item in an enumeration list, and processes the next level.

[0109] It may be observed that the foregoing resembles the functioning of a mileage odometer, in that digits of an odometer, corresponding to significance levels in the above, run through all possible values, beginning with the least significant digit.

[0110] The following is an illustrative example of the foregoing enumeration process:

[0111] command

[0112] address range x0A x0C

[0113] // The above is a command statement in the configuration file syntax. The first and

[0114] // most significant parameter combination specification is a range type of

[0115] // specification for parameter name=address. The lower limit or min_value for the

[0116] // range is x0A, and the upper limit or max_value is x0C. No step value is specified,

[0117] // so beginning with the lower limit, the range will be incremented by the default step

[0118] // value which is 1;

[0119] be enum 000 111

[0120] // The above is an enum or enumeration list type of parameter combination

[0121] // specification for parameter name=be (byte enable) comprising two list items, 000

[0122] // and 111. This is the least significant parameter combination specification in the

[0123] // command statement;

[0124] end_command

[0125] From the above command specification, the correlator would produce the following parameter combinations:

[0126] address=0A, be=000

[0127] address=0A, be=111

[0128] address=0B, be=000

[0129] address=0B, be=111

[0130] address=0C, be=000

[0131] address=0C, be=111

[0132] As can be seen, the correlator traversed the least significant level first, pairing each list value with the initial range value, 0A, of the next significance level. Then, the next significance level was processed. The range value was incremented to 0B, the level of lower significance was reset to its initial value, and the correlator produced the next possible combinations. Finally, the upper limit, 0C, of the most significant level was reached and each combination at that level was generated.

[0133] The following is an example of application of a rule in a configuration file to the above-described command definition:

[0134] rule exclude

[0135] eq address x0C

[0136] eq be 111

[0137] end_rule

[0138] In the above rule specification, the specified tests are that if a parameter combination having an address equal (eq) to x0C and a “be” parameter equal to 111 is generated, the combination is to be excluded, i.e., not considered valid by the correlator. Thus, if this rule was present in the configuration file with the above command definition, the correlator would produce the following valid combinations:

[0139] address=0A, be=000

[0140] address=0A, be=111

[0141] address=0B, be=000

[0142] address=0B, be=111

[0143] address=0C, be=000

[0144] It can be seen that, because both tests returned a true condition for the parameter combination “address=0C, be=111”, this combination was excluded.

[0145] The following are an example incremental test coverage file, DUT configuration file, and resulting correlator output. The cumulative test coverage file may be assumed to have an initialized or empty status:

[0146] Incremental Test Coverage File

[0147] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0148] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0149] read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0150] write(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0151] read(addr=ff, data=eeeeeeee, req_delay=2, ctr_assert_delay=3)

[0152] read(addr=ff, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0153] read(addr=ff, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0154] read(addr=ff, data=eeeeeeee, req_delay=6, ctr_assert_delay=2)

[0155] read(addr=ff, data=eeeeeeee, req_delay=6, ctr_assert_delay=3)

[0156] read(addr=ff, data=ffffffff, req_delay=2, ctr_assert_delay=2)

[0157] read(addr=ff, data=ffffffff, req_delay=2, ctr_assert_delay=3)

[0158] read(addr=ff, data=ffffffff, req_delay=4, ctr_assert_delay=2)

[0159] read(addr=ff, data=ffffffff, req_delay=4, ctr_assert_delay=3)

[0160] read(addr=ff, data=ffffffff, req_delay=6, ctr_assert_delay=2)

[0161] read(addr=ff, data=ffffffff, req_delay=6, ctr_assert_delay=3)

[0162] DUT Configuration File

[0163] configuration dcr_device

[0164] path/dcr_complex/m0/master

[0165] device_type dcr_master

[0166] trans_type

[0167] read

[0168] end_trans_type

[0169] generate

[0170] list read // default that generates a read followed by a write

[0171] end_generate

[0172] command

[0173] addr enum dd ee ff

[0174] data enum dddddddd eeeeeeee ffffffff

[0175] req_delayenum 2 4 6

[0176] ctr_assert_delay enum 2 3

[0177] end_command

[0178] end_configuration

[0179] Correlator Output (Cumulative Test Coverage) File

[0180] [FOUND][40]:read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0181] [DUPLICATE][40]:read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0182] [DUPLICATE][40]:read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0183] [UNKNOWN]:write(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0184] [FOUND][64]:read(addr=ff, data=eeeeeeee, req_delay=2, ctr_assert_delay=3)

[0185] [FOUND][66]:read(addr=ff, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0186] [FOUND][67]:read(addr=ff, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0187] [FOUND][69]:read(addr=ff, data=eeeeeeee, req_delay=6, ctr_assert_delay=2)

[0188] [FOUND][70]:read(addr=ff, data=eeeeeeee, req_delay=6, ctr_assert_delay=3)

[0189] [FOUND][72]:read(addr=ff, data=ffffffff, req_delay=2, ctr_assert_delay=2)

[0190] [FOUND][73]:read(addr=ff, data=ffffffff, req_delay=2, ctr_assert_delay=3)

[0191] [FOUND][75]:read(addr=ff, data=ffffffff, req_delay=4, ctr_assert_delay=2)

[0192] [FOUND][76]:read(addr=ff, data=ffffffff, req_delay=4, ctr_assert_delay=3)

[0193] [FOUND][78]:read(addr=ff, data=ffffffff, req_delay=6, ctr_assert_—delay=2)

[0194] [FOUND][79]:read(addr=ff, data=ffffffff, req_delay=6, ctr_assert_delay=3)

[0195] [MISSING][0]:read(addr_dd, data=dddddddd, req_delay=2, ctr_assert_delay=2)

[0196] [MISSING][1]:read(addr=dd, data=dddddddd, req_delay=2, ctr_assert_delay=31)

[0197] [MISSING][2]:read(addr=dd, data=dddddddd, req_delay=2)

[0198] [MISSING][3]:read(addr=dd, data=dddddddd, req_delay=4, ctr_assert_delay=2)

[0199] [MISSING][4]:read(addr=dd, data=dddddddd, req-delay=4, ctr-assert-delay=3)

[0200] [MISSING][5]:read(addr=dd, data=dddddddd, req_delay=4)

[0201] [MISSING][6]:read(addr=dd, data=dddddddd, req_delay=6, ctr_assert_delay=2)

[0202] [MISSING][7]:read(addr=dd, data=dddddddd, req_delay=6, ctr_assert_delay=3)

[0203] [MISSING][8]:read(addr_dd, data=dddddddd, req_delay=6)

[0204] [MISSING][9]:read(addr=dd, data=eeeeeeee, req_delay=2, ctr_assert_delay=2)

[0205] [MISSING][10]:read(addr=dd, data=eeeeeeee, req_delay=2, ctr_assert_delay=3)

[0206] [MISSING][11]:read(addr=dd, data=eeeeeeee, req_delay=2)

[0207] [MISSING][12]:read(addr=dd, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0208] [MISSING][13]:read(addr=dd, data=eeeeeeee, req_delay=4, ctr_assert_delay=3)

[0209] [MISSING][14]:read(addr=dd, data=eeeeeeee, req_delay=4)

[0210] [MISSING][15]:read(addr=dd, data=eeeeeeee, req_delay=6, ctr_assert_delay=2)

[0211] [MISSING][16]:read(addr=dd, data=eeeeeeee, req_delay=6, ctr_assert_delay=3)

[0212] [MISSING][17]:read(addr=dd, data=eeeeeeee, req_delay=6)

[0213] [MISSING][18]:read(addr=dd, data=ffffffff, req_delay=2, ctr_assert_delay=2)

[0214] [MISSING][19]:read(addr=dd, data=ffffffff, req_delay=2, ctr_assert_delay=3)

[0215] [MISSING][20]:read(addr=dd, data=ffffffff, req_delay=2)

[0216] [MISSING][21]:read(addr=dd, data=ffffffff, req-delay=4, ctr_assert_delay=2)

[0217] [MISSING][22]:read(addr=dd, data=ffffffff, req_delay=4, ctr_assert_delay=3)

[0218] [MISSING][23]:read(addr=dd, data=ffffffff, req_delay=4)

[0219] [MISSING][24]:read(addr=dd, data=ffffffff, req_delay=6, ctr_assert_delay=2)

[0220] [MISSING][25]:read(addr=dd, data=ffffffff, req_delay=6, ctr_assert_delay=3)

[0221] [MISSING][26]:read(addr=dd, data=ffffffff, req_delay=6)

[0222] [MISSING][27]:read(addr=ee, data=dddddddd, req_delay=2, ctr_assert_delay=2)

[0223] [MISSING][28]:read(addr=ee, data=dddddddd, req_delay=2, ctr_assert_delay=3)

[0224] [MISSING][29]:read(addr=ee, data=dddddddd, req_delay=2)

[0225] [MISSING][30]:read(addr=ee, data=dddddddd, req_delay=4, ctr_assert_delay=2)

[0226] [MISSING][31]:read(addr=ee, data=dddddddd, req_delay=4, ctr_assert_delay=3)

[0227] [MISSING][32]:read(addr=ee, data=dddddddd, req_delay=4)

[0228] [MISSING][33]:read(addr=ee, data=dddddddd, req_delay=6, ctr_assert_delay=2)

[0229] [MISSING][34]:read(addr=ee, data=dddddddd, req_delay 6, ctr_assert_delay=3)

[0230] [MISSING][35]:read(addr=ee, data=dddddddd, req_delay=6)

[0231] [MISSING][36]:read(addr=ee, data=eeeeeeee, req_delay=2, ctr_assert_delay=2)

[0232] [MISSING][37]:read(addr=ee, data=eeeeeeee, req_delay=2, ctr_assert_delay=3)

[0233] [MISSING][38]:read(addr=ee, data=eeeeeeee, req_delay=2)

[0234] [MISSING][39]:read(addr=ee, data=eeeeeeee, req_delay=4, ctr_assert_delay=2)

[0235] [MISSING][41]:read(addr=ee, data=eeeeeeee, req_delay=4)

[0236] [MISSING][42]:read(addr=ee, data=eeeeeeee, req_delay=6, ctr_assert_delay=2)

[0237] [MISSING][43]:read(addr=ee, data=eeeeeeee, req_delay=6, ctr_assert_delay=3)

[0238] [MISSING][44]:read(addr=ee, data=eeeeeeee, req_delay=6)

[0239] [MISSING][45]:read(addr=ee, data=ffffffff, req_delay=2, ctr_assert_delay=2)

[0240] [MISSING][46]:read(addr=ee, data=ffffffff, req_delay=2, ctr_assert_delay=3)

[0241] [MISSING][47]:read(addr=ee, data=ffffffff, req_delay=2)

[0242] [MISSING][48]:read(addr=ee, data=ffffffff, req_delay=4, ctr_assert_delay=2)

[0243] [MISSING][49]:read(addr=ee, data=ffffffff, req_delay=4, ctr_assert_delay=3)

[0244] [MISSING][50]:read(addr=ee, data=ffffffff, req_delay=4)

[0245] [MISSING][51]:read(addr=ee, data=ffffffff, req_delay=6, ctr_assert_delay=2)

[0246] [MISSING][52]:read(addr=ee, data=ffffffff, req_delay=6, ctr_assert_delay=3)

[0247] [MISSING][53]:read(addr=ee, data=ffffffff, req_delay=6)

[0248] [MISSING][54]:read(addr=ff, data=dddddddd, req_delay=2, ctr_assert_delay=2)

[0249] [MISSING][55]:read(addr=ff, data=dddddddd, req_delay=2, ctr_assert_delay=3)

[0250] [MISSING][56]:read(addr=ff, data=dddddddd, req_delay=2)

[0251] [MISSING][57]:read(addr=ff, data=dddddddd, req-delay=4, ctr_assert_delay=2)

[0252] [MISSING][58]:read(addr=ff, data=dddddddd, req-delay=4, ctr_assert_delay=3)

[0253] [MISSING][59]:read(addr=ff, data=dddddddd, req_delay=4)

[0254] [MISSING][60]:read(addr=ff, data=dddddddd, req_delay=6, ctr_assert_delay=2)

[0255] [MISSING][61]:read(addr=ff, data=dddddddd, req_delay=6, ctr_assert_delay=3)

[0256] [MISSING][62]:read(addr=ff, data=dddddddd, req_delay=6)

[0257] [MISSING][63]:read(addr=ff, data=eeeeeeee, req_delay=2, ctr_assert_delay=2)

[0258] [MISSING][65]:read(addr=ff, data=eeeeeeee, req_delay=2)

[0259] [MISSING][68]:read(addr=ff, data=eeeeeeee, req_delay=4)

[0260] [MISSING][71]:read(addr=ff, data=eeeeeeee, req_delay=6)

[0261] [MISSING][74]:read(addr=ff, data=ffffffff, req_delay=2)

[0262] [MISSING][77]:read(addr=ff, data=ffffffff, req_delay=4)

[0263] [MISSING][80]:read(addr=ff, data=ffffffff, req_delay=4)

[0264] It can be seen from the first three lines of the correlator output that the correlator detected a valid transaction in the incremental test coverage file, and then two duplicates of that transaction. The fourth line identifies the write transaction in the incremental test coverage file as “UNKNOWN”, since the DUT configuration file only generated read transactions.

[0265] The lines following the “UNKNOWN” transaction and identified as “FOUND” can be seen to correspond to each of the BFL statements of the incremental test coverage file. These transactions can be accreted toward total test coverage.

[0266] The lines identified as “MISSING” can be seen to correspond to parameter combinations generated by the correlator from the example DUT configuration file, but which were absent from the incremental test coverage file. These are transactions which must be applied in a test cases or cases to provide complete coverage.

[0267] FIG. 3 shows a high-level representation of a computer system for implementing a preferred embodiment of the present invention, such as might be realized by a variety of known and commercially available hardware and software elements as embodied in, for example, a UNIX® workstation. The system comprises a memory 300 including ROM and RAM, processor 310 and user interface 311 comprising a video display 312, keyboard 313 and mouse 314. Elements may communicate via system bus 309. The system may further comprise a network 317 connected by a network medium 318 and network interface 319.

[0268] A computer program or collection of programs comprising computer-executable instructions for performing method steps according to the present invention may be stored and transported on computer-usable media such as diskette 301, CD-ROM 302, magnetic tape 303 and fixed disk 304. To perform the steps of the method, computer instructions according to the present invention may be retrieved from the computer-usable media 301-304 using their respective drives 305-308 into memory 300, and executed by a processor 310. The process steps and functionality disclosed hereinabove for performing the method may find specific implementations in a variety of forms, which are considered to be within the abilities of a programmer of ordinary skill in the art after having reviewed the specification.

[0269] The foregoing description of the invention illustrates and describes the present invention. Additionally, the disclosure shows and describes only the preferred embodiments of the invention, but it is to be understood that the invention is capable of use in various other combinations, modifications, and environments and is capable of changes or modifications within the scope of the inventive concept as expressed herein, commensurate with the above teachings, and/or the skill or knowledge of the relevant art. The embodiments described hereinabove are further intended to explain best modes known of practicing the invention and to enable others skilled in the art to utilize the invention in such, or other, embodiments and with the various modifications required by the particular applications or uses of the invention. Accordingly, the description is not intended to limit the invention to the form disclosed herein. Also, it is intended that the appended claims be construed to include alternative embodiments.