2 commits

Author	SHA1	Message	Date
CRT	9ba8471002	ci speed: desktop boot check runs its cases in parallel (one browser, killed at the end; a page per case; condition waits instead of fixed sleeps: element, text or a quiet window of host calls and DOM); shots capture / render close the browser with a 3 s cap, then kill it; console engine waits injectable for tests (WAITS / engineWaits: poll rounds, a missing step ends once its loaded page stays quiet, team switch settle, field-miss grace), fillPage looks up each data type's dialog once per round and skips dialog sections when no dialog is open; browser tests run 4 at a time per file (testScope().concurrent with a scope per test, --max-concurrency in ci), 20 ms rounds; capture-web counts boots per test and runs its browser tests concurrently; console-session / -persist Chrome tests concurrent; recorded test timings smoothed (mergeTimings) so one loaded run does not skew the shard split	2026-10-13 02:22:25 +08:00
CRT	de243cdbd9	tests: profile persistence runs in a real Chrome, in its own shard ... The two "session cookie survives closing and relaunching storebound's own profile" tests failed with Playwright's headless shell, which ignores --restore-last-session. They now live in tests/console-persist.test.ts and launch the same browser kind console fill uses for its profile (the resolver's "visible" kind: Google Chrome, else the full Chromium; headless here, so no window). They skip with the reason only when neither is installed. All other browser tests keep the fast headless shell. The file is HEAVY in tools/ci-plan.ts, so it never shares a shard with another browser suite.	2026-10-12 06:27:42 +08:00