|
|
|
@@ -2,8 +2,25 @@
|
|
|
|
|
|
|
|
|
|
## Test Environment
|
|
|
|
|
- **URL:** https://groombook.farh.net (demo)
|
|
|
|
|
- **Repository:** https://github.com/groombook/site
|
|
|
|
|
- **Last Updated:** 2026-05-12
|
|
|
|
|
- **Repository:** https://git.farh.net/groombook/groombook.dev
|
|
|
|
|
- **Last Updated:** 2026-05-26
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## 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.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
@@ -76,6 +93,52 @@ Verify homepage copy aligns with Path C strategy (solo/small operator focus) wit
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## 3. Self-Booking CTA (GRO-1791)
|
|
|
|
|
|
|
|
|
|
### Purpose
|
|
|
|
|
Verify "Book an Appointment" is the primary CTA in the hero section, "Book Now" appears in navigation, and all CTAs are present and mobile-responsive.
|
|
|
|
|
|
|
|
|
|
### Pre-Conditions
|
|
|
|
|
- Homepage loads successfully
|
|
|
|
|
- User is not logged in
|
|
|
|
|
|
|
|
|
|
### Test Cases
|
|
|
|
|
|
|
|
|
|
#### TC-3.1: Hero CTA - Book an Appointment
|
|
|
|
|
| Step | Action | Expected Result |
|
|
|
|
|
|------|--------|-----------------|
|
|
|
|
|
| 1 | Navigate to homepage | Page loads without errors |
|
|
|
|
|
| 2 | Locate hero CTA buttons | "Book an Appointment →" is the first button in the hero CTA group |
|
|
|
|
|
| 3 | Click "Book an Appointment →" button | Navigates to https://groombook.dev/admin/book (the 4-step booking wizard) |
|
|
|
|
|
|
|
|
|
|
#### TC-3.2: Hero CTA - All Buttons Present
|
|
|
|
|
| Step | Action | Expected Result |
|
|
|
|
|
|------|--------|-----------------|
|
|
|
|
|
| 1 | Locate hero CTA buttons | All 4 buttons present: "Book an Appointment", "Try the Demo", "View on GitHub", "Get Started" |
|
|
|
|
|
| 2 | Verify button order | "Book an Appointment" is first |
|
|
|
|
|
|
|
|
|
|
#### TC-3.3: Mobile Responsiveness - Hero CTA (375px)
|
|
|
|
|
| Step | Action | Expected Result |
|
|
|
|
|
|------|--------|-----------------|
|
|
|
|
|
| 1 | Resize browser to 375px width | Page is responsive |
|
|
|
|
|
| 2 | Locate hero CTA buttons | "Book an Appointment" button is visible and properly sized |
|
|
|
|
|
| 3 | Verify flex-wrap | CTA buttons wrap gracefully on small screens |
|
|
|
|
|
|
|
|
|
|
#### TC-3.4: Footer Navigation - Book Now
|
|
|
|
|
| Step | Action | Expected Result |
|
|
|
|
|
|------|--------|-----------------|
|
|
|
|
|
| 1 | Scroll to footer | "Book Now" appears in footer navigation links |
|
|
|
|
|
| 2 | Click "Book Now" link | Navigates to https://groombook.dev/admin/book |
|
|
|
|
|
|
|
|
|
|
#### TC-3.5: Getting Started Page - Booking CTA
|
|
|
|
|
| Step | Action | Expected Result |
|
|
|
|
|
|------|--------|-----------------|
|
|
|
|
|
| 1 | Navigate to getting-started page | Page loads |
|
|
|
|
|
| 2 | Locate "Book an Appointment" link | "Book an Appointment →" link present in Quick Links section |
|
|
|
|
|
| 3 | Click "Book an Appointment →" link | Navigates to https://groombook.dev/admin/book |
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Pass/Fail Criteria
|
|
|
|
|
|
|
|
|
|
- **PASS:** All test cases execute successfully with expected results
|
|
|
|
@@ -88,3 +151,4 @@ Verify homepage copy aligns with Path C strategy (solo/small operator focus) wit
|
|
|
|
|
- UAT should be performed on both desktop and mobile viewports
|
|
|
|
|
- Check browser console for JavaScript errors during test execution
|
|
|
|
|
- Verify all links are functional and lead to expected destinations
|
|
|
|
|
- Mobile viewport test (TC-3.3) must be executed at exactly 375px width per acceptance criteria
|
|
|
|
|