Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / third_party / svunit / refs/heads/upstream/add-assert-eq-and-assert-neq-macros
commitb46d76f4c4391c065616f14bb67f57542121a3e5[log] [tgz]
authorTudor Timi <tudortimi@users.noreply.github.com>Sat Oct 22 22:46:15 2022 +0300
committerTudor Timi <tudortimi@users.noreply.github.com>Tue Nov 01 20:39:11 2022 +0200
treedd9b26571570fbe03a475f71b8d7e3d57514bd58
parent3d7822b543fcbe0a94bcb345aa51169eb15372d8 [diff]
Use dummy type as default for type parameters that should be passed by macro

This causes a compile error for the test which doesn't specify the type, because we haven't implemented type inference yet.
3 files changed
tree: dd9b26571570fbe03a475f71b8d7e3d57514bd58
  1. .dvt/
  2. .github/
  3. .vscode/
  4. bin/
  5. docs/
  6. examples/
  7. src/
  8. sv_test/
  9. svunit_base/
  10. test/
  11. .editorconfig
  12. .gitignore
  13. AUTHORS
  14. CHANGELOG.md
  15. CONTRIBUTING.md
  16. header.txt
  17. LICENSE.txt
  18. README.md
  19. release.bsh
  20. Setup.bsh
  21. Setup.csh
  22. Setup.zsh
  23. VERSION.txt
README.md

SVUnit

SVUnit is an open-source test framework for ASIC and FPGA developers writing Verilog/SystemVerilog code. SVUnit is automated, fast, lightweight and easy to use making it the only SystemVerilog test framework in existence suited to both design and verification engineers that aspire to high quality code and low bug rates.

NOTE: for instructions on how to get going with SVUnit, go to www.agilesoc.com/svunit.

NOTE: Refer also to the FAQ at: www.agilesoc.com/svunit/svunit-FAQ

Release Notes

Go here for release notes.

Step-by-step instructions to get a first unit test going

1. Set up the SVUNIT_INSTALL and PATH environment variables

export SVUNIT_INSTALL=`pwd`
export PATH=$PATH:$SVUNIT_INSTALL"/bin"

You can source Setup.bsh if you use the bash shell.

source Setup.bsh

You can source Setup.csh if you use the csh shell.

source Setup.csh

2. Go somewhere outside SVUNIT_INSTALL (i.e. where you are right now)

Start a class-under-test:

// file: bogus.sv
class bogus;
endclass

3. Generate the unit test

create_unit_test.pl bogus.sv

4. Add tests using the helper macros

// file: bogus_unit_test.sv
`SVUNIT_TESTS_BEGIN

  //===================================
  // Unit test: test_mytest
  //===================================
  `SVTEST(test_mytest)
  `SVTEST_END

`SVUNIT_TESTS_END

5. Run the unit tests

runSVUnit -s <simulator> # simulator is ius, questa, modelsim, riviera or vcs

6. Repeat steps 4 and 5 until done

7. Pat self on back