uat-run

User Acceptance Testing pre-checks are automated by executing SQL queries and shell commands to validate system prerequisites before manual testing begins. This interactive proctor orchestrates these non-destructive checks against a project-specific markdown checklist to verify environment readiness.

A UAT checklist for automated validation should be structured as a project-specific markdown file. The interactive proctor parses this markdown to orchestrate automated pre-checks and present test sections sequentially for guided manual verification.

Guided User Acceptance Testing handles bug tracking by standardizing the capture of test failures directly into the project's inbox. During the interactive walkthrough, the proctor logs identified defects with automated priority and type inference for seamless tracking.

Yes, a local database MCP tool and shell environment are required to run interactive UAT workflows. These integrations enable the proctor to execute non-destructive SQL queries and shell commands during the automated pre-validation phase.

Yes, you can execute SQL queries during User Acceptance Testing without damaging data because the proctor performs only non-destructive validation tasks. It leverages local database MCP tools to verify prerequisites safely before manual testing begins.

An interactive UAT proctor removes friction from quality assurance by automating pre-checks and standardizing failure capture, whereas manual checklists lack automated validation. It orchestrates structured verification workflows and logs bugs with inferred priority directly into your project inbox.