Add an integrationTest source set that can target a custom B2 endpoint

オープン
  • 何か問題がありますか？
#225 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 3 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, java
領域
build-system, testing

調査の方向性

Start with the test conventions in buildSrc/src/main/kotlin/b2sdk.gradle.kts and the credential handling in .github/workflows/ci_cd.yml. Then read B2ClientConfig.Builder.setMasterUrl and HttpClientFactoryImpl.Builder.setSupportInsecureHttp, and use samples/src/main/java/com/backblaze/b2/sample/B2Sample.java as the flow outline. Done means ./gradlew integrationTest skips cleanly without the env vars, runs against B2_ENDPOINT when set, and ./gradlew test is unchanged. Confirm with maintainers first, since the author has not pushed code and no reply exists yet.

索引モデルが issue の本文から書いたものです。

説明

What

Please consider adding a Gradle integrationTest source set whose tests run the main client flows against a configurable B2 endpoint, so the SDK has an integration suite that can run against either real B2 or a local B2 API simulator.

Why

The repository's tests run offline (stubbed web layer / local test server), and CI touches real B2 only to upload the build zip. There is therefore no suite that exercises the SDK end to end against a B2 API. A suite gated on an endpoint variable would let Backblaze's own CI or a contributor run it with no real-account credentials by pointing it at a local B2 API simulator. No SDK change is needed: the endpoint is already configurable.

What I checked (default branch master)

  • .github/workflows/ci_cd.yml:19-21 exposes B2_ACCOUNT_ID, B2_UPLOAD_BUCKET, B2_APPLICATION_KEY, used by the "Upload to b2" step (maybe_upload_build_results), which uploads the build zip; I found no test step that uses them.
  • The master URL is already configurable: B2ClientConfig.Builder.setMasterUrl (core/src/main/java/com/backblaze/b2/client/B2ClientConfig.java:113), consumed by B2StorageClientWebifierImpl (.../B2StorageClientWebifierImpl.java:106-123).
  • Plain-http loopback needs HttpClientFactoryImpl.Builder.setSupportInsecureHttp(true) (httpclient/src/main/java/com/backblaze/b2/client/webApiHttpClient/HttpClientFactoryImpl.java:128).
  • samples/src/main/java/com/backblaze/b2/sample/B2Sample.java already walks the main flows.
  • The test conventions live in buildSrc/src/main/kotlin/b2sdk.gradle.kts.

I did not read every test file line by line; I looked for integration-named files and for the CI credentials path, and found none.

Minimal sketch

  • New integrationTest source set (JUnit 4, same convention plugin), not part of the default test task.
  • Tests skip unless B2_ACCOUNT_ID, B2_APPLICATION_KEY and B2_ENDPOINT are set; B2_ENDPOINT goes to setMasterUrl.
  • Start from the B2Sample flows: authorize, create bucket, upload, list, download, large file, copy, hide, delete.

Acceptance criteria

  • ./gradlew test is unchanged and still offline.
  • ./gradlew integrationTest skips cleanly when the variables are unset, and runs against the given endpoint when set.
  • Nothing in the suite hard-codes api.backblazeb2.com.

Offer

The Backblaze SDK test-harness team can contribute the suite as a PR if that is welcome. We have not pushed any code.

🤖 Generated with Claude Code

主要言語
Java
スター
103
フォーク
23
平均マージ
5日 8時間
マージ済み PR（30日）
3

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Backblaze/b2-sdk-java のほかの issue

Backblaze/b2-sdk-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。