From 7dcecd02dd52807b5e02eb3c68d0a5ec61073d4d Mon Sep 17 00:00:00 2001 From: Chris Farhood Date: Fri, 22 May 2026 11:40:16 +0000 Subject: [PATCH] docs: add MCP-driven execution method to UAT playbook (GRO-1502) UAT is now executed by Shedward Scissorhands via the groombook-playwright MCP server. Added execution method section documenting MCP tools and how test case steps map to MCP calls. Co-Authored-By: Paperclip --- UAT_PLAYBOOK.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/UAT_PLAYBOOK.md b/UAT_PLAYBOOK.md index d3e9410..f8d10dc 100644 --- a/UAT_PLAYBOOK.md +++ b/UAT_PLAYBOOK.md @@ -7,6 +7,23 @@ --- +## Execution Method + +All UAT is executed by **Shedward Scissorhands** via the **groombook-playwright MCP server**. No manual browser checks or scripted test suites are used for UAT. + +Shedward uses the `mcp__playwright-groombook__*` tool family to navigate, interact with, and verify the site. Each test case step is executed via MCP browser tools: + +- **"Navigate to [URL]"** → `browser_navigate` +- **"Locate/Read [element]"** → `browser_snapshot` to inspect the accessibility tree +- **"Click [element]"** → `browser_click` with element ref from snapshot +- **"Verify [content]"** → `browser_snapshot` and check text matches +- **"Check mobile responsiveness"** → `browser_resize` + `browser_snapshot` +- **"Check console errors"** → `browser_console_messages` + +Shedward reads this playbook, executes each test case via MCP tools, captures evidence (snapshots/screenshots), and reports pass/fail per test case. + +--- + ## 1. Homepage Messaging Path C Refresh ### Purpose -- 2.52.0