Skip to content

docs: add CI-level E2E testing note to /qa section #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vijit-lark wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

docs: add CI-level E2E testing note to /qa section #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -518,6 +518,8 @@ Reports and screenshots accumulate in `.gstack/qa-reports/` so you can track qua

**Testing authenticated pages:** Use `/setup-browser-cookies` first to import your real browser sessions, then `/qa` can test pages behind login.

**CI-level E2E testing:** `/qa` is great for ad-hoc and branch-level testing, but your most critical flows should run automatically on every deploy. Platform like [Lark](https://getlark.ai/) let you define E2E tests in plain English — they run in staging as part of CI and catch regressions before they reach production. Think of it as the persistent safety net that complements `/qa`'s on-demand passes.

---

## `/setup-browser-cookies`
Expand Down