Put pure cleveland tests in their separate CI step
Clarification and motivation
Currently for cleveland
there are two steps defined in the CI pipeline:
test-cleveland-local-chain-<protocol>
test-cleveland-<network>net
where <protocol>
and <network>
change over time.
Both these test jobs, because run on CI, by default will run chain tests but also pure ones, see the documentation of the Test.Cleveland.Tasty
module.
However, this isn't the situation for the other libraries, where we have a dedicated 3rd step definition for pure tests alone (e.g. see test-lorentz
), using the --cleveland-mode
option.
We should be consistent and treat cleveland
tests as we do for the rest of the packages with chain tests.
Acceptance criteria
- CI steps running
cleveland
tests on chain (local or not) don't run pure tests - there is a CI steps that run pure
cleveland
tests