Documentation

Domains / qa-basic

QA domain

Tool-agnostic test strategy: a living coverage map and durable testing standards.

Use it when: A QA team tracks how each requirement is verified, independent of the test runner.

cumaru install agent <agent> --domain qa-basic

Pillars

PillarLifetimeHolds
coverage/DurableAreas under test, levels, and Given-When-Then scenarios.
standards/DurableTesting conventions: mocking, data, gates, flakiness, environments.
intake/TransientWhat must be verified: requests, bug reports, requirements.
plans/TransientTest campaigns with strategy, scope, cases, and handoffs.
exploring/TransientExploratory-testing charters. Never loaded by default.

Roles

  • Lead (QA): plans campaigns, maintains coverage/, owns standards/ and exploring/.
  • Dev (tester): executes campaign cases inside the active plan.

Lifecycle

  • intake/ and exploring/ -> plans/ -> coverage/; standards/ govern coverage/ through relates.
  • Before an intake item is removed, its coverage owner keeps the acceptance fact and a stable tracker reference.

Skills

Domain-specific skills, in addition to the universal ones: cumaru-intake,cumaru-explore,cumaru-plan,cumaru-coverage,cumaru-absorb.

Bootstrap

No domain bootstrap document. cumaru bootstrap prints the universal rules.

Domain rules

  • targets: lists test levels (unit, integration, e2e, contract, performance, all, meta).
  • Requirements use EARS or RFC 2119; coverage scenarios use Given-When-Then.

Example: Guard a reported bug

  1. intake/BUG-42 states the expected behavior in EARS.
  2. A campaign plan adds an integration scenario in Given-When-Then.
  3. cumaru-absorb writes the scenario into coverage/ with the tracker reference and removes the plan.

Source: domain.md, config.yaml, roles, skills at revision 37ad79f. The example is a summary of the shipped recipes, not CLI output.

Back to the comparison