Skip to content

test(e2e): status page journeys (public, subscriptions and emails) - #1186

Open
mortondev wants to merge 10 commits into
test/product-e2e-statusfrom
test/product-e2e-status-public
Open

mortondev wants to merge 10 commits into
test/product-e2e-statusfrom
test/product-e2e-status-public

Conversation

@mortondev

@mortondev mortondev commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

Status page product e2e journeys, part 2 of 3 (public page, feed, subscriptions, emails). Stacked on #1172 (test/product-e2e-status) → #1150.

Covered (ids per spec file and tier)

Spec @smoke @core @nightly @quarantine
public-page.spec.ts P-01, P-02, P-03, P-04, P-08, P-10/P-11, P-14 P-12, P-13, P-19, P-28 P-15
feed.spec.ts P-20 P-21
subscribe.spec.ts S-01, S-02, S-03/S-04, S-05, S-06 S-07 S-09
emails.spec.ts S-10 S-11, S-12, S-13, S-14, S-15, S-16, S-19/S-20, S-21, S-24 S-22, S-26, S-29 S-23, S-30

Lower layer, already proved by src/routes/status/__tests__/feed.test.ts (no new tests): P-22 (cap keeps what is open, :175), P-24 (escaping, line breaks, :279/:285/:333), P-25 (links at the status host, :359).

Also here: the helpers delete every incident a test made (deleteMadeIncidents in afterEach). The feed keeps each open incident's newest entry inside its 50-item cap, so open incidents left behind crowded later tests' items out. Each subscriber a test makes is unsubscribed after it. Every "gets nothing" is proved against a later mail or bell the same person (or a sibling) must get.

Quarantined (product bugs)

  • P-15 (and X-04 in test(e2e): status page journeys (API, webhooks and settings) #1201): createStatusComponent (status.components.ts:176) writes no history row for a non-operational initial status; uptime reads 100% operational.
  • S-09: subscribeStatusFn (functions/status-subscriptions.ts:25) stores a components subscription with an empty or bogus list.
  • S-23: same cause as A-30.
  • S-30: incident impact maintenance accepted (routes/api/v1/status/-validation.ts:33), email template has no label for it (status-incident-published.tsx:29).

Notes

  • The incident page shows its timeline newest first (status-incident-timeline.tsx:53 reverses the server's list); the inventory said ascending. The test asserts what the page deliberately does.
  • Feed "Affected:" lists services in no fixed order (links read without ORDER BY); the email's order was stable. The test compares as a set.
  • S-05: the no-session refusal "Authentication required" is not masked in the production build, so the portal button's message match works.
  • S-07: the re-subscribe upsert keeps the original source (the subscribe() docstring says the new one applies). Not asserted; listed for the owner.
  • Skipped: P-16 (in-dialog sign-in as a segment member), P-26 (owner question: should a public incident keep naming a deleted service), S-18 (personal preferences, not reached).

Local runs

Fresh database, --workers=2 --retries=0, whole tests/status/ folder three times: all green (80 then 93 passed per run as specs were added). CI on this PR: product-smoke, product-core and product-isolated green, zero flaky.

…help center and people

A second Playwright config (playwright.product.config.ts) on the support
suite's harness: same production build, environment, stand-ins and people,
with tests under e2e/tests/<module>/. The setup project turns on Feedback,
Changelog, Help center and Status (and publishes the status page, which the
raw flag write alone does not). Three `@smoke` wiring tests prove every
admin product page and public page opens.

CI gains product-smoke (every PR), product-changes, product-core (four
shards, product paths or the run-product-e2e label, main, nightly),
product-core-report and product-isolated, mirroring the support jobs.
… tests run

The seed's published entries have notified_at NULL, so the changelog
reconciler (armed 25 s after boot) would email them to every subscriber
while tests read Mailpit.
@mortondev mortondev added the run-product-e2e Run the product e2e core suite on this PR label Nov 20, 2026
@mortondev
mortondev added this pull request to stack #1204 November 20, 2026 11:06
@mortondev
mortondev removed this pull request from stack #1204 November 20, 2026 11:08
@mortondev
mortondev force-pushed the test/product-e2e-status branch 3 times, most recently from 3a3f1c4 to 0dce20e Compare November 20, 2026 12:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

run-product-e2e Run the product e2e core suite on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant