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

Abierto
  • ¿Algo no está bien?
#225 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, java
Área
build-system, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
103
Forks
23
Merge medio
5 d 8 h
PR fusionados (30 d)
3

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Backblaze/b2-sdk-java

Todos los issues de Backblaze/b2-sdk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.