feat(nix): KDE as a Platform, and the tiling scenario in core-e2e

KdePlatform is a Kde session seen through the neutral vocabulary: kdotool
for the OS's frames, foot for clients, the cell of its font as the
tolerance. The core-e2e suite runs scenarios.tiling through it as a new
section, so that the scenario that will run on Windows is checked on the
one platform that works; the suite's own sections are unchanged. It passes
on KVM (74 checks) on the WSL2 machine.
This commit is contained in:
LGUG2Z committed 2026-10-30 12:02:55 -07:00
1 parent 2c5e8f57dc
commit bb8299410f
4 files changed
+80 -3

No files matched your search

+8
View File
@@ -149,6 +149,14 @@ the run.
goes in `Snapshot.extra`. Its unit tests use fixtures written from the two
ports' serializers; recorded states replace them once a run on each port
exists.
- `Platform` (`core/platform.py`) is what a scenario needs of a platform: start the
daemon, run `komorebic`, read the `Snapshot`, open a window, ask the operating
system for its frame (`os_window`, the oracle: the daemon's state is the thing
under test), and take a screenshot. `core/scenarios` has the scenarios written
against it; `tiling` is the first. A method is added with the first scenario
that needs it. `KdePlatform` (`kde_platform.py`) is a `Kde` session as a
`Platform`, and the `core-e2e` suite runs `tiling` through it after its own
sections.
- `Checks` counts checks and fails once, at the end, so that one failure does
not hide the ones after it. `finish()` prints `passed: N failed: M`, and its
error names the checks that failed, which `nix build` shows in the last lines