一键在 Manus 中运行任何 Skill

tackle-mvi-tests

星标2

分支0

更新时间2026年6月14日 17:11

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

djkovrik

djkovrik/Tackle

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Tackle MVI Store Tests

Read AGENTS.md first for project testing conventions and store architecture.

Base Pattern

Put tests in the component module's src/commonTest/kotlin/.../store.
Extend StoreTest<XStore.Intent, XStore.State, XStore.Label>.
Use DefaultStoreFactory().
Pass Dispatchers.Unconfined for mainContext and ioContext.
Create the store with create(autoInit = false).
Call setUp() in @BeforeTest and tearDown() in @AfterTest.
Call store.init() inside tests that assert bootstrap behavior.
Assert state through store.state.
Assert labels through the inherited labels list.

Mocking

Use Mokkery mock, every, everySuspend, returns, throws, and verifySuspend.
Stub gateway interfaces, not concrete network/database/settings implementations.
Use mutable settings stubs for settings-like state.
Keep response fixtures or constants in Responses.kt and Constants.kt near the tests.

What To Test

Initial state before/after store.init().
Bootstrap success and failure.
Each user-facing intent.
State flags for loading/progress/empty/error.
One-shot labels, especially ErrorCaught and navigation labels.
Rollback behavior for optimistic updates.
Pagination edge cases: first page, next page, last page, failed page.
Cross-state derived behavior such as selected votes, text counters, menu actions, and availability flags.

Assertions

Use assertk.
Prefer specific state and label assertions over broad non-empty checks.
Use runTest for coroutine tests.
Avoid timing sleeps. If a manager exposes delay, stub it to 0L.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. Run .\gradlew.bat detekt before final handoff if code was changed.

同仓库更多 Skills

同仓库

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

Tackle MVI Store Tests

Read AGENTS.md first for project testing conventions and store architecture.

Base Pattern

Put tests in the component module's src/commonTest/kotlin/.../store.
Extend StoreTest<XStore.Intent, XStore.State, XStore.Label>.
Use DefaultStoreFactory().
Pass Dispatchers.Unconfined for mainContext and ioContext.
Create the store with create(autoInit = false).
Call setUp() in @BeforeTest and tearDown() in @AfterTest.
Call store.init() inside tests that assert bootstrap behavior.
Assert state through store.state.
Assert labels through the inherited labels list.

Mocking

Use Mokkery mock, every, everySuspend, returns, throws, and verifySuspend.
Stub gateway interfaces, not concrete network/database/settings implementations.
Use mutable settings stubs for settings-like state.
Keep response fixtures or constants in Responses.kt and Constants.kt near the tests.

What To Test

Initial state before/after store.init().
Bootstrap success and failure.
Each user-facing intent.
State flags for loading/progress/empty/error.
One-shot labels, especially ErrorCaught and navigation labels.
Rollback behavior for optimistic updates.
Pagination edge cases: first page, next page, last page, failed page.
Cross-state derived behavior such as selected votes, text counters, menu actions, and availability flags.

Assertions

Use assertk.
Prefer specific state and label assertions over broad non-empty checks.
Use runTest for coroutine tests.
Avoid timing sleeps. If a manager exposes delay, stub it to 0L.

Verification

Run .\gradlew.bat testDebugUnitTest after changing tests. Run .\gradlew.bat detekt before final handoff if code was changed.