Kaleb Barrett
Kaleb Barrett
Well... Maybe I'll just try fixing #1994 while I'm at it =/
I'm actually going to pause on this to focus on 2.0 features.
I agree. I would even like to see all the current data broken down by package version. For example, it'd be interesting to me to see what versions users who...
Outside of the Runner where we can use `pytest-coverage` to collect coverage, the other things in that package can't easily have coverage collected on them. We also don't have exhaustive...
Does specifying `--cov=cocotb_tools.runner` work? That's fine by be. We can enable more once we have some idea of how we can actually collect coverage on those modules. They are commandline...
And Questa fails randomly until #4593 is in.
Are we sure that specifying `--cov` more than once works correctly? It seems like coverage decreases because of pytest tests coverage not being collected anymore. Also, I don't see `runner.py`...
It looks like it's collecting coverage data in `tests/` as well and strangely picking up a single line from one file? Maybe we should exclude the `tests/` and `examples/` directories...
This sounds nice, but it should definitely be a separate package. There are many possible uses of pytest with cocotb so anything that prevents other users from using cocotb with...
The assertion writing is a bit different. We aren't registering ourselves into pytest, but registering pytest's assertion rewriting import hook. It works standalone. Same with cocotb supporting `pytest.raises`, `pytest.warns`, and...