Expose repository-owned sdkharness conformance checks

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
testing

Línea de trabajo

Start by inspecting .sdkharness/tests.tsv and the existing CLI conformance checks in backblaze-labs/demand-side-ai/sdkharness; the issue does not name specific assertion files or test commands. The work is complete when all 30 checks are moved in coherent batches, run in shadow mode with equivalent evidence, and accept only the specified simulator realm and fake credentials while emitting one versioned result per scenario.

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

Descripción

Context

The repository now owns its sdkharness customer-health contract (#1166 / #1167). The next phase moves the CLI-specific conformance assertions that currently live in backblaze-labs/demand-side-ai/sdkharness beside the CLI implementation.

These are not replacements with the existing credentialed integration suite. They are deterministic quality contracts run by the central harness against its loopback B2 simulator.

Proposed contract

  • Extend .sdkharness/tests.tsv with conformance/<capability> rows.
  • Store the corresponding executable assertions under .sdkharness/tests/.
  • Accept only the harness-provided simulator realm and fixed fake credentials for routine execution.
  • Emit exactly one versioned SDKHARNESS_RESULT record per scenario.
  • Load the CLI implementation from the checked-out repository revision.

The central harness remains responsible for scenario semantics, simulator lifecycle, invocation, evidence, issue reconciliation, fleet reporting, and notifications.

Safe rollout

Deliver the 30 current CLI conformance checks in coherent batches. Each batch runs in non-counting shadow mode beside the current harness implementation before promotion. No harness check is removed until the exact merged upstream revision produces equivalent evidence.

Lenguaje dominante
Python
Estrellas
638
Forks
138
Merge medio
8 h 27 min
PR fusionados (30 d)
8

Preparar el entorno

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_Command_Line_Tool

Todos los issues de Backblaze/B2_Command_Line_Tool

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.