Does each test have to be unique

UVM
4

In reply to dave_59:

Dave,

  1. It really does not make sense to everytime creae a new derived config object just to change some constraints and then override original one with this new one in the test. I am really thinking from resuability point of view and also maintainibility of test cases. Imagine each test case should have a different config object name while oberriding. And what if someone forgot to change the override name in a test. Say test1 has config1 and test2 has config2. But while overriding in test2 one by mistake puts override to config1. Then compiler won’t complain as the code for config1 exists in test1.

  2. How about if I want to use external constraint block. Say I have put external constraint blocks in config object and transcation objects.
    I would like to use them to do my random settings in my test. But then in every test I am going to do different settings. Will the compiler not complaint that I have defined multiple external constraint blocks. In anycase, which one will take presedence. The code that executes is only the test that runs. Other tests are just compiled in.

  3. “Each test uses the factory to override the creation of these extended classes. You can automate this be appending the test name to the base class when specifying the override by name”
    Could you point me to some example in line with you above remark?

Appreciate your help.

thanks
shrawan