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

未關閉
  • 哪裡不對？
#225 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
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 小時
30 天內合併 PR
3

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

Backblaze/b2-sdk-java 的其他 Issue

查看 Backblaze/b2-sdk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。