Move out of cleveland test suites for other packages
Clarification and motivation
<history>
Long ago, in #233 (closed), the cleveland
testing framework was created, putting all of our testing code in a single package.
One downside of doing that is that test suites of other libraries (e.g. morley
) then had cleveland
as a dependency and sadly this means (at least currently) that compilation will be rejected due to cyclic dependencies between packages (even tho there is none between libraries
and tests
components).
So, to introduce as little clutter as possible, it was decided to move those tests suites under the cleveland
package itself (e.g. morley-test
).
</history>
Recently however it was discussed how this is un-intuitive and conceptually off.
In the end the agreement was that a better solution would be to instead:
- move all test suites that don't cover
cleveland
itself out of thecleveland
package to a new one (e.g. atests
one) - properly document why this new package exists and the criteria for adding a new test suite to it
Acceptance criteria
- the
cleveland
package does not contain test-suites for libraries in other packages - a new package contains all test suites that cannot be part of the same package as the library that they test
- documentation is updated and explains why this new package exists, including:
the package's README and the
description
field in the package.yaml