Skip to content
SyntaxisSyntaxisSyntaxis

automate

Writes tests into the harness the project already has, one test per case, titled with the case ID.

Invocation

Section titled “Invocation”
/automate                    propose the highest-value cases
/automate checkout           the eligible cases in that area
/automate TC-014 TC-015      exactly those cases

It never automates every case by default. A suite that outgrows its value gets deleted rather than fixed.

Selection

Section titled “Selection”

A case is automated only when its behaviour is stable, deterministic, repeated, and observable by the harness. Visual judgement, real payments, biometrics, and browser permission dialogs stay manual — a legitimate outcome, reported as such.

What it guarantees

Section titled “What it guarantees”
  • It never installs a harness. /tests browser and /tests mobile own setup.
  • It never invents a case.
  • It asserts the full expected result, including its negative half.
  • No fixed sleeps, no retries to mask flakiness. A flaky test is not a passing test.
  • Each new test is proven able to fail before it is reported as covering anything.
  • Credentials and authentication state are never committed.
  • The suite is not added to Verify or CI without a separate request.

See Web Automation and Mobile Automation.