[Infrastructure] Code coverage

[gyermolenko]

As far as I know almost always coverage is used to see "test coverage".
For unused branches/variables etc there are linters, dead-code finders (such as vulture or dead).

So I don't think code coverage is important to extent of running run_all.sh script.

I would like to

• remove run_all.sh
• collect coverage
  • only for tests
  • only for one python branch (e.g. 3.7) (although it is possible to do coverage run -p and then coverage combine)

[faif]

What's the reasoning behind running it only for a specific Python version (e.g. 3.7)?

[gyermolenko]

What's the reasoning behind running it only for a specific Python version

a bit simpler, I guess. But combining is possible, so nevermind.
My biggest concern here is - why run_all.sh at all?

[faif]

I think that the basic idea was to able to run all scripts with one command. Coverage came later. So if we can simplify it by removing the coverage part since it's handled elsewhere, fine by me.

[gyermolenko]

To update on this issue:

• run_all.sh was removed
• since removal of py2 support full coverage can be done without combining reports per test environment

So only some simplifications in tox.ini are required to resolve the issue.