Test run execution logging

When a test run starts in Testmo, the agent reads the assigned cases and, for automated results arriving from a connected pipeline, applies your rules to record each outcome as pass, fail, or skipped. It updates the run record and notifies the owner as milestones complete. Ambiguous results, flaky cases, or a run that stalls partway are not force-closed: the agent flags the run to the QA owner with the affected cases listed, so a person decides whether to retry, investigate, or mark it blocked.

Case result recording

As manual and exploratory testers work, the agent reads submitted results in Testmo, applies your rules to update case status and attach evidence like notes or screenshots, and keeps the run totals current. It notifies the lead when coverage targets are met. Results that conflict, such as the same case passing and failing across runs, or a case with missing required fields, are held for a person: the agent surfaces the discrepancy to the QA owner rather than overwriting, so the record reflects a human decision.

Failure-to-issue linking

On a failed result, the agent reads the failure details in Testmo, applies your rules, and where the connector allows, opens or links an issue in your connected tracker like Jira, GitHub, or GitLab, writing the reference back onto the case. It notifies the assignee with the failure context. Failures that look like duplicates or need triage judgment are not filed blindly: the agent proposes the link and notifies the QA owner, who confirms whether to open a new issue, attach to an existing one, or dismiss it.