OpenParable
Skip to content
← Back to skills

Write E2e Tests

Testing & Quality
write-e2e-tests

Write E2e Tests is an Agent Skill for testing & quality published in the igorescodro/alkaa repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when writing or modifying end-to-end tests in the Alkaa project — triggers on tasks like "add an E2E test", "write a flow test", "test this feature end-to-end", "add a test to shared module", or "cover this user journey with a test".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/igorescodro/alkaa/blob/HEAD/.claude/skills/write-e2e-tests/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/write-e2e-tests, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Write E2E Tests

Overview

E2E tests exercise full application flows through a real Koin DI graph and a live AlkaaMultiplatformApp Compose tree. They live in shared/src/commonTest/kotlin/com/escodro/alkaa/ — one file per feature domain (e.g., TaskFlowTest, CategoryFlowTest).

Structure

  • Class setup — Extends AlkaaTest(), KoinTest; @BeforeTest calls beforeTest() first, then cleans DAOs → see references/SETUP.md
  • Entry point — = uiTest { } for all tests; = flakyUiTest { } only for known timing-sensitive tests → see references/SETUP.md
  • Data seeding — Insert directly via DAOs in @BeforeTest using runTest → see references/SETUP.md
  • Navigation helpers — Private ComposeUiTest extension functions using content descriptions → see references/SETUP.md
  • Assertions — Existence, wait helpers, selection state, semantic matchers → see references/SETUP.md
  • Fake dependencies — declare<T> { FakeImpl() } to override external dependencies → see references/SETUP.md

Naming

Descriptive, underscore-separated. Two styles:

  • State-driven: when_no_query_then_all_tasks_are_visible()
  • Action-driven: add_and_open_task(), complete_task_from_list()

No camelCase, no backtick names.

Rules

RuleDetails
beforeTest() firstCall beforeTest() before any DAO injection or by inject() use
cleanTable() in @BeforeTestCall on every DAO used to avoid state leakage between tests
DAO-based seedingInsert test data directly via DAOs — not via use cases
Content descriptions for navigationNavigate via content descriptions, not raw text
Resource stringsgetString(Res.string.xyz) inside uiTest or runComposeUiTest — never hardcode
Fakes over mocksUse declare<T> { FakeImpl() } for external dependencies
@AfterTest alwaysAlways call afterTest() to stop Koin after each test

Common Mistakes

MistakeFix
Calling by inject() before beforeTest()Always call beforeTest() first
Skipping cleanTable()Call on every DAO to avoid state leakage
Using flakyUiTest by defaultReserve for tests with known timing sensitivity
Hardcoding UI stringsUse getString(...) inside uiTest or runComposeUiTest
Testing multiple flows in one testOne scenario per test
Missing @AfterTest / afterTest()Always stop Koin after each test
Navigation via raw textNavigate via content descriptions
Using mocksUse fakes via declare<T> { FakeImpl() }