Own sdkharness conformance and resilience checks

未關閉
#612 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
15/100
Issue 類型
重構
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python
領域
testing-qa

研究方向

Start with the contract file .sdkharness/tests.tsv, which must list all 33 conformance and 16 resilience scenarios as repository-owned, simulator-only entries. Check that each contract imports b2sdk from the exact checkout, and that dispatch rejects non-loopback endpoints and malformed scenarios or results. Done means every scenario passes against fresh sdkharness simulators with unchanged behavior, and the focused contract tests, lint, and unit gates pass. The payload does not name the individual scenario files, so mapping them is the first real task.

由索引模型根據 Issue 內容生成。

描述

The centralized sdkharness currently contains 33 b2sdk conformance implementations and 16 resilience implementations. That makes behavioral assertions live outside the repository and allows them to drift from the SDK revision they exercise.\n\nMove those executable assertions into this repository under the existing .sdkharness contract. Keep scenario inventory, simulator lifecycle, orchestration, evidence, issue reconciliation, reporting, and notification in demand-side-ai/sdkharness.\n\nAcceptance criteria:\n- .sdkharness/tests.tsv exposes all 33 conformance and 16 resilience scenarios as simulator-only repository-owned contracts.\n- Every contract imports b2sdk from the exact checkout.\n- Dispatch rejects non-loopback endpoints, malformed scenarios, and malformed or ambiguous results.\n- Existing behavior is preserved when all scenarios run against fresh sdkharness simulators.\n- Focused contract tests, repository lint, and the relevant unit gates pass.\n\nParent roadmap: backblaze-labs/demand-side-ai#744

主要語言
Python
星號
214
分支
68
平均合併
51 分鐘
30 天內合併 PR
6

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

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

Backblaze/b2-sdk-python 的其他 Issue

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

相似的 Issue

更多 Python Issue

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

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