feat(nix): the focus and moving scenarios, for every platform

focus moves the focus with focus and cycle-focus and checks that the OS and
the daemon's state agree on the window that has it and that no window moved.
moving swaps the focused window with its neighbor with move and puts every
window back with cycle-move, and checks that the focus stays with it. Both
read the windows through the Platform, so they are what kfw's suite will
run.

Their unit tests run against a fake daemon that follows the commands over
three tiles, and against two that do not (a move that moves nothing, a move
that loses the focus). core-e2e runs them after tiling on KDE: 85 checks
pass on KVM.
This commit is contained in:
LGUG2Z committed 2026-10-30 12:02:55 -07:00
1 parent bb8299410f
commit c861f4f789
8 files changed
+287 -8

No files matched your search

+2 -1
View File
@@ -153,7 +153,8 @@ the run.
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
against it: `tiling`, `focus` and `moving`, which `core-e2e` runs on KDE and which
scenarios of kfw's suite can run unchanged. 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.