Repository navigation
ToppleCat 0.0.5
ToppleCat 0.0.5
Review the contract more easily before handoff, and try the samples directly
from a fresh checkout.
Why upgrade
- The reviewer contract page now puts each acceptance condition beside the
exact canonical test method that JUnit will execute. Public examples appear
first; independent reviewer-only checks are clearly labelled. The page also
has stronger contrast for practical review sessions. - The JUnit and Spring Boot samples can now be tried from their own directories
with./gradlew. Normal interactive use resolves the released package; the
repository demos use Maven Local only when they deliberately test the source
checkout. - The new FAQ explains the Java/JUnit contract approach, why ToppleCat does not
require Cucumber or.featurefiles, and how PIT, BDD, and JGiven relate to
the project.
Upgrade
Most projects only need to update the plugin and topplecat-junit dependency
to 0.0.5.
id("io.github.samzhu.topplecat") version "0.0.5"Compatibility
No user-visible breaking changes. Existing contracts, reviewer custody, and
verification gates keep their behavior.
Learn more
ToppleCat 0.0.5
交付前更容易確認真正會執行的合約,也能從剛 clone 下來的 sample 直接開始試用。
為什麼值得升級
- 審閱合約頁現在會把每個驗收條件放在真正會由 JUnit 執行的主要測試方法旁邊。
公開案例先出現,獨立設計的審閱者專用檢查會清楚標示;畫面的對比也提高了,
看報告比較不吃力。 - JUnit 與 Spring Boot 的 sample 現在可以直接在各自目錄執行
./gradlew。
一般互動試用會使用正式發佈的套件;只有要驗證這個原始碼工作副本的 demo 才會
使用 Maven Local。 - 新增的常見問題整理了 Java/JUnit 合約的做法、為什麼 ToppleCat 不需要
Cucumber 或.feature,以及 PIT、BDD 和 JGiven 與本專案的關係。
升級方式
大多數專案只要把 Gradle 外掛與 topplecat-junit 的版本更新成 0.0.5。
id("io.github.samzhu.topplecat") version "0.0.5"相容性
沒有使用者可見的破壞性變更。既有合約、審閱者保管流程與驗證關卡的行為都維持不變。