groombook/app
Archived
13
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Set up Playwright E2E tests via MCP #80

New Issue
Closed
opened 2026-03-20 22:13:32 +00:00 by the-dogfather-cto[bot] · 2 comments
the-dogfather-cto[bot] commented 2026-03-20 22:13:32 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Context

Board directive to set up E2E testing. Tracked in Paperclip as GRO-77. Depends on unit test infrastructure (Phase 1).

Tasks

  1. Install Playwright as dev dependency
  2. Configure MCP connection to target the deployed groombook container in K8s namespace
  3. Write E2E tests for critical flows:
    • Login via OIDC (Authentik)
    • Appointment booking
    • Client management (create, edit, view)
    • Customer portal impersonation
  4. Add Playwright CI job in GitHub Actions (runs-on: runners-groombook)

Acceptance Criteria

  • Playwright E2E suite runs in CI against deployed namespace
  • Critical user flows covered
## Context Board directive to set up E2E testing. Tracked in Paperclip as GRO-77. Depends on unit test infrastructure (Phase 1). ## Tasks 1. Install Playwright as dev dependency 2. Configure MCP connection to target the deployed groombook container in K8s namespace 3. Write E2E tests for critical flows: - Login via OIDC (Authentik) - Appointment booking - Client management (create, edit, view) - Customer portal impersonation 4. Add Playwright CI job in GitHub Actions (`runs-on: runners-groombook`) ## Acceptance Criteria - Playwright E2E suite runs in CI against deployed namespace - Critical user flows covered
the-dogfather-cto[bot] commented 2026-03-20 22:26:42 +00:00 (Migrated from github.com)
Copy Link
Copy Source

CTO Technical Guidance

Playwright E2E is already set up (PR #43):

  • Config in apps/e2e/, runs Chromium
  • CI job runs after lint + unit tests
  • Currently mocks API calls via page.route()
  • 3 test files: navigation smoke, booking flow, clients

What this issue adds (MCP-based E2E against real deployment):

This is blocked until we have a stable K8s deployment in the groombook namespace. The current E2E suite mocks all API calls — running against a real deployed backend requires:

  1. A running PostgreSQL (CNPG) instance with seeded test data
  2. The API and web containers deployed and accessible
  3. MCP connection configured to target the namespace endpoint

Recommendation:

Keep this blocked until groombook/infra has a working deployment. In the meantime, the existing mock-based E2E suite provides good regression coverage for frontend flows.

Tracked in Paperclip as GRO-77 (assigned to Lint Roller, status: blocked).

## CTO Technical Guidance Playwright E2E is already set up (PR #43): - Config in `apps/e2e/`, runs Chromium - CI job runs after lint + unit tests - Currently mocks API calls via `page.route()` - 3 test files: navigation smoke, booking flow, clients ### What this issue adds (MCP-based E2E against real deployment): This is **blocked** until we have a stable K8s deployment in the `groombook` namespace. The current E2E suite mocks all API calls — running against a real deployed backend requires: 1. A running PostgreSQL (CNPG) instance with seeded test data 2. The API and web containers deployed and accessible 3. MCP connection configured to target the namespace endpoint ### Recommendation: Keep this blocked until `groombook/infra` has a working deployment. In the meantime, the existing mock-based E2E suite provides good regression coverage for frontend flows. Tracked in Paperclip as GRO-77 (assigned to Lint Roller, status: blocked).
the-dogfather-cto[bot] commented 2026-03-24 21:25:31 +00:00 (Migrated from github.com)
Copy Link
Copy Source

All testing infrastructure is in place. Phase 1 (unit/integration tests) and Phase 2 (Playwright E2E via MCP) are both complete and merged. Closing.

PRs merged: #85 (unit tests), #99 (factory tests), #101 (E2E login/impersonation), #92 (seed data/impersonation infra)

All testing infrastructure is in place. Phase 1 (unit/integration tests) and Phase 2 (Playwright E2E via MCP) are both complete and merged. Closing. PRs merged: #85 (unit tests), #99 (factory tests), #101 (E2E login/impersonation), #92 (seed data/impersonation infra)
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
New feature
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#80
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?