The capture gains the phase 5 screens, light and dark: - videos: the Videos section in cards on a sample of this PC's renders (a 4K video also on the server and copied to the videos folder, a still, a 1080p share, a PNG image sequence, a render whose file is gone), two renders only the sample server holds and a workspace GIF not sent yet; - videos-list: the list with the still selected and shown in the player; - edit-export-playback: Output and File folded to their summaries, Encoding and Playback open on a boomerang played twice with fades; - edit-render-menu: the header's Render menu dropped down. The menu is a popup the window's picture does not hold, so the capture builds it from the same entries (SplitButton.CreateItem, now public) and draws it over the window where it opens, without showing a popup on screen. The renders sit on sequences the server does not hold, so the sync table keeps its own sample. The videos folder is set to D:\Videos\Chronos before Settings reads it, so Settings > Archive no longer shows this PC's own Videos folder. edit-export-copies and edit-remote-export fold the groups that would push their subject (Sync and Restore, the server's encoder) below the fold of the grouped Export panel. Every other baseline changes for the Videos rail entry, the fixed-width Render header and the grouped Export panel. Refs #21 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.8 KiB
Screenshot baselines
The approved look of every screen, one PNG per --capture screenshot (<screen>-<theme>.png, as Chronos.exe,
Chronos.Uploader.exe and Chronos.Setup.exe --capture <dir> write them). CI compares each new screenshot with the
file of the same name here (BRIEF §20.2, visual regression with a pixel-diff tolerance):
dotnet run --project src/Chronos.Tools -- screenshots diff out/screenshots --out out/screenshot-diff
- A pixel differs when one of its channels moves by more than
--tolerance(default 8 of 255); a screen fails when more than--max-diffof its pixels differ (default 0.0005, that is 0.05 %), when its size changed, or when a baseline here has no screenshot any more. - A screenshot without a baseline fails as soon as this folder holds any PNG: a pull request that adds a screen adds its baselines too.
- While this folder holds no PNG nothing is compared: the step passes, with a warning in the log saying that no visual change can fail it.
out/screenshot-diffgets<screen>-diff.pngfor every screen with differing pixels (the baseline faded to grey, the differences magenta) andsummary.md; they stay in the work folder of the Windows runner (Gitea Actions keeps no artifacts here), and the job log lists every screen that failed.
The pictures are reproducible
The capture runs on sample data whose clock stands at SampleData.Now (2026-10-02 10:18 UTC), in English with English
formats and with animations off, so the same code draws the same pixels on any day. What the screens measure on
the machine is shown as fixed sample values while the clock is frozen (AppClock): free space (1.2 TB), the
server's response time (12 ms) and the time and duration of the last sync comparison. The capture's data folder is a
new one in the machine's temporary folder, but the screens show it as a sample user's (C:\Users\Studio\AppData\Local\Chronos,
its sample archive as D:\ChronosArchive: AppEnvironment.Shown; the videos folder is set to D:\Videos\Chronos), so neither the temporary folder nor the user name
reaches a picture; a path typed over a shown one goes back to the temporary folder (AppEnvironment.Actual), so the
capture writes nowhere else. Two captures made with different TEMP folders are identical. Two things still come from the
machine: the time zone (times are shown in local time; the baselines are made in the development PC's, Europe/Rome,
which the Windows runner must share) and the fonts and scaling of Windows itself.
Adding or updating baselines
Capture them on the development PC, the one where the Windows runner is registered (fonts, scaling and the time zone differ per machine), from a Release build of the branch that changes the screens:
dotnet build Chronos.slnx -c Release
src/Chronos.App/bin/Release/net10.0-windows/Chronos.exe --capture out/screenshots
src/Chronos.Uploader/bin/Release/net10.0-windows/Chronos.Uploader.exe --capture out/screenshots
src/Chronos.Setup/bin/Release/net10.0-windows/Chronos.Setup.exe --capture out/screenshots
dotnet run --project src/Chronos.Tools -- screenshots diff out/screenshots
dotnet run --project src/Chronos.Tools -- screenshots accept out/screenshots
screenshots accept <dir> copies every PNG of <dir> here. Commit only the screens whose change is intended, and delete
the baseline of a screen that no longer exists. If the Windows runner is ever registered on another PC, accept a new
set captured there in one commit.
The first baselines
The first set (156 screens) was captured on the development PC on 2026-11-04 (owner review 3, R2), at SampleData.Now,
and is committed with the ports fix of v0.1.0-rc.9. Until a Windows runner is registered, CI skips the windows job
and nothing compares them: run screenshots diff locally before a pull request that touches a screen.