rafaeltonholo/svg-to-compose/unit-test-author

Unit Test Author

Overview

Create focused, behavior-driven tests that follow this repository's testing conventions. Prefer commonTest and kotlin.test assertions, use Burst for parameterized cases, and run the smallest relevant test command first.

Workflow

1. Read .ai/guidelines.md and the target module AGENTS.md before writing

tests.

1. Locate the production code and existing nearby tests.
2. Mirror the package and source-set conventions:

• svg-to-compose: place tests in src/commonTest/kotlin/... unless

platform APIs are required.

• svg-to-compose-gradle-plugin: place tests in the module test source

sets (src/test or src/functionalTest) based on scope.

1. Write tests that verify observable behavior, not implementation details.
2. Prefer table-driven tests for many similar cases. Use Burst when it improves

readability.

1. Run narrow test commands first, then broader checks if requested.
2. Keep assertions explicit and deterministic.

Test Style Rules

• Use kotlin.test APIs (@Test, assertEquals, assertContentEquals,

assertTrue, assertNull, assertFailsWith).

• Use descriptive backtick test names that state behavior and condition.
• Follow Arrange/Act/Assert structure with minimal setup.
• Keep one primary behavior per test.
• Avoid flaky inputs (time, random, unordered collections) unless explicitly

controlled.

• Reuse existing helper methods/builders when available; avoid adding

unnecessary abstractions.

• Prefer fakes over mocks unless the behavior is platform-specific.

Parameterized Testing

• Use Burst for repeated input/output validation.
• Prefer compact datasets that still cover edge cases.
• Include boundary and malformed inputs when behavior defines fallbacks or

errors.

See references/kotlin-kmp-testing.md for patterns and command examples.

Execution Commands

Use the smallest useful command first:

./gradlew :svg-to-compose:allTests --tests "<FQN>"
./gradlew :svg-to-compose-gradle-plugin:test --tests "<FQN>"
./gradlew allTests
./gradlew cleanAllTests allTests

Completion Criteria

• New/changed behavior is covered by tests.
• Tests are deterministic and readable.
• Targeted test task passes.
• If broad verification is requested, run the broader test task and report

results.