Skip to content

test: end-to-end test chaining receiver → storage → api → client #83

Description

@planetf1

crates/otelite-receiver/tests/ exercises OTLP → conversion → storage but not through the API.
crates/otelite-api/tests/ exercises REST endpoints but writes to storage directly, bypassing the receiver.

No test currently chains all four layers. A wiring regression in the OTLP receiver or in the API router would not be caught.

Suggested: a single tokio::test that boots both servers on ephemeral ports, sends one OTLP HTTP/JSON payload, and asserts via otelite-client that the same payload round-trips.

Acceptance criteria: the test exists and runs in CI; passes against current main.


Filed from review on 2026-05-15.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:ciCI/CD and build toolingpriority:p3Lower priority — nice to havetype:testTest coverage and quality

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions