Contributing in the form of code, feedback, ideas or bug reports are welcome. Code contributions are expected to pass all tests and style checks. If there are any problems let us know.

Before doing any major changes we recommend creating an issue or chatting with us on gitter to discuss first. In this way you do not get started on the wrong track and wasting time.

Being a testing framework we value automated testing and all contributions in both the Python and VHDL/SystemVerilog domain are expected to add new tests along with the new functionality.

Continous Integration

VUnit runs all test and lint checks on both Windows using AppVeyor and Linux using Travis CI with several versions of Python. GHDL is used to run the VHDL tests of all our libraries and examples.

All tests will be automatically run on any pull request and they are expected to pass for us to approve the merge.

Any commit on master that has a successful CI run will automatically update the VUnit website

Testing with Tox

VUnit uses the Python tox tool in the CI flow. Typically developers do not need to run this on their local machine.

Tox makes it easier to automatically test VUnit in various configurations. Tox automates creation of virtual environments and installation of dependencies needed for testing. In fact, all of the tests can be run in a single command:

vunit/ > tox

If tox is not available in your Python environment, it can be installed from PyPI with pip:

vunit/ > pip install tox

For most developers, running the full testsuite will likely lead to failed test cases because not all Python interpreters or HDL simulators are installed in their environment. More focused testing is possible by specifying which tox “environments” should be tested. For example, assume a developer uses Python 2.7 and Modelsim and would like to test changes using tools available in his environment:

vunit/ > tox -e py27-unit,py27-acceptance-modelsim

A full list of test environments can be seen by issuing the following command:

vunit/ > tox -l

Making releases

Releases are automatically made by Travic CI on any master commit that has a new version set in vunit/ together with a corresponding release note in docs/release_notes/X.Y.Z.rst. The release note files in docs/release_notes/ are used to automatically generate the release notes.

Travic CI makes a release by uploading a new package to PyPI and setting a release tag named vX.Y.Z in Git.

A new release will not be made if the the X.Y.Z release is already on PyPI or the repo tag is already set.