Expose repository-owned sdkharness conformance checks

未关闭
#1,168 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
638
派生
138
平均合并
8 小时 27 分钟
30 天内合并 PR
8

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Backblaze/B2_Command_Line_Tool 的其他 Issue

查看 Backblaze/B2_Command_Line_Tool 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。