<!-- Please read https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before submitting your pull request --> ### Description <!-- Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change. --> Fixes # #### Type of change - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ### Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings ### AI disclosure: - [ ] Partially AI assisted (clarify which code was AI assisted and briefly explain what it does). - [ ] Fully AI generated (explain what all the generated code does in moderate detail). <!-- Write any explanation required here, but do not generate the explanation using AI!! You must prove you understand what the code in this PR does. -->
End-to-end tests
Playwright drives a production build served by Vite preview on :4175 against a throwaway
Continuwuity homeserver started per run. The suite
covers functional flows (login, sync, navigation, timeline) and captures
screenshots for layout regression.
Requirements
- Docker running (a Continuwuity container is started via testcontainers).
Running
pnpm test:e2e # functional tests on the host (screenshots skipped)
pnpm test:e2e:docker # full suite, browser in the pinned container
pnpm test:e2e:docker:update # regenerate screenshot baselines
pnpm test:e2e:ui # interactive UI mode
pnpm test:e2e:report # open the last HTML report
Screenshot baselines are rendered in mcr.microsoft.com/playwright:<version>-noble,
because font rendering differs between hosts. Regenerate them with
test:e2e:docker:update, never on the host. Visual tests skip unless
PW_TEST_CONNECT_WS_ENDPOINT is set.
How it works
global.setup.ts:
- Starts a Continuwuity container with open registration.
- Registers a bootstrap user and seeds deterministic rooms/messages over the client-server API.
- Gives each Playwright worker its own identically seeded user and
storageState, isolating sync and crypto state while specs run in parallel. - Saves the container id for
global.teardown.ts. - Injects the session into the app's
localStorage(matrixSessions+matrixActiveSession), so specs start already logged in without driving the login UI.
global.teardown.ts removes the container after the dependent projects finish.
Adding a test
Specs live in tests/e2e/*.spec.ts and run against both a desktop and a mobile
viewport. The touch project runs touch interactions and permalink navigation;
the narrow mobile project covers the rest of the responsive flows. Assert
behaviour with locators; add toHaveScreenshot where a layout baseline is
useful. Screenshot baselines live in tests/e2e/__screenshots__.
Notes when adding screenshots:
- Mask dynamic content (
timeelements, the room-intro creation line). - The message timeline is virtualised, so its item positions shift between runs; snapshot the surrounding layout rather than the timeline itself.
foldsrendersTextasp, sogetByRole('heading')will not match titles.