In reply to kranthi445:
What defines the end of a test is very design specific. Once you have the definition, we can show you the best way to implement that in UVM. Without knowing more, I can only say the two most popular ways it:
- Define your sequences so they block the sequence is finished. Sometimes this means not calling item_done until the driver is finished sending all the data. You can also add a dummy sequence if the driver can’t do that.
- Put the objection in the scoreboard when there are no more outstanding items to compare. This may require a timeout if there is a problem - you don’t want the test running forever.