Five hand-built patterns carry most testbench structure. A disciplined transaction, a factory, a shared config, callbacks and a phased hierarchy compose into one environment, and each pattern resurfaces as a UVM standard.
Lesson | What gets built | Path |
|---|---|---|
Copy, compare, print and pack on one self-contained transaction. | Required | |
A creator registry with explicit registration and test-time overrides. | Required | |
One shared config with protected construction and freeze before build. | Optional | |
Driver hooks with stacked callbacks for injection and sampling. | Recommended | |
A named tree with build, connect and run waves. | Required |
Path labels. Required means core first pass for this topic, Recommended means most learners should read it, and Optional means reference, specialist or revision material you can return to later.
The object and factory, the config database, the callback system and the component phases. UVM standardizes these five patterns, and the bench already runs their hand-built versions.