Runs

Track manual test execution. Run records are stored as JSON in .tms/runs/ and committed with the project, so execution history travels with your repo.

#Recording a run

• A new-run wizard lets you pick the suite scope, select cases, and enter results.
• For each case you record a result: pass / fail / skip / pending, with a free-form reason.

#History and detail

• A run history list shows past runs, filterable by status.
• A run detail view shows the case preview next to the recorded result. Results stay editable post-run, so you can correct or update them.

#Scope

Runs cover manual execution tracking. Kensa deliberately does not run automated tests or ingest CI results - that's a separate concern from managing the test cases themselves. The dashboard surfaces an execution-rate metric derived from recorded runs.