Code review comment for ~jugmac00/lpci:improve-contribution-documentation

> Should running the plain `tox` command run the unit tests twice - once each for the unit test environment and once for the coverage environment.

Yes, this is a common approach.

Once we use tox 4, we can use a different approach. As then it is more easily possible to declare dependencies between environments, resp. run environments in succession.

Other approaches I have seen.... Every testenv, which runs tests, also runs coverage. This approach works nicely for CI, but is pretty annoying when developing locally, as then you always need to scroll up to find the reason for error.

So all in all - I think we are using the best approach.