Run any Skill in Manus with one click

tackle-component-tests

Stars2

Forks0

UpdatedJune 14, 2026 at 17:11

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.

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-component-tests
description	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.

Tackle Decompose Component Tests

Read AGENTS.md first for component tree, output flow, and testing conventions.

Base Pattern

Put tests in src/commonTest/kotlin/.../integration.
Extend ComponentTest<XComponent>.
Create the component with DefaultComponentContext(lifecycle).
Use DefaultStoreFactory() for store-backed components.
Pass testDispatchers from ComponentTest.
Pass output = { componentOutput.add(it) } or the matching callback name.
Read current state from component.model.value.
ComponentTest.setUp() resumes the lifecycle; tearDown() clears outputs and resets main-thread assertion behavior.

What To Test

Component creation and initial model.
Public component methods map to the right store intents or child behavior.
Store labels become ComponentOutput.
Errors become ComponentOutput.Common.ErrorCaught.
Parent-handled outputs are consumed locally when intended.
Forwarded outputs reach componentOutput.
Navigation values update: childStack, ChildSlot, LazyChildItems.
Child factory methods create children with correct inputs, when the method is internal and already tested in the project.

Navigation Checks

For stack components, assert childStack.value.active.instance.
For slots, trigger activation/dismissal and assert slot.child?.instance.
For lists, read component.items.value.items and activeItems.
Use existing tests such as StatusListComponentTest, AuthComponentTest, and editor child component tests as templates.

Mocking

Mock gateway interfaces with Mokkery.
Stub settings/tools/database narrowly.
Do not instantiate platform factories or real network/database modules in component tests.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. Run .\gradlew.bat assembleDebug if component wiring changed.

More from this repository

same repository

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

tackle-unit-tests

djkovrik/Tackle

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.

2026-06-142

name	tackle-component-tests
description	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.

Tackle Decompose Component Tests

Read AGENTS.md first for component tree, output flow, and testing conventions.

Base Pattern

Put tests in src/commonTest/kotlin/.../integration.
Extend ComponentTest<XComponent>.
Create the component with DefaultComponentContext(lifecycle).
Use DefaultStoreFactory() for store-backed components.
Pass testDispatchers from ComponentTest.
Pass output = { componentOutput.add(it) } or the matching callback name.
Read current state from component.model.value.
ComponentTest.setUp() resumes the lifecycle; tearDown() clears outputs and resets main-thread assertion behavior.

What To Test

Component creation and initial model.
Public component methods map to the right store intents or child behavior.
Store labels become ComponentOutput.
Errors become ComponentOutput.Common.ErrorCaught.
Parent-handled outputs are consumed locally when intended.
Forwarded outputs reach componentOutput.
Navigation values update: childStack, ChildSlot, LazyChildItems.
Child factory methods create children with correct inputs, when the method is internal and already tested in the project.

Navigation Checks

For stack components, assert childStack.value.active.instance.
For slots, trigger activation/dismissal and assert slot.child?.instance.
For lists, read component.items.value.items and activeItems.
Use existing tests such as StatusListComponentTest, AuthComponentTest, and editor child component tests as templates.

Mocking

Mock gateway interfaces with Mokkery.
Stub settings/tools/database narrowly.
Do not instantiate platform factories or real network/database modules in component tests.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. Run .\gradlew.bat assembleDebug if component wiring changed.