Repository navigation
0.0.10
0.0.10 makes formal Mutation Testing comparable across AI deliveries: every
Verify run now owns the PIT version, operator set, public Acceptance Methods,
and full result matrix while preserving the producer's raw evidence for human
review.
Upgrade: remove custom formal mutation producers
Formal toppleCatVerify no longer accepts mutationTesting.producerTask or
mutationTesting.reportFile. Remove those settings before upgrading. A project
may still run its own PIT workflow separately, but ToppleCat does not read,
merge, or use that result for its Mutation Gate.
The public Java/JUnit acceptance-authoring API is otherwise unchanged.
Run the same mutation challenge for every delivery
Formal Verify now runs PIT 1.25.5 with the versioned
topplecat-managed-v1 profile. The profile explicitly selects return-value,
forced-conditional, conditional-boundary, void-call, and arithmetic operators;
it never inherits PIT's DEFAULTS, STRONGER, or ALL groups.
The producer is fresh for every formal run and targets only compiler-emitted
public Acceptance Methods. Hidden Tests, Properties, helpers, and a project's
own PIT tasks cannot contribute mutation coverage or detection credit.
See which exact Acceptance Method detected a change
ToppleCat keeps PIT's original status, detected, mutator, description,
coveringTests, killingTests, and succeedingTests. Mutation Attribution
matches the complete class, method, overload, and parameter types. Each AC's
detection rate therefore counts only mutants covered by that Acceptance Method
and killed by that same method.
A usable matrix with no exact public attribution fails the Mutation Gate. Once
some exact attribution exists, remaining unattributed mutants and ACs with no
covered managed-profile mutant stay visible to the reviewer without directly
changing the Gate. The sealed threshold still applies to every AC that has
covered mutants; lowering it remains a human verification-policy decision.
Review independent evidence without a blended score
Verification HTML presents Mechanical Seal, Hidden Tests, Property-Based
Testing, and Mutation Testing as separate sections. Mutation details include
the managed profile, operator summaries, per-AC rates, attribution gaps, and
expandable raw PIT relationships. Every enabled Independent Safeguard finishes
and retains its own current-run result even when another one fails.
Contract Review also includes the reviewer-only, non-blocking Contract Quality
Advisory introduced since the previous published GitHub Release. It flags
possible expected-shape drift or opaque identifier literals for human review;
it never infers business rules or affects a Gate.
Public reports and agent-feedback.json remain safe: profile details, raw PIT
fields, selectors, classes, methods, counts, hidden data, and private failures
stay reviewer-only.
Upgrade actions
- Update the Gradle plugin and
topplecat-junitdependency to0.0.10. - Remove
producerTaskandreportFilefrommutationTestingconfiguration. - Restore reviewer custody, Check, Review, and Reseal before Verify because
the Mechanical Seal is current-version-only.
Reviewer tooling that reads generated projections must adapt to the directly
updated topplecat.mutation-results.v1 managed-profile fields and the current
topplecat.review-view.v6 and topplecat.verification-view.v8 projections.
There is no migration or dual-format reader.
Requirements
Java 25 and the existing compatible Gradle and JUnit requirements are
unchanged. PIT 1.25.5 is managed internally by formal Verify.
========================
0.0.10 讓不同 AI 交付的正式突變測試可以互相比較:每次 Verify 都由 ToppleCat
管理 PIT 版本、operator 清單、公開 Acceptance Method 與完整結果矩陣,同時保留
producer 的原始證據供人類判讀。
升級:移除自訂的正式 mutation producer
正式 toppleCatVerify 不再接受 mutationTesting.producerTask 或
mutationTesting.reportFile。升級前請移除這兩項設定。專案仍可另外執行自己的 PIT
工作流,但 ToppleCat 不會讀取、合併或將其結果用於 Mutation Gate。
公開 Java/JUnit 驗收撰寫 API 除此之外沒有改變。
每次交付都執行相同的突變挑戰
正式 Verify 現在固定執行 PIT 1.25.5 與版本化的 topplecat-managed-v1 profile。
這個 profile 明確選取回傳值、強制條件、條件邊界、void call 與算術運算相關
operators,不會繼承 PIT 的 DEFAULTS、STRONGER 或 ALL 群組。
每次正式執行都重新建立 producer,只以 compiler 產生的公開 Acceptance Methods
為目標。隱藏測試、Properties、helper 與專案自己的 PIT task 都不能替 Mutation Gate
提供 coverage 或 detection credit。
看見是哪個精確 Acceptance Method 偵測到改變
ToppleCat 原樣保留 PIT 的 status、detected、mutator、description、
coveringTests、killingTests 與 succeedingTests。Mutation Attribution 會完整比對
class、method、overload 與參數型別,因此每個 AC 的 detection rate 只計算該
Acceptance Method 自己覆蓋、並由同一方法殺死的 mutants。
若可用矩陣完全無法精確歸因到任何公開方法,Mutation Gate 會失敗。一旦已有部分
精確歸因,其餘 unattributed mutants 與沒有被 managed profile mutant 覆蓋的 AC
仍會呈現給審閱者,但不直接改變 Gate。所有已有 covered mutants 的 AC 仍套用
sealed threshold;降低 threshold 仍是人類選擇的驗證政策。
分開判讀各項證據,不建立綜合分數
Verification HTML 將 Mechanical Seal、隱藏測試、Property-Based Testing 與
Mutation Testing 分區呈現。Mutation 區塊包含 managed profile、operator 摘要、
每個 AC 的 rate、attribution gap,以及可展開的 PIT 原始關係。即使某一項失敗,
每個已啟用的 Independent Safeguard 仍會完成並保留本次執行的獨立結果。
自上一個已公開的 GitHub Release 起,Contract Review 也加入 reviewer-only、非阻擋的
Contract Quality Advisory,提醒人類檢查可能的 expected shape drift 或 opaque
identifier literal。它不推測業務規則,也不影響任何 Gate。
公開報告與 agent-feedback.json 仍維持安全邊界:profile 細節、PIT 原始欄位、
selectors、class、method、計數、隱藏資料與私密失敗都只提供給審閱者。
升級步驟
- 將 Gradle plugin 與
topplecat-junitdependency 更新為0.0.10。 - 移除
mutationTesting中的producerTask與reportFile。 - Mechanical Seal 只適用目前版本;更新後請先 Restore reviewer custody,再 Check、
Review、Reseal,最後才 Verify。
若 reviewer tooling 會讀取產生的投影,必須配合直接更新的
topplecat.mutation-results.v1 managed-profile 欄位,以及目前的
topplecat.review-view.v6 與 topplecat.verification-view.v8。本版不提供 migration
或雙格式 reader。
環境需求
Java 25 與既有相容的 Gradle、JUnit 需求沒有改變。正式 Verify 會在內部管理
PIT 1.25.5。