Test audit: remove low-value tests, repair tests that cannot fail, adopt a test authoring gate
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- リファクタリング
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- typescript
- 領域
- testing-qa, tooling
調査の方向性
Start by reading the complete evidence for audit batches L1, L2, and G5, then inspect the repository's agent instructions and the affected tests on the unedited base. Re-run each affected test and keeper test before changes, and use mutation proofs for repairs or consolidations. Done means the batches are merged or explicitly declined, the authoring gate is adopted, and comparable BEFORE/AFTER measurements are posted.
索引モデルが issue の本文から書いたものです。
説明
Summary
A test audit of this repository (method: the openclaw test-audit skill: authoring gate, junk-pattern list, retention bar, full evidence per candidate) found 3 candidates with complete evidence: tests that duplicate a stronger owner test, tests that cannot fail, and test-only production seams. This issue tracks applying them as small atomic PRs, one per owner boundary, plus adopting a test authoring gate in this repository's agent instructions.
Every PR re-runs the affected tests and their keeper tests on the unedited base first. A retained test that fails on the base is treated as a product bug and fixed at its owner, never deleted. Every consolidation or repair carries a mutation proof (a deliberate break of the production owner turns the keeper red, then the owner is restored byte for byte).
Expected (ideal state)
| Property | Why |
|---|---|
| Every test protects observable behavior, a credible regression, or an independently meaningful contract | Confidence, not deletion count |
| Every junk test with complete evidence is deleted, consolidated into its named keeper, or repaired so it can fail | Low-value tests cost CI time and mislead reviewers |
| Test-only production seams unlocked by those deletions are removed | Production code whose only callers are tests is dead weight |
| Assertions that can never fail are repaired, each proven by a mutation that turns it red | A test that cannot fail proves nothing |
| Valuable tests that run in no CI job are routed into CI | Coverage that never runs is not coverage |
| The repository's agent test rules carry the authoring gate, junk-pattern list and retention bar, with conflicting older rules reconciled | New junk stops arriving |
| Test/support/production line counts and CI time are measured before and after with the same tool | The effect is stated in numbers |
Acceptance criteria
- Every audit batch for this repository merged or explicitly declined with a reason (planned batches: L1, L2, G5)
- The test authoring gate adopted in this repository's agent instructions
- BEFORE/AFTER numbers (test files, test/support/production lines, CI job times or a stated "not comparable") posted here
- 主要言語
- TypeScript
- スター
- 3.8k
- フォーク
- 246
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
code-yeongyu/lazycodex のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
code-yeongyu/lazycodex#170 ·
-
Fix Codex browser QA routing before standalone Playwright対応中かも @berkshirehathaways が 85 日前に担当しました。 オープン
難易度 2/5 1〜2日 初心者へのやさしさ 72/100
code-yeongyu/lazycodex#148 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
code-yeongyu/lazycodex#172 ·
-
[5.0.0-beta.78] High cost and rapid quota consumption: use role-appropriate agent model defaultsオープン
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
code-yeongyu/lazycodex#166 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
code-yeongyu/lazycodex#163 ·
code-yeongyu/lazycodex の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
openremote/openremote#3487 · コメント 1 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
coollabsio/jean#867 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
ehmpathy/rhachet-roles-bhuild#616 ·
メンテナーはふだん 1 日以内に返信
-
📘 Docs supabase/cli
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
bug(cli): theme file home-directory check uses startsWith (sibling dirs pass, Windows casing fails)オープンarea/core kind/bug priority/p2 status/bot-triaged
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
google-gemini/gemini-cli#29955 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信