You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Two browser tests failed once each in the first CI runs #47
The browser suite ran five times on GitHub on 2026-11-18: on main twice and on three dependency pull requests. Three runs passed. Two failed, each on one test, and neither test has failed on a developer's machine.
Pull request chore(deps): Bump @types/node from 24.19.2 to 26.6.6 #3 (a bump of Node's type definitions, which the app does not ship): test/e2e/writing.spec.ts › "the formatting bar sizes, colours, aligns and indents, in plain markup, and takes it off again". The test clicked a tool of the bar and waited a minute for the item of its menu (Align centre), which never appeared: the menu did not open, or opened and closed again.
Pull request chore(deps): Bump better-auth from 1.7.23 to 1.7.25 #2 (a bump of the sign-in library): test/e2e/remembered.spec.ts › "a choice made in one browser is there in a second browser of the same person, and a choice of the device is not". This one may be the bump and not chance: it must be told apart before that pull request merges.
Done when
Each failure has a cause that is written down: the test, the app, or the dependency.
If a person can hit the same moment, the app is fixed; if only the test can, the test waits for the right thing instead of trying again.
The failed runs keep their output for a while: job "pnpm e2e (browser)" of each pull request. The status, section 3, records a similar miss for a click into the mail frame.
changed the title [-]The formatting-bar browser test fails now and then in CI[/-][+]Two browser tests failed once each in the first CI runs[/+]on Nov 18, 2026
Both causes are found and corrected in #48, which is merged.
The formatting bar: the app, not the test. A choice from a menu asked for the cursor and so did the closing menu; the later of the two closed the next menu on a slow machine. Made to happen at will with the browser's processor slowed eight times: 5 of 8 runs failed before, 0 of 8 after.
Activity
[-]The formatting-bar browser test fails now and then in CI[/-][+]Two browser tests failed once each in the first CI runs[/+]Madraka commentedon Nov 18, 2026
Both causes are found and corrected in #48, which is merged.
Left open here: both tests twenty times in a row in CI. Three runs since the correction have passed (#48, #49 before its merge, and
main).