jaegertracing/jaeger

Re-expose Storage Integration Tests

Open

#6813 opened on Mar 5, 2025

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
area/storagechangelog:breaking-changeenhancementgood first issuehelp wanted

Description

Historically the integration tests for the storage layer have been exposed, and even recommended to be used to verify the correctness of 3rd party storage plugins.

The documentation still recommends this, but the docs are stale, and with the recent refactoring where the integration suite was moved into internal, this is no longer possible.

The breaking changes happened in #6657, but are a part of the greater #6637

Contributor guide

Tech stack
gogrpc
Domain
backendtesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GogRPCJaeger storage integration tests
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine PR #6657 and issue #6637 to understand how the integration suite was moved internal. The goal is to make the tests publicly accessible again while maintaining the internal structure. Review the current documentation link (https://github.com/jaegertracing/jaeger/tree/main/internal/storage/v1/grpc#certifying compliance) and update it accordingly. There are 14 comments discussing potential approaches; read them to align with maintainer expectations.