jaegertracing/jaeger

Re-expose Storage Integration Tests

Open

#6,813 opened on 2025年3月5日

GitHub で見る
 (14 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.
Re-expose Storage Integration Tests · jaegertracing/jaeger#6813 | Good First Issue