In reply to dave_59:
In reply to Reuben:
In a block level testcase, you need to provide stimulus and response components for blocks that are not part of the simulation. In a System-Level testbench, those components become passive because now you have all the blocks in place. But you still have prove stimulus for the parts of the system that are not being simulated, or whatever is external to the “System” But the monitors and scoreboards you used at the block level can be reused at the system level.
A test vector is older terminology from applying stimulus once cycle at time with all the inputs to the DUT being concatenated into a single “vector”. Typically used in manufacturing tests, not functional verification.
Hi dave,
Thanks for the reply. I also heard some engineers say if your testcase is used in silicon. What is this?
Then there are also testcases that are created from C-language. They use this if the DUT is a microcontroller. What is this? What’s the purpose of using C-Language? Is this what they call a software testing? What is it for?
Regards,
Reuben