What's the best class naming convention for re-usability in higher level testbenches (avoid multiple classes with same names)

In reply to dave_59:

Thanks Dave,

That makes more sense. I’m hoping you might know of an example I could look at that shows this testbench sharing environments from other testbenches, or the superblock made of blocks. I’m wanting a better understanding of the syntax in the top level environment that shows the lower level environment being created. e.g., package_name::lower_env etc…

My goal is to better understand the structure of the environments and how to best name and create them.

Any thoughts on where I might look?
Thanks again,
Brian