A layered testbench separates stimulus, driving, observation, and checking into classes joined by mailboxes. The class world touches the DUT only through virtual interfaces owned by the static harness.
Topic | Lessons | What it covers | Time |
|---|---|---|---|
4 | How a layered testbench is organized, from the static harness to tests and a complete example. | 30 min | |
8 | Stimulus flow plus constraint shaping: transactions, generators, drivers, and closure. | 65 min | |
4 | Passive monitors, scoreboards and reference models that prove a testbench checked the DUT. | 30 min | |
4 | Self-checking tests that print their own verdict, plus seeds, logging, and the regression flow. | 30 min | |
3 | Map each hand-built testbench piece to its UVM counterpart and plan the migration. | 25 min |
The mailbox decouples their timing, so the generator can randomize ahead while the driver consumes transactions at DUT pace. It also lets both run as independent threads.