القائمة
Unit-test a use case with hand-written fake repositories. Use when asked to "test a use case", "add use case tests", or to verify a use case's aggregation and error-propagation logic.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a screen's composables to a feature module using the Route → Screen → Content structure. Use when asked to "add a screen", "build the <X> screen", "wire up a screen's UI", or to render a feature's state. Pairs with add-viewmodel.
Add a ViewModel to a feature module using the Action / State / Event triad, depending on use case / repository interfaces. Use when asked to "add a viewmodel" or to wire a screen's state, actions, and events. The screen's composables are a separate skill (add-screen).
Add a reusable design-system Composable to the :ui module — stateless, themed via RickAndMortyTheme tokens, with a preview. Use when asked to "add a button", "add a shared component", "add a card/loader/empty state", or to build any reusable UI primitive shared across screens.
Unit-test a ViewModel's Action → State → Event behaviour with fakes. Use when asked to "test a viewmodel", "add viewmodel tests", or to verify a screen's state transitions and one-time events.
Add a repository to :data:core as composable single-unit repositories ([Verb][Name]Repository) encapsulated by a parent contract, each mapping a data source's RemoteResult into DataResult. Use when asked to "add a repository", "wire up a repository", or to expose data-layer operations to domain/presentation.
Unit-test a repository with a hand-written fake data source. Use when asked to "test a repository", "add repository tests", or to verify a [Verb][Name]Repository maps RemoteResult into DataResult correctly.
| name | add-usecase-test |
| description | Unit-test a use case with hand-written fake repositories. Use when asked to "test a use case", "add use case tests", or to verify a use case's aggregation and error-propagation logic. |
A use case exists to aggregate repositories, so its test hands it fakes of
the repository contracts and asserts the aggregation — the combined result and
each error path. No Koin, no Android. (A one-shot passthrough has no use case to
test — see add-usecase.)
:data:domain needs kotlinx-coroutines-test (for runTest); JUnit comes from
the library convention plugin. Add via add-dependency if missing.
A repository's parent contract is public and its children are fun interfaces,
so a fake exposes them as overridable vals with safe defaults:
class FakeCharacterRepository(
override val getCharacter: GetCharacterRepository =
GetCharacterRepository { DataResult.Error("not stubbed") },
override val getCharacters: GetCharactersRepository =
GetCharactersRepository { DataResult.Error("not stubbed") },
) : CharacterRepository
src/test/java/.../<feature>/GetCharacterWithEpisodesUseCaseImplTest.kt:
class GetCharacterWithEpisodesUseCaseImplTest {
@Test
fun `combines a character with its episodes`() = runTest {
val useCase = GetCharacterWithEpisodesUseCaseImpl(
characterRepository = FakeCharacterRepository(
getCharacter = GetCharacterRepository { DataResult.Success(character) },
),
episodeRepository = FakeEpisodeRepository(
getEpisodes = GetEpisodesRepository { DataResult.Success(episodes) },
),
)
val result = useCase(1)
assertTrue(result is DataResult.Success)
assertEquals(episodes, (result as DataResult.Success).data.episodes)
}
@Test
fun `fails fast when a repository errors`() = runTest {
val useCase = GetCharacterWithEpisodesUseCaseImpl(
characterRepository = FakeCharacterRepository(
getCharacter = GetCharacterRepository { DataResult.Error("boom") },
),
episodeRepository = FakeEpisodeRepository(),
)
assertTrue(useCase(1) is DataResult.Error)
}
}
The point: a use case earns a test because it has aggregation logic — cover the combine path and each short-circuit/error path. The aggregation is the only thing worth asserting here.
./gradlew :data:domain:testDebugUnitTest --console=plain
(Set JAVA_HOME to a JDK 21 — e.g. an SDKMAN *-jbr — if the shell can't find
Java.)
fun interface
children with safe defaults).:data:domain:testDebugUnitTest passes.