Skip to content
SyntaxisSyntaxisSyntaxis

test-run

Runs designed cases against a real running application and writes a cycle record to syntaxis/qa/runs/<date>-<cycle>.md.

Invocation

Section titled “Invocation”
/test-run                    the active work's cases, plus smoke cases
/test-run checkout           one area
/test-run regression         every non-retired case in scope
/test-run TC-014 TC-021      exactly those cases

Results

Section titled “Results”
Result Meaning
pass The expected result was observed in full, including its negative half
fail The expected result was not observed
blocked The case could not be run; the record names the blocker
skipped Deliberately not run, with a reason

What it guarantees

Section titled “What it guarantees”
  • It never edits application source during a cycle; repairing mid-cycle invalidates the record.
  • It never weakens, skips, or rewrites a case to produce a pass.
  • Results are observed, never inferred. A partial pass is a fail. A flaky case is a fail.
  • Every failure opens a finding in syntaxis/context/findings.md, so P0 and P1 defects block /complete.
  • The exact commit, environment, and platform versions are recorded, or the record proves nothing.
  • Credentials and personal data are redacted from evidence.
  • The report says plainly what the cycle did not cover.
Section titled “Related”

/check proves one spec’s done-when criteria. /test-run executes a set of designed cases across areas. See Defects and Evidence.