From bb2fcf0e9b9b52f61f4d9073eac20e1c3ae34274 Mon Sep 17 00:00:00 2001 From: Vijit Dhingra Date: Sat, 14 Mar 2026 15:43:39 -0700 Subject: [PATCH] docs: add CI-level E2E testing note to /qa section Readers using /qa for branch-level testing may not realize their critical flows should also run automatically on every deploy. Added a note pointing to platforms like Lark as an example. Made-with: Cursor --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 3e32fa8..ed8a422 100644 --- a/README.md +++ b/README.md @@ -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`