Closes DOCS-1203 ## Problem The docs E2E workflow only ever tested one hardcoded page: the Next.js quickstart. All other docs content had no E2E coverage. ## Solution This PR expands the initial scaffolding to generalize the Next.js quickstart tests, page runs and checks local links, to all pages affecting Docs content: - Add `resolveDocsScope` (`e2e/docs/utils/resolve-docs-scope.ts`) to map changed guide and troubleshooting `.mdx` files to their `/docs/...` page paths, and to expand changed `_partials` to every page that includes them (including transitively, through partials nested inside other partials). Federated guide sections (`graphql`, `database/extensions/wrappers`, `ai/python`, `deployment/terraform`, `deployment/ci`) and reference docs stay out of scope, and resolution is capped at 20 pages to keep runtime bounded. - Replace the single `quickstarts.spec.ts` test with a generic `docs-pages.spec.ts` that loads whatever pages are resolved, asserting each renders with an `<h1>` and that its docs-owned links resolve. - Add `run-e2e-docs.ts` so `pnpm e2e:docs` resolves scope locally (from commits since `origin/master`, plus staged/unstaged changes) and skips Playwright entirely when nothing in scope changed. - Update `.github/workflows/docs-e2e.yml` to widen the trigger paths to all guides/troubleshooting/partials, resolve scope in a dedicated step, skip the rest of the job when scope is empty, and accept a `page_paths` input for manual `workflow_dispatch` runs. - Rewrite `e2e/docs/README.md` to document the new scoping behavior, the override envs (`DOCS_E2E_PAGE_PATHS`, `DOCS_E2E_BASE_REF`), and how CI uses the suite. - `pnpm e2e:docs:all` is also added to run tests on every page locally. Good for scoping issues but should not be included in CI. ## Manual testing Walk through the following steps to verify this works: - [x] `pnpm e2e:docs` from repo root resolves the expected pages for a local guide edit and can run against local dev **Note:** Challenges with testing on local in part because of the long lag for first page load. Recommendation to use a hosted URL is added to docs. - [x] Editing a shared `_partials` file resolves to every page that includes it (including through nested partials) - [x] `pnpm e2e:docs` exits cleanly with no Playwright run when no in-scope files changed - [x] `git diff --name-only ... | pnpm -C e2e/docs resolve-docs-scope` prints the expected page list for a sample diff - [x] Workflow run on a PR that only touches `e2e/docs`/workflow files skips the Playwright steps - [x] Manual `workflow_dispatch` run with `page_paths` set tests only those pages - [x] Run `pnpm e2e:docs:all` to run the suite on all docs content, which takes awhile ## Next steps After this PR merges, we have the scaffolding to add more fun tests like a11y 😁 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added scoped Docs E2E runs that target eligible doc pages based on changes, plus manual page-targeted runs and an “all eligible pages” mode. * Introduced `DOCS_E2E_PAGE_PATHS` (and updated base ref/base URL behavior) to control which pages are tested. * **Bug Fixes** * Automatically skips Playwright setup when no relevant pages are in scope; Playwright reporting now uploads only on failure. * **Documentation** * Updated the Docs E2E README with new run/CI behavior, troubleshooting notes, and commands to inspect the resolved page list. * **Tests** * Added a Docs-owned pages E2E suite; removed the Next.js quickstart E2E spec. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
6.8 KiB
Docs E2E tests
This guide explains how to run Playwright end-to-end checks against docs pages this repo owns.
Use this suite when you change guides, troubleshooting entries, or shared
partials under apps/docs/content. It loads each in-scope page, checks that the
article renders, and verifies that docs-owned links in the article resolve.
This page covers:
- Set up — install the browser once
- Run the tests — the usual local command
- Choose a target URL — production, preview, or local docs
- Override which pages run — when the default git scope is wrong
- What the suite covers — in-scope paths and limits
- Debug failures — reports and traces
- How CI uses this suite — pull request behavior
Set up
-
From this directory, install the Playwright Chromium browser once:
cd e2e/docs pnpm exec playwright install chromium
Run the tests
By default, pnpm e2e:docs tests pages affected by your current changes:
commits since origin/master, plus staged and unstaged working-tree files. If
nothing in scope changed, the command exits successfully without starting
Playwright.
-
From the repository root, point the suite at a deployed docs site and run it:
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs -
Optional: open Playwright UI mode for the same scoped run:
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs:ui
You can also run from e2e/docs with pnpm run e2e:docs.
Choose a target URL
Tests use PLAYWRIGHT_BASE_URL. When unset, they default to the local docs
dev server at http://localhost:3001.
Prefer a deployed site for day-to-day checks. Use the local server only when you need unpublished content that production does not serve yet.
Deployed site
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs
For a protected Vercel preview, also set VERCEL_AUTOMATION_BYPASS_SECRET.
Local docs server
-
From the repository root, start docs in a separate terminal:
pnpm dev:docs -
Run the suite without
PLAYWRIGHT_BASE_URL, or set it tohttp://localhost:3001.
The local server needs a full monorepo install and credentials for some content.
Local runs are unreliable for pages whose docs-owned links point into
/docs/reference/* or /docs/guides/auth/server-side/*: reference pages can
take over a minute to compile on first request in dev mode, which exceeds the
suite's per-test timeout, and server-side auth guides have a known local-only
routing issue that 404s even though the page serves correctly in production.
Prefer a deployed site for pages that link into either of those sections.
Override which pages run
Leave DOCS_E2E_PAGE_PATHS unset to keep the default changed-files scope.
To test specific pages instead of the git diff:
DOCS_E2E_PAGE_PATHS=/docs/guides/getting-started/quickstarts/nextjs \
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs
To compare against a different base ref:
DOCS_E2E_BASE_REF=origin/develop \
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs
DOCS_E2E_PAGE_PATHS accepts a comma- or newline-separated list of /docs/...
paths.
Run every in-scope page
To test every guide and troubleshooting entry instead of a changed-files scope — for example, a periodic full-site check — run:
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs:all
This ignores DOCS_E2E_PAGE_PATHS and the 20-page cap described in
Limits, and tests every page listed by
pnpm -C e2e/docs resolve-docs-scope across the whole guides and
troubleshooting trees — several hundred pages as of this writing. --all
runs also default to --max-failures=0, so a full run isn't cut short by
playwright.config.ts's global maxFailures: 3. Expect a long run: the suite
runs one worker by default, so pass --workers to parallelize it, for
example:
PLAYWRIGHT_BASE_URL=https://supabase.com pnpm e2e:docs:all -- --workers=4
Run this against a deployed site, not the local dev server — see Local docs server for why local runs are unreliable for pages linking into reference docs or server-side auth guides.
What the suite covers
In scope
| Changed path | Behavior |
|---|---|
apps/docs/content/guides/**/*.mdx |
Test /docs/guides/<slug>, excluding federated sections |
apps/docs/content/troubleshooting/**/*.mdx |
Test /docs/guides/troubleshooting/<slug> |
apps/docs/content/_partials/** |
Test owned pages that include that partial |
Out of scope
- Federated guide sections:
graphql,database/extensions/wrappers,ai/python,deployment/terraform,deployment/ci - Reference docs under
/docs/reference - Non-docs routes such as
/dashboardand/ui, which the link checker skips
Limits
Resolved scope is capped at 20 pages so a widely shared partial cannot explode
runtime. If a change resolves to more pages than that, only the first 20 in
sorted order are tested and the rest are silently dropped from that run. To
test beyond the cap, use pnpm e2e:docs:all instead of raising it. See
Run every in-scope page.
To inspect the resolved list without running Playwright, replicate the same
scope pnpm e2e:docs uses by default: commits since origin/master, plus
staged and unstaged working-tree changes.
{
git diff --name-only --diff-filter=ACMR origin/master...HEAD
git diff --name-only --diff-filter=ACMR
git diff --name-only --diff-filter=ACMR --cached
} | pnpm -C e2e/docs resolve-docs-scope
Debug failures
-
Open the HTML report after a run:
pnpm -C e2e/docs exec playwright show-report -
Inspect traces and screenshots under
test-results/for failed runs.
How CI uses this suite
The workflow at .github/workflows/docs-e2e.yml runs on pull requests that touch
owned docs content, partials, or e2e/docs.
- Diff the pull request against its base branch and resolve in-scope page paths.
- Skip Playwright when nothing in scope changed.
- When
apps/docschanged, wait for the Vercel docs preview and setPLAYWRIGHT_BASE_URLto that preview. Otherwise use production. - Run the suite with
DOCS_E2E_PAGE_PATHSset to the resolved list.
Draft pull requests stay skipped until you mark them ready for review. Manual
workflow_dispatch runs require a page_paths input and accept an optional
base_url, which defaults to production.