The test suite is currently split between two organization models: some tests are organized by the component, or the feature, they test (like this), and a lot of tests are organized by the number of the GitHub issue they verify (like [this](https://github.com/mockk/mockk/blob/master/mockk/jvm/s

This is very low prio, but it usually happens that when touching Prims or some other file high in the dependency graph, we get spurious diffs in many other files. Since we check-in the snapshot, and we need to have it up-to-date, we get very verbose commits when nothing relevant changed. Plus, when something did change, it's hard to spot.

Example: I removed a few lines in prims and get things

The metric needs to be updated to support multiple databases (eg. give the database name as a label).

If TOPLEVEL is not set iverilog fails with an obscure error message because there is nothing after the -s option. I recommend that Makefile.sim check for TOPLEVEL and (and other required variables) and give a clean error message.

Here is the problem:

$ make compile
Traceback (most recent call last):
File "C:\My_Designs\probe_fpga_design_1\run.py", line 336, in
main()
File "C:\My_Designs\probe_fpga_design_1\run.py", line 181, in main
vu.add_osvvm()
File "c:\my_designs\probe_fpga_design_1\deps\vunit\vunit\ui_init_.py", line 1030, in add_osvvm
self.builtins.add("osvvm")
File "c:\my

It would be useful to add new programs to the prusti-tests/ test suite, with the goal of increasing code coverage as some branches of Prusti are currently never reached by the tests.

See also the dev guide.