VUnit will compile a testbench that does not set the ".example" attribute for any testcase, when called like this:
python run.py --with-attributes=.example
Only after compilation "No tests were run." is reported. Is this a deliberate design decision?
I think it would make sense to skip compilation if the test_list is empty.
My use case, where this would be a great benefit:
The codebase has many run.py's. In the CI/CD pipeline for an FPGA Image A I want to run all testbenches that are tagged to be related to the FPGA Image. The Makefile finds all run.py's and runs them using --with-attributes. However, the time overhead for compiling all testbenches if only a few are actually executed is quite large.
VUnit will compile a testbench that does not set the ".example" attribute for any testcase, when called like this:
python run.py --with-attributes=.exampleOnly after compilation "No tests were run." is reported. Is this a deliberate design decision?
I think it would make sense to skip compilation if the test_list is empty.
My use case, where this would be a great benefit:
The codebase has many run.py's. In the CI/CD pipeline for an FPGA Image A I want to run all testbenches that are tagged to be related to the FPGA Image. The Makefile finds all run.py's and runs them using --with-attributes. However, the time overhead for compiling all testbenches if only a few are actually executed is quite large.