Split docker-compose.test.yml: one container per microservice #15

Open
opened 2026-05-05 00:20:47 +10:00 by unkinben · 0 comments
Owner

The current test compose runs everything monolithically. Rework docker-compose.test.yml so each microservice runs in its own container (auth, catalogue, streaming, ingest, thumbnailer, metadata) with the same inter-service networking as production. Tests should hit the real HTTP endpoints through nginx or direct service ports. This validates that service-to-service JWT auth, NATS event flow, and S3 access all work end-to-end, not just in-process. Mark these as e2e tests (already have pytest marker). Add a make target: 'make test-e2e'.

The current test compose runs everything monolithically. Rework docker-compose.test.yml so each microservice runs in its own container (auth, catalogue, streaming, ingest, thumbnailer, metadata) with the same inter-service networking as production. Tests should hit the real HTTP endpoints through nginx or direct service ports. This validates that service-to-service JWT auth, NATS event flow, and S3 access all work end-to-end, not just in-process. Mark these as e2e tests (already have pytest marker). Add a make target: 'make test-e2e'.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/streamstack#15