The tests for the trace-related endpoints need to cover failures from both the Tempo and Loki backends.
Missing Test Cases:
- Tempo/Loki Unavailability: Test for 502 Bad Gateway responses when calls to Tempo or Loki fail due to network errors.
- Tempo/Loki Error Responses: Test for 502 Bad Gateway responses when Tempo or Loki return non-200 status codes.
- Trace Not Found: Test the response when a validly formatted, but non-existent, trace ID is requested from Tempo (e.g., ensuring a 404 from Tempo is handled gracefully).
- No Correlated Logs: Test the scenario where a trace exists in Tempo, but has no associated logs in Loki.
- Invalid Payloads: Test for malformed JSON responses from both services.
The tests for the trace-related endpoints need to cover failures from both the Tempo and Loki backends.
Missing Test Cases:
- Tempo/Loki Unavailability: Test for
502 Bad Gatewayresponses when calls to Tempo or Loki fail due to network errors.- Tempo/Loki Error Responses: Test for
502 Bad Gatewayresponses when Tempo or Loki return non-200 status codes.- Trace Not Found: Test the response when a validly formatted, but non-existent, trace ID is requested from Tempo (e.g., ensuring a 404 from Tempo is handled gracefully).
- No Correlated Logs: Test the scenario where a trace exists in Tempo, but has no associated logs in Loki.
- Invalid Payloads: Test for malformed JSON responses from both services.