Should we consolidate interface, scenario tests under unit?

[sed-i]

Currently,

• Some charming teams have both unit and scenario under tests.
• Interface tester assumes tests are under tests/interface, so we have to have yet another folder under tests.

Since harness, scenario an interface tests (and the occasional doctests!) are all unit tests, would it make more sense to encourage hosting them all under tests/unit? This could also ease making coverage calculation more precise.

[benhoyt]

Hey @sed-i, this makes sense to me. I notice the charmcraft init templates have only "unit" and "integration". We can't actually police this in canonical/operator. Are you thinking that we'd have some (maybe charmcraft) plugin to check for this, or just a "best practice" that we'd document/promote?