Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

CI: add a mutation check — 11 mutations across #222/#223/#224 left the suite green

オープン
  • 何か問題がありますか？
#235 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 4 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
typescript
領域
ci-cd, testing-qa

調査の方向性

@stryker-mutator/core とその vitest サポートを使用した runtime spike から始め、packages/outpost にある既存の ~1,090 件のテストを測定します。次に、記録された CPK-8037 commits に対して、packages/outpost/** と apps/** の変更行のカバレッジを評価します。完了の条件は、一覧にある 4 つの mutation classes が検出され、必要な CI に対してチェックの範囲が限定されていることです。

索引モデルが issue の本文から書いたものです。

説明

area: infrastructure roadmap roadmap: next

Why

A review round on 2026-08-20 across three open PRs found eleven mutations that delete a claimed fix while leaving the test suite green. Every one was a test that read as coverage and was not.

The distribution matters more than the individual cases:

  • Several were in newly added code, i.e. the tests written alongside a fix did not pin that fix.
  • Two were worse than absent coverage, because the test documents the behaviour it fails to pin — a future reader treats it as proof, and a reviewer treats it as reviewed.
  • One survived removing the exact line the test is named after.

This is not a review-diligence problem. It survived a seven-agent review on the largest of the three PRs until mutation testing was enforced, and the same round produced several confidently-stated findings that were wrong for the same underlying reason: claims about what a test would do, asserted without running it.

Specifics per PR are in CPK-8037, kept there rather than here.

What to build

A CI check that, for source lines a PR touches, applies mechanical mutations and fails if the suite still passes.

Priority order, based on which classes actually caught real gaps in the review round:

  1. Predicate relaxation — comparison operators widened, a truthiness check substituted for a normalising one, a regex anchor dropped. Cheapest to implement, caught the most.
  2. Guard deletion — remove a newly added early-return or throw.
  3. Call-site un-wiring — where a diff extracts a helper and calls it, revert the call site while leaving the helper defined and exported. This is the class a human reviewer is least likely to imagine, and it produced a full-green suite twice in one day.
  4. await removal on newly added awaits.

Scope to changed lines, not the tree, or the runtime is unbounded.

Known limit, worth designing around

Assertions made against strings that are never executed are the structural blind spot this cannot close. Where a query or template is built as text and the dependency is mocked, a substring assertion can be satisfied by an unrelated occurrence while a real semantic mutation passes through. Mutation testing catches "this test cannot fail"; it does not catch "this test asserts the wrong thing about text it never runs." Closing that needs execution against a real dependency, which is separate work.

Acceptance

  • Runs on PRs touching packages/outpost/** and apps/**
  • The mutation classes above are detected as survivors when run against the relevant pre-fix commits (recorded in CPK-8037)
  • Bounded enough to sit in the required check set rather than a nightly

@stryker-mutator/core supports vitest and is the obvious starting point, but spike the runtime first — packages/outpost alone is ~1090 tests and mutation runs multiply that.

主要言語
TypeScript
スター
10
フォーク
4
平均マージ
4日 2時間
マージ済み PR（30日）
7

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CopilotKit/outpost のほかの issue

CopilotKit/outpost の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。