e2e: characterization suite for the 1.7.4-1.7.7 release notes (packaged app, no provider key) - #146
Open
kai-openswarm wants to merge 1 commit into
Open
Conversation
…ed app, no provider key) A regression net for the user-facing claims in backend/apps/help/changelog.py: each test names the changelog line it pins, so a later refactor of the files that carry that behaviour has to keep the claim true, not just compile. - canvas-fullscreen: composer yields to open windows; a wheel inside a window never moves the canvas; flat default wash; nothing drags while fullscreen and Escape exits; exactly one fullscreen owner, ever; dock tiles are never letters - chat-toolui: AskUI approval cards answer once with a receipt, an unparked answer is reported honestly, older asks go quiet behind the live one, widget links open browser cards leaving fullscreen first, the provider-retry pill survives status frames and never shows a scary card - resilience: a failed or unscoped sessions read never wipes the board; the packaged backend is really killed - a quick recovery is silent, a sustained outage shows the reconnecting pill and heals when it can - workflows-and-settings: off means off (Run Now refused + History row; a deleted workflow cannot run), Settings > Memory is the store's own list, the dictation cue defaults to 70% Sessions come from the app's own launch route; streamed messages are dispatched through the store's reducer in the wire shape the backend emits; the backend is called from inside the renderer so no spec handles a token or a port. Sorted after the existing specs so it never changes their starting profile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 18, 2026
Draft
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.
What
A regression net for the user-facing claims in the release notes (
backend/apps/help/changelog.py, 1.7.4–1.7.7):e2e/tests/v1.7-characterization/— 4 specs, 19 tests, plus a sharedsupport.tsand a README section. Each test names the changelog line it pins, so a later refactor of the files that carry that behaviour (the chat surface, the canvas and window state, the shell's dashboard host, the layout slice) has to keep the claim true, not just compile.Same rules as the rest of
e2e/: packaged app, no provider key, macOS + Windows. Sessions come from the app's own launch route; the messages an agent would stream (AskUI approval cards, ShowUI links) are dispatched through the store's own reducer in the wire shape the backend emits; the backend is called from inside the renderer (already bearer-patched), so no spec handles a token or a port. Namedv1.7-…so it sorts after the existing specs and never changes their starting profile.Verified
smoke.spec.ts) in one run against a packaged 1.7.7 build on macOS, pristine profile; each file also run repeatedly standalone.windows-latestthe packaged app currently cold-boots past the harness's own budgets (smoke.spec.tsfails there inbeforeAll), so the Windows leg was not the proof here; the specs use no OS-specific paths beyond a PowerShell branch for finding the backend PID.e2e/testswas already over the linter's 7-item cap ondev; this adds one folder.The suite surfaced a few things on the way, sent separately: #142 (a fresh read after a save could be answered from the 1 s GET cache — the memory test carries a 1.5 s wait until that lands), the launch-snapshot fix, the mac dev-build fix, and the installer verifier port.