| Name | svut JSON |
| Version |
1.9.1
JSON |
| download |
| home_page | https://github.com/dpretet/svut |
| Summary | SystemVerilog Unit Test (SVUT) |
| upload_time | 2024-06-27 11:44:51 |
| maintainer | None |
| docs_url | None |
| author | Damien Pretet |
| requires_python | <4,>=3.7 |
| license | The MIT License Copyright (c) 2022 The SVUT Authors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
verilog
systemverilog
testing
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# SystemVerilog Unit Test (SVUT)
[](https://github.com/dpretet/svut/blob/master/LICENSE)
[](https://github.com/dpretet/svut/issues)
[](https://github.com/dpretet/svut/stargazers)
[](https://github.com/dpretet/svut/network)
[](https://twitter.com/intent/tweet?text=Wow:&url=https%3A%2F%2Fgithub.com%2Fdpretet%2Fsvut)
## Introduction
SVUT is a very simple flow to create a Verilog/SystemVerilog unit test. It is
widely inspired by [SVUnit](http://agilesoc.com/open-source-projects/svunit/),
but it's written in python and run with [Icarus
Verilog](http://iverilog.icarus.com/). SVUT follows KISS principle: [Keep It
Simple, Stupid](https://en.wikipedia.org/wiki/KISS_principle).
Hope it can help you!
### How to Install
#### Pypi
SVUT is availble on Pypi and can be installed as following:
```bash
pip3 install svut
```
#### Git
Git clone the repository in a path. Set up the SVUT environment variable
and add SVUT to `$PATH`:
```bash
export SVUT=$HOME/.svut
git clone https://github.com/dpretet/svut.git $SVUT
export PATH=$SVUT:$PATH
```
SVUT relies on [Icarus Verilog](http://iverilog.icarus.com/) as simulation
back-end. Please install it with your favourite package manager and be sure to
use a version greater or equal to v10.2. SVUT is tested with `v10.2` and cannot
work with with lower version (`<= v9.x`).
SVUT can also use [Verilator](https://github.com/verilator/verilator) but the support
is more limited for the moment. A future release will fix that. An example to understand
how to use it along Icarus can be found [here](https://github.com/dpretet/friscv/tree/master/test/common)
### How to use it
To create a unit test of a verilog module, call the command:
```bash
svutCreate your_file.v
```
No argument is required. SVUT will create "your_file_testbench.sv" which contains your module
instanciated and a place to write your testcase(s). Some codes are also commented to describe the
different macros and how to create a clock or dump a VCD for GTKWave. To run a test, call the
command:
```bash
svutRun -test your_file_testbench.sv
```
or simply `svutRun` to execute all testbenchs in the current folder.
```bash
svutRun
```
SVUT will scan your current folder, search for the files with "\_testbench.sv"
suffix and run all tests available. Multiple suffix patterns are [possible](https://github.com/dpretet/svut/blob/master/svutRun.py#L46).
svutRun proposes several arguments, most optional:
- `-test`: specify the testsuite file path or a folder containing tests
- `-f`: pass the fileset description, default is `files.f`
- `-sim`: specify the simulator, `icarus` or `verilator`
- `-main`: specify the main.cpp file when using verilator, default is `sim_main.cpp`
- `-define`: pass verilog defines to the tool, like `-define "DEF1=2;DEF2;DEF3=3"`
- `-vpi`: specify a compiled VPI, for instance `-vpi "-M. -mMyVPI"`
- `-dry-run`: print the commands but don't execute them
- `-include`: to pass include path, several can be passed like `-include folder1 folder2`
- `-no-splash`: don't print SVUT splash banner, printed by default
- `-compile-only`: just compile the testbench, don't execute it
- `-run-only`: just execute the testbench, if no executable found, also build it
# Tutorial
Copy/paste this basic FFD model in a file named ffd.v into a new folder:
```verilog
`timescale 1 ns / 1 ps
module ffd
(
input wire aclk,
input wire arstn,
input wire d,
output reg q
);
always @ (posedge aclk or negedge arstn) begin
if (arstn == 1'b0) q <= 1'b0;
else q <= d;
end
endmodule
```
Then run:
```bash
svutCreate ffd.v
```
ffd_testbench.v has been dropped in the folder from you called svutCreate. It
contains all you need to start populating your testcases. In the header, you
can include directly your DUT file (uncomment):
```verilog
`include "ffd.v"
```
or you can store the path to your file into a `files.f` file, automatically
recognized by SVUT. Populate it with the files describing your IP. You can
also specify include folder in this way:
```bash
+incdir+$HOME/path/to/include/
```
Right after the module instance, you can use the example to generate a clock
(uncomment):
```verilog
initial aclk = 0;
always #2 aclk <= ~aclk;
```
Next line explains how to dump your signals values into a VCD file to open a
waveform in GTKWave (uncomment):
```verilog
initial $dumpvars(0, ffd_unit_test);
initial $dumpfile("ffd_testbench.vcd");
```
Two functions follow, `setup()` and `teardown()`. Use them to configure the
environment of the testcases:
- setup() is called before each testcase execution
- teandown() after each testcase execution
A testcase is enclosed between to specific defines:
```verilog
`UNIT_TEST("TESTNAME")
...
`UNIT_TEST_END
```
TESTNAME is a string (optional), which will be displayed when test execution
will start. Then you can use the macros provided to display information,
warning, error and check some signals status and values. Each error found with
macros increments an error counter which determine a testcase status. If the
error counter is bigger than 0, the test is considered as failed.
A testsuite, comprising several `UNIT_TEST` is declared with another define:
```verilog
`TEST_SUITE("SUITENAME")
...
`TEST_SUITE_END
```
To test the FFD, add the next line into `setup()` to drive the reset and init the
FFD input:
```verilog
arstn = 1'b0;
d = 1'b0;
#100;
arstn = 1'b1;
```
and into the testcase:
```verilog
`FAIL_IF(q);
```
Here is a basic unit test checking if the FFD output is 0 after reset. Once
called `svutRun` in your shell, you should see something similar:
```
INFO: Start testsuite << FFD Testsuite >> (@ 0)
INFO: Starting << Test 0: Check reset is applied >> (@ 0)
I will test if Q output is 0 after reset (@ 100000)
SUCCESS: Test 0 pass (@ 110000)
INFO: Starting << Test 1: Drive the FFD >> (@ 110000)
I will test if Q output is 1 after D assertion (@ 210000)
SUCCESS: Test 1 pass (@ 236000)
INFO: Stop testsuite 'FFD Testsuite' (@ 236000)
- Warning number: 0
- Critical number: 0
- Error number: 0
- STATUS: 2/2 test(s) passed
```
SVUT relies (optionally) on files.f to declare fileset and define. The user
can also choose to pass define in the command line:
```bash
svutRun -test my_testbench.sv -define "DEF1=1;DEF2;DEF3=3"
```
SVUT doesn't check possible collision between define passed in command line
and the others defined in files.f. Double check that point if unexpected
behavior occurs during testbench.
Finally, SVUT supports VPI for Icarus. Follow an example to compile and set up
the flow of an hypothetic UART, compiled with iverilog and using a define "PORT":
```bash
iverilog-vpi uart.c
svutRun -vpi "-M. -muart" -define "PORT=3333" -t ./my_testbench.sv &
```
Now you know the basics of SVUT. The generated testbench provides prototypes of
available macros. Try them and play around to test SVUT. You can find these
files into the example folder.
Enjoy!
## License
Copyright 2021 The SVUT Authors
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. imitations under the License.
Raw data
{
"_id": null,
"home_page": "https://github.com/dpretet/svut",
"name": "svut",
"maintainer": null,
"docs_url": null,
"requires_python": "<4,>=3.7",
"maintainer_email": null,
"keywords": "verilog, systemverilog, testing",
"author": "Damien Pretet",
"author_email": "Damien Pretet <damien.pretet@me.com>, Sarah Clark <sarahclark@google.com>, Sebastian Schaetz <seb.schaetz@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/44/bf/0135a4925ccaab04dc99a8c324fc0d85b9ef93d37840995e8934bd80daa1/svut-1.9.1.tar.gz",
"platform": null,
"description": "# SystemVerilog Unit Test (SVUT)\n\n[](https://github.com/dpretet/svut/blob/master/LICENSE)\n\n\n[](https://github.com/dpretet/svut/issues)\n[](https://github.com/dpretet/svut/stargazers)\n[](https://github.com/dpretet/svut/network)\n[](https://twitter.com/intent/tweet?text=Wow:&url=https%3A%2F%2Fgithub.com%2Fdpretet%2Fsvut)\n\n\n## Introduction\n\nSVUT is a very simple flow to create a Verilog/SystemVerilog unit test. It is\nwidely inspired by [SVUnit](http://agilesoc.com/open-source-projects/svunit/),\nbut it's written in python and run with [Icarus\nVerilog](http://iverilog.icarus.com/). SVUT follows KISS principle: [Keep It\nSimple, Stupid](https://en.wikipedia.org/wiki/KISS_principle).\n\nHope it can help you!\n\n### How to Install\n\n#### Pypi\n\nSVUT is availble on Pypi and can be installed as following:\n\n```bash\npip3 install svut\n```\n\n#### Git\n\nGit clone the repository in a path. Set up the SVUT environment variable\nand add SVUT to `$PATH`:\n\n```bash\nexport SVUT=$HOME/.svut\ngit clone https://github.com/dpretet/svut.git $SVUT\nexport PATH=$SVUT:$PATH\n```\n\nSVUT relies on [Icarus Verilog](http://iverilog.icarus.com/) as simulation\nback-end. Please install it with your favourite package manager and be sure to\nuse a version greater or equal to v10.2. SVUT is tested with `v10.2` and cannot\nwork with with lower version (`<= v9.x`).\n\nSVUT can also use [Verilator](https://github.com/verilator/verilator) but the support\nis more limited for the moment. A future release will fix that. An example to understand\nhow to use it along Icarus can be found [here](https://github.com/dpretet/friscv/tree/master/test/common)\n\n\n### How to use it\n\n\nTo create a unit test of a verilog module, call the command:\n\n```bash\nsvutCreate your_file.v\n```\n\nNo argument is required. SVUT will create \"your_file_testbench.sv\" which contains your module\ninstanciated and a place to write your testcase(s). Some codes are also commented to describe the\ndifferent macros and how to create a clock or dump a VCD for GTKWave. To run a test, call the\ncommand:\n\n```bash\nsvutRun -test your_file_testbench.sv\n```\n\nor simply `svutRun` to execute all testbenchs in the current folder.\n\n```bash\nsvutRun\n```\n\nSVUT will scan your current folder, search for the files with \"\\_testbench.sv\"\nsuffix and run all tests available. Multiple suffix patterns are [possible](https://github.com/dpretet/svut/blob/master/svutRun.py#L46).\n\nsvutRun proposes several arguments, most optional:\n\n- `-test`: specify the testsuite file path or a folder containing tests\n- `-f`: pass the fileset description, default is `files.f`\n- `-sim`: specify the simulator, `icarus` or `verilator`\n- `-main`: specify the main.cpp file when using verilator, default is `sim_main.cpp`\n- `-define`: pass verilog defines to the tool, like `-define \"DEF1=2;DEF2;DEF3=3\"`\n- `-vpi`: specify a compiled VPI, for instance `-vpi \"-M. -mMyVPI\"`\n- `-dry-run`: print the commands but don't execute them\n- `-include`: to pass include path, several can be passed like `-include folder1 folder2`\n- `-no-splash`: don't print SVUT splash banner, printed by default\n- `-compile-only`: just compile the testbench, don't execute it\n- `-run-only`: just execute the testbench, if no executable found, also build it\n\n\n# Tutorial\n\nCopy/paste this basic FFD model in a file named ffd.v into a new folder:\n\n```verilog\n`timescale 1 ns / 1 ps\n\nmodule ffd\n (\n input wire aclk,\n input wire arstn,\n input wire d,\n output reg q\n );\n\n always @ (posedge aclk or negedge arstn) begin\n if (arstn == 1'b0) q <= 1'b0;\n else q <= d;\n end\n\nendmodule\n```\n\nThen run:\n\n```bash\nsvutCreate ffd.v\n```\n\nffd_testbench.v has been dropped in the folder from you called svutCreate. It\ncontains all you need to start populating your testcases. In the header, you\ncan include directly your DUT file (uncomment):\n\n```verilog\n`include \"ffd.v\"\n```\n\nor you can store the path to your file into a `files.f` file, automatically\nrecognized by SVUT. Populate it with the files describing your IP. You can\nalso specify include folder in this way:\n\n```bash\n+incdir+$HOME/path/to/include/\n```\n\nRight after the module instance, you can use the example to generate a clock\n(uncomment):\n\n```verilog\ninitial aclk = 0;\nalways #2 aclk <= ~aclk;\n```\n\nNext line explains how to dump your signals values into a VCD file to open a\nwaveform in GTKWave (uncomment):\n\n```verilog\ninitial $dumpvars(0, ffd_unit_test);\ninitial $dumpfile(\"ffd_testbench.vcd\");\n```\n\nTwo functions follow, `setup()` and `teardown()`. Use them to configure the\nenvironment of the testcases:\n- setup() is called before each testcase execution\n- teandown() after each testcase execution\n\nA testcase is enclosed between to specific defines:\n\n```verilog\n`UNIT_TEST(\"TESTNAME\")\n ...\n`UNIT_TEST_END\n```\n\nTESTNAME is a string (optional), which will be displayed when test execution\nwill start. Then you can use the macros provided to display information,\nwarning, error and check some signals status and values. Each error found with\nmacros increments an error counter which determine a testcase status. If the\nerror counter is bigger than 0, the test is considered as failed.\n\nA testsuite, comprising several `UNIT_TEST` is declared with another define:\n\n```verilog\n`TEST_SUITE(\"SUITENAME\")\n ...\n`TEST_SUITE_END\n```\n\nTo test the FFD, add the next line into `setup()` to drive the reset and init the\nFFD input:\n\n```verilog\narstn = 1'b0;\nd = 1'b0;\n#100;\narstn = 1'b1;\n```\n\nand into the testcase:\n\n```verilog\n`FAIL_IF(q);\n```\n\nHere is a basic unit test checking if the FFD output is 0 after reset. Once\ncalled `svutRun` in your shell, you should see something similar:\n\n```\nINFO: Start testsuite << FFD Testsuite >> (@ 0)\n\nINFO: Starting << Test 0: Check reset is applied >> (@ 0)\nI will test if Q output is 0 after reset (@ 100000)\nSUCCESS: Test 0 pass (@ 110000)\n\nINFO: Starting << Test 1: Drive the FFD >> (@ 110000)\nI will test if Q output is 1 after D assertion (@ 210000)\nSUCCESS: Test 1 pass (@ 236000)\n\nINFO: Stop testsuite 'FFD Testsuite' (@ 236000)\n - Warning number: 0\n - Critical number: 0\n - Error number: 0\n - STATUS: 2/2 test(s) passed\n```\n\nSVUT relies (optionally) on files.f to declare fileset and define. The user\ncan also choose to pass define in the command line:\n\n```bash\nsvutRun -test my_testbench.sv -define \"DEF1=1;DEF2;DEF3=3\"\n```\n\nSVUT doesn't check possible collision between define passed in command line\nand the others defined in files.f. Double check that point if unexpected\nbehavior occurs during testbench.\n\nFinally, SVUT supports VPI for Icarus. Follow an example to compile and set up\nthe flow of an hypothetic UART, compiled with iverilog and using a define \"PORT\":\n\n```bash\niverilog-vpi uart.c\nsvutRun -vpi \"-M. -muart\" -define \"PORT=3333\" -t ./my_testbench.sv &\n```\n\nNow you know the basics of SVUT. The generated testbench provides prototypes of\navailable macros. Try them and play around to test SVUT. You can find these\nfiles into the example folder.\n\nEnjoy!\n\n\n## License\n\nCopyright 2021 The SVUT Authors\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of\nthis software and associated documentation files (the \"Software\"), to deal in\nthe Software without restriction, including without limitation the rights to\nuse, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\nof the Software, and to permit persons to whom the Software is furnished to do\nso, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE. imitations under the License.\n",
"bugtrack_url": null,
"license": "The MIT License Copyright (c) 2022 The SVUT Authors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "SystemVerilog Unit Test (SVUT)",
"version": "1.9.1",
"project_urls": {
"Bug Tracker": "https://github.com/dpretet/svut/issues",
"Homepage": "https://github.com/dpretet/svut"
},
"split_keywords": [
"verilog",
" systemverilog",
" testing"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f6483c6e49ebb39f5a8f1ae6bbc75ccdea60aec3a6c42fe670d9292f600f489d",
"md5": "574b9587a47b2c744ebbe85e213df98e",
"sha256": "8bf8c8190f97ad06f611406d73b9fbcb574bd261e5509fe55b2c18dd6b1a3b6f"
},
"downloads": -1,
"filename": "svut-1.9.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "574b9587a47b2c744ebbe85e213df98e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4,>=3.7",
"size": 19788,
"upload_time": "2024-06-27T11:44:49",
"upload_time_iso_8601": "2024-06-27T11:44:49.657120Z",
"url": "https://files.pythonhosted.org/packages/f6/48/3c6e49ebb39f5a8f1ae6bbc75ccdea60aec3a6c42fe670d9292f600f489d/svut-1.9.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "44bf0135a4925ccaab04dc99a8c324fc0d85b9ef93d37840995e8934bd80daa1",
"md5": "0704879be16dfec7a5dc18cfde74c459",
"sha256": "cc99db4007b17174203910d9ca976f0f8f1a9e1bb669bbf8538c14f070cb61e8"
},
"downloads": -1,
"filename": "svut-1.9.1.tar.gz",
"has_sig": false,
"md5_digest": "0704879be16dfec7a5dc18cfde74c459",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4,>=3.7",
"size": 19753,
"upload_time": "2024-06-27T11:44:51",
"upload_time_iso_8601": "2024-06-27T11:44:51.385190Z",
"url": "https://files.pythonhosted.org/packages/44/bf/0135a4925ccaab04dc99a8c324fc0d85b9ef93d37840995e8934bd80daa1/svut-1.9.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-06-27 11:44:51",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "dpretet",
"github_project": "svut",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "svut"
}
