Q. Why would I use SVUnit?
Good question. You’ll want to use SVUnit if you and your customers value defect free systemverilog code. Simple as that.
Q. What do I do with SVUnit?
The SVUnit framework allows you to easily isolate modules, classes and/or interfaces in your designs and testbenches so you can kill bugs at a granularity that is most productive: the unit test level. It’s good for design and verification engineers. It’s also great for test-driven development if you care enough to prevent defects in the first place.
Q. Why would I not use SVUnit?
A. If you love garbage code and irate customers, then SVUnit is not for you.
Q. How do I get SVUnit?
A. Instructions for downloading and using SVUnit are on the Getting Started page.
Q. It used to be that SVUnit was only available to early adopters. That still the case?
A. Nope… not any more. Now anyone can download SVUnit.
Q. What’s the best way to learn how to use SVUnit?
A. It’s best to start with the Getting Started page.
Q. If I find a problem or have questions about SVUnit, what do I do?
A. Best to file a ticket on GitHub at: https://github.com/nosnhojn/https://github.com/nosnhojn/svunit-code/issues. Or, you can send me an email at firstname.lastname@example.org and I’ll do my best to help you out.
Q. Can anyone file a ticket against the project?
A. Yes… though you’ll have to be logged into GitHub to do so.
Q. How can I connect with other SVUnit users?
A. We have an SVUnit User Group where people can reach out with questions and share their experience. Anyone can join.
Q. How do I use SVUnit with UVM?
A. Specify the -U/–uvm switch on the command line to use the version of UVM supported by the simulator you’re using.