Run any Skill in Manus with one click

tackle-unit-tests

Stars2

Forks0

UpdatedJune 14, 2026 at 17:11

Write or update non-component unit tests in the Tackle Kotlin Multiplatform project. Use when testing domain managers, mappers, utilities, database behavior, settings wrappers, network response mapping, or other commonTest code that is not a MVIKotlin store or Decompose component.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

djkovrik

djkovrik/Tackle

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	tackle-unit-tests
description	Write or update non-component unit tests in the Tackle Kotlin Multiplatform project. Use when testing domain managers, mappers, utilities, database behavior, settings wrappers, network response mapping, or other commonTest code that is not a MVIKotlin store or Decompose component.

Tackle Unit Tests

Read AGENTS.md first for module roles, data flow, and validation commands.

Choose The Test Style

Domain manager tests: plain common tests with Mokkery gateway/tool mocks.
Network mapper tests: extend JsonBasedTest, parse JSON fixtures from src/commonTest/resources/responses, and assert mapped domain values.
Utility tests: plain common tests under the utility module.
Database-like behavior: prefer TackleTestDatabase or direct mapper tests unless the change specifically needs SQLDelight integration.
Settings behavior: test TackleSettingsInternal through a test Settings implementation when needed.

Domain Manager Tests

Instantiate the manager directly.
Mock only its gateway interfaces.
Assert returned Result success/failure and key payload fields.
Verify gateway calls with exact parameters.
Cover branching logic, especially current-locale decisions and toggle methods that choose between paired API calls.

Mapper Tests

Add a realistic JSON fixture under the module's src/commonTest/resources/responses.
Parse with responseFromFile<Dto>("src/commonTest/resources/responses/file.json").
Map DTO to domain model.
Assert required fields, optional defaults, nested lists, enums, dates, and fallback behavior.
Keep response DTOs internal; tests in the same module can access them.

Utility Tests

Keep tests small and deterministic.
Cover edge cases: empty strings, invalid dates, unknown MIME extensions, null numeric helpers, URL normalization, and regex matches.
For time-sensitive functions, pass explicit now or timezone parameters when the utility allows it.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. If production code changed, also run .\gradlew.bat assembleDebug and final .\gradlew.bat detekt.

More from this repository

same repository

tackle-component-tests

djkovrik/Tackle

Write or update unit tests for Decompose components in the Tackle Kotlin Multiplatform project. Use when testing component models, child navigation, child item creation, ComponentOutput propagation, lifecycle cleanup, or component method wiring.

2026-06-142

tackle-decompose

djkovrik/Tackle

Create or update Decompose components and navigation in the Tackle Kotlin Multiplatform project. Use when adding a new screen/component, wiring component gateways, adding child stacks/slots/items, connecting a component to Compose UI, or propagating ComponentOutput events.

2026-06-142

tackle-mvi

djkovrik/Tackle

Create or update MVIKotlin stores in the Tackle Kotlin Multiplatform project. Use when adding a new component store, changing store intents/state/labels, wiring a domain manager into a store, or adapting store state to a Decompose component model.

2026-06-142

tackle-mvi-tests

djkovrik/Tackle

Write or update unit tests for MVIKotlin stores in the Tackle Kotlin Multiplatform project. Use when testing store bootstrap, intents, reducer state, labels, error labels, optimistic updates, or pagination behavior.

2026-06-142

name	tackle-unit-tests
description	Write or update non-component unit tests in the Tackle Kotlin Multiplatform project. Use when testing domain managers, mappers, utilities, database behavior, settings wrappers, network response mapping, or other commonTest code that is not a MVIKotlin store or Decompose component.

Tackle Unit Tests

Read AGENTS.md first for module roles, data flow, and validation commands.

Choose The Test Style

Domain manager tests: plain common tests with Mokkery gateway/tool mocks.
Network mapper tests: extend JsonBasedTest, parse JSON fixtures from src/commonTest/resources/responses, and assert mapped domain values.
Utility tests: plain common tests under the utility module.
Database-like behavior: prefer TackleTestDatabase or direct mapper tests unless the change specifically needs SQLDelight integration.
Settings behavior: test TackleSettingsInternal through a test Settings implementation when needed.

Domain Manager Tests

Instantiate the manager directly.
Mock only its gateway interfaces.
Assert returned Result success/failure and key payload fields.
Verify gateway calls with exact parameters.
Cover branching logic, especially current-locale decisions and toggle methods that choose between paired API calls.

Mapper Tests

Add a realistic JSON fixture under the module's src/commonTest/resources/responses.
Parse with responseFromFile<Dto>("src/commonTest/resources/responses/file.json").
Map DTO to domain model.
Assert required fields, optional defaults, nested lists, enums, dates, and fallback behavior.
Keep response DTOs internal; tests in the same module can access them.

Utility Tests

Keep tests small and deterministic.
Cover edge cases: empty strings, invalid dates, unknown MIME extensions, null numeric helpers, URL normalization, and regex matches.
For time-sensitive functions, pass explicit now or timezone parameters when the utility allows it.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. If production code changed, also run .\gradlew.bat assembleDebug and final .\gradlew.bat detekt.