Use for fast Kotest unit/component tests: domain logic, application services with fakes, builders, focused test data, or /unit-tests. Use /integration-tests for real adapters. Use /e2e-tests for app boot.
التثبيت
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use for fast Kotest unit/component tests: domain logic, application services with fakes, builders, focused test data, or /unit-tests. Use /integration-tests for real adapters. Use /e2e-tests for app boot.
Unit Tests
Rules
Test behavior through public interfaces, not private functions or implementation details.
Keep tests fast and local. Avoid application boot, Kafka, and Testcontainers.
Use Kotest FunSpec.
Use fakes, builders, and focused test data at system boundaries.
Keep setup small and tests easy to read.
Split tests when a class requires too much context.
Checklist
Choose the behavior to prove.
Select the test boundary: domain, application service, or adapter with fakes.
Write a focused FunSpec test.
Run the targeted test with ./gradlew test --tests.
