jaegertracing/jaeger

Re-expose Storage Integration Tests

Open

#6,813 建立於 2025年3月5日

在 GitHub 查看
 (14 留言) (0 反應) (0 負責人)Go (18,974 star) (2,326 fork)batch import
area/storagechangelog:breaking-changeenhancementgood first issuehelp wanted

描述

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

貢獻者指南

技術棧
gogrpc
領域
backendtesting
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GogRPCJaeger storage integration tests
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.