Unit testing- too much maintenance overhead?

Guest #3714915
Hi, all,
I will be happy to hear your thoughts on this.

I'm working on some complex designs, with ten or more subunits. I know 
its often recommended, in the software world, to do unit level testing, 
as well as design-level testing, but i find that later maintaining those 
testbenches is very time consuming.

so, how do you simulate and test your designs? On what level?
Note - im bot talking about verification here, just testing as part of 
the design process itself.

Thx,
RL
#3717442
If you can simulate (which you most probably refer to as "testing") your 
sub blocks embedded within the higher entity, no problem.

However, sometimes it's easier to simulate lower level entities 
standalone (doing it the "divide and conquer" way). You may better reach 
special conditions and be sure it works before going to a greater 
context. Depends on how complex your "complex designs" are...
#3809747
And of course it's a big difference whether your design goes into an 
FPGA (simulate, among other reasons, to avoid to many synthesis 
iterations) or into an ASIC (full coverage required, as masks are 
expensive) ...

Reply

A question of your own? This thread is over 12 years old. Ask it in a thread of its own – more people read along there, and it gets answered more often and sooner.

Start a new thread

A fix, an addition or feedback on this thread? Then reply here.

Formatting
  • [c]C-Code[/c]
  • [vhdl]VHDL-Code[/vhdl]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.