testing

To write Kotlin tests that verify state, you must enforce the Iron Law of Classical TDD by asserting outcomes and avoiding mock-heavy verify() calls. This Skill guides you in applying state-based assertions and BDD nesting to maintain reliable test suites.

The Iron Law of Classical TDD mandates that tests verify only state and outcomes, never interactions. This prevents test pollution and anti-patterns, ensuring your test suite validates actual behavior rather than fragile implementation details.

Structuring BDD tests with boundary analysis in Kotlin involves using BDD nesting with systematic boundary value analysis and equivalence class partitioning. This Skill provides test isolation tactics and factory methods with defaults to justify every data combination before writing assertions.

Configuring WireMock scenarios in Spring testing workflows requires state-based assertions and strict adherence to Classical TDD principles. This Skill documents WireMock patterns and Awaitility scenarios to satisfy behavioral requirements without resorting to interaction verification.

You should avoid using verify() in unit tests whenever following Classical TDD, as it couples tests to internal interactions. This Skill helps you identify hybrid state and interaction anti-patterns, guiding you to use decision table coverage and responsibility separation instead.

Classical TDD works effectively with Kotlin and Spring testing frameworks by applying BDD nesting, state-based assertions, and decision table coverage. This Skill ensures your Kotlin/Spring teams can trust test suites without slipping back into mock-heavy habits.