Repository navigation
Conversation
…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.
…overview journeys
…ncidents after it
mortondev
force-pushed
the
test/product-e2e-status
branch
3 times, most recently
from
November 20, 2026 12:04
3a3f1c4 to
0dce20e
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)
@smoke@core@nightly@quarantinepublic-page.spec.tsfeed.spec.tssubscribe.spec.tsemails.spec.tsLower 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 (
deleteMadeIncidentsin 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)
createStatusComponent(status.components.ts:176) writes no history row for a non-operational initial status; uptime reads 100% operational.subscribeStatusFn(functions/status-subscriptions.ts:25) stores a components subscription with an empty or bogus list.maintenanceaccepted (routes/api/v1/status/-validation.ts:33), email template has no label for it (status-incident-published.tsx:29).Notes
status-incident-timeline.tsx:53reverses the server's list); the inventory said ascending. The test asserts what the page deliberately does.source(thesubscribe()docstring says the new one applies). Not asserted; listed for the owner.Local runs
Fresh database,
--workers=2 --retries=0, wholetests/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.