This ticket relates to #103.
The ChannelFinder org projects and their tests are currently way too coupled. A change to recCaster leads to spinning up CF + ES. All of these concerns should be separated:
- recCaster moves to its own repo, tests the recsync wire protocol against a stub recCeiver
- recCeiver tests the recsync protocol against a stub recCaster, and tests the CF interface against a mock or contract-tested HTTP stub - no real Elasticsearch
- CF has whatever unit and (unit) integration tests that it needs, and then tests against e.g. AA interface via mock or contract for AA integration
- full end-to-end stack tests (recCaster + recCeiver + CF + ES) live as a separate nightly/release CI job, not in any individual project's test suite
This ticket relates to #103.
The ChannelFinder org projects and their tests are currently way too coupled. A change to recCaster leads to spinning up CF + ES. All of these concerns should be separated: