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

Aperta
  • Qualcosa non va?
#225 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, java
Ambito
build-system, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Java
Stelle
103
Fork
23
Merge medio
5g 8h
PR unite (30g)
3

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Backblaze/b2-sdk-java

Tutte le issue di Backblaze/b2-sdk-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.