Skip to Content
DocsWelcome

klera docs

End-to-end tests that survive your next redesign.

klera is LLM-native E2E testing for Expo / React Native. Write flows in plain prose; klera compiles them to a deterministic IR, runs them on real simulators and devices, self-heals across UI drift, and ships every failure with a verdict, suspect commit, and proposed fix.

# Sign in and see today's notifications Sign in with the seeded test user, dismiss the onboarding modal, and assert that the home screen shows today's notifications. Take a visual snapshot called "home-after-login".

That is the whole flow file (flows/login.flow.md). klera compiles it to a deterministic IR cache committed alongside (.flow.json — plumbing — adopters never hand-edit it). At run time klera walks a strategy ladder (testID → accessibilityLabel → role+text → fuzzy text), self-heals across UI drift, and ships failures with PNG triplets, matcher traces, and PM + engineer narratives.

Pick your starting point

Then go deep

  • Authoring flows — the prose syntax, the YAML escape hatch, the full IR step reference, fixtures and secrets, network mocks, visual snapshots.
  • Running flows — every CLI command and flag, watch mode for fast iteration, recording, the JSON / HTML / JUnit report.
  • Debugging — the four-verdict triage, the failure-evidence directory, the matcher’s strategy ladder, how the planner stays correct under hallucination pressure.
  • Integrations — CI scaffolds for GitHub Actions / GitLab / CircleCI, OpenTelemetry wiring, the MCP server, planner transports (API / local CLI / manual / MCP), JSON Schema editor support.
  • Platforms — iOS and Android driver composites, native module setup, sim-host / emulator-host actions.
  • Contributing — code conventions, release flow, where the changelog lives.
  • Reference — the canonical Flow JSON Schema.

Stay current

The version label in the navbar tracks @klera/cli. APIs may shift before v1; we will tell you when v1 cuts.

Last updated on