Rbanh/schemeta
1
0
Fork 0
Code Issues 11 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Add Playwright regression flow to CI for core UI interactions #11

New Issue
Closed
opened 2026-02-18 21:33:31 -05:00 by Rbanh · 1 comment
Rbanh commented 2026-02-18 21:33:31 -05:00
Owner
Copy Link

Objective

Add browser-based regression flow to CI for key interaction paths validated manually.

Scope

  • Introduce Playwright-driven CLI/script flow in CI job.
  • Cover: selection/deselect, schema modal open/close, destructive confirm path, migration preview/apply gate, mode switch + auto tidy.
  • Fail CI on interaction regressions.

Acceptance Criteria

  • CI executes Playwright scenario reliably on push/PR.
  • Fails on broken interaction path.
  • Artifacts/logs available for failed runs.
## Objective Add browser-based regression flow to CI for key interaction paths validated manually. ## Scope - Introduce Playwright-driven CLI/script flow in CI job. - Cover: selection/deselect, schema modal open/close, destructive confirm path, migration preview/apply gate, mode switch + auto tidy. - Fail CI on interaction regressions. ## Acceptance Criteria - CI executes Playwright scenario reliably on push/PR. - Fails on broken interaction path. - Artifacts/logs available for failed runs.
Rbanh added this to the Phase 3 - Browser QA and UX Consistency milestone 2026-02-18 21:33:52 -05:00
Rbanh commented 2026-02-18 21:44:52 -05:00
Author
Owner
Copy Link

Completed in commit d5836a2.

Delivered:

  • Added Playwright-driven browser regression runner (tests/ui-regression-runner.js).
  • Wired CI workflow to install Chromium and execute browser flow.
  • Added failure artifact listing for easier triage.

Validation:

  • Local run: npm run test:ui
  • CI workflow updated in .gitea/workflows/ci.yml
Completed in commit `d5836a2`. Delivered: - Added Playwright-driven browser regression runner (`tests/ui-regression-runner.js`). - Wired CI workflow to install Chromium and execute browser flow. - Added failure artifact listing for easier triage. Validation: - Local run: `npm run test:ui` - CI workflow updated in `.gitea/workflows/ci.yml`
Rbanh closed this issue 2026-02-18 21:45:00 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Phase 3 - Browser QA and UX Consistency
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Rbanh/schemeta#11
No description provided.
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?