Commit Graph
125 Commits
Author SHA1 Message Date
LGUG2Z 37bb9e3fe4 feat(repo): scenario-status makes the table from the runs 2026-10-30 12:03:01 -07:00
LGUG2Z 781b082778 feat(nix): a test that no extra repeats a shared check 2026-10-30 12:03:01 -07:00
LGUG2Z 70d8041a62 feat(nix): run_suite times each step and can run only some 2026-10-30 12:03:01 -07:00
LGUG2Z a33504f377 feat(nix): the KDE-only suites as extras and run_suite steps 2026-10-30 12:03:01 -07:00
LGUG2Z 3fba34cbec feat(nix): core-e2e leaves KWin restarts to the kwin-restart suite 2026-10-30 12:03:01 -07:00
LGUG2Z cc32260230 feat(nix): kwin-restart as a KDE extra 2026-10-30 12:03:01 -07:00
LGUG2Z 00adb90244 feat(nix): stacks as a KDE extra 2026-10-30 12:03:01 -07:00
LGUG2Z 52d44c2829 feat(nix): scrolling as a KDE extra 2026-10-30 12:03:01 -07:00
LGUG2Z b72edf4bcf feat(nix): workspace-switch as a KDE extra 2026-10-30 12:03:01 -07:00
LGUG2Z 92aaaeb65f feat(nix): placement as shared steps and KDE extras 2026-10-30 12:03:01 -07:00
LGUG2Z caa5b011a8 feat(nix): workspace-rules as KDE extras and shared steps 2026-10-30 12:03:01 -07:00
LGUG2Z d5eff2c445 feat(nix): the KWin helpers several KDE extras use 2026-10-30 12:03:01 -07:00
LGUG2Z 5e0721bec4 feat(nix): core-e2e as shared steps and KDE extras 2026-10-30 12:03:01 -07:00
LGUG2Z 2c58920db0 feat(nix): a suite names its steps and returns what they returned 2026-10-30 12:03:01 -07:00
LGUG2Z 3b40bedac3 feat(nix): drag-resize as KDE extras and shared steps 2026-10-30 12:03:01 -07:00
LGUG2Z bc5f4babc4 feat(nix): commands as shared steps and KDE extras 2026-10-30 12:03:01 -07:00
LGUG2Z b09011dce7 fix(nix): a suite step may call something that returns a value 2026-10-30 12:03:01 -07:00
LGUG2Z f5db6975b4 feat(nix): hotplug as shared steps and KDE extras 2026-10-30 12:03:01 -07:00
LGUG2Z 47123ad748 feat(nix): scoped checks and a suite helper in the core 2026-10-30 12:03:01 -07:00
LGUG2Z 15d6a5aef3 feat(nix): exe_id spells the id of a rule for a program 2026-10-30 12:03:00 -07:00
LGUG2Z dbe84192d4 feat(nix): an optional komorebi-recorder in the core suites 2026-10-30 12:03:00 -07:00
LGUG2Z 2e078f9ef6 feat(nix): config reload, exe rules and lock scenarios in the core 2026-10-30 12:03:00 -07:00
LGUG2Z 733a5a4934 feat(nix): the rules_class scenario, and an app id for Platform.spawn
A workspace rule by class sends a window to its workspace, an ignore
rule by class leaves one alone, and a window of another class stays
where it opened. Platform.spawn takes an app_id, which is foot's -a on
KDE and the window class on Windows. core-e2e passes 271 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z e375d0a151 feat(nix): the scrolling scenario
In the scrolling layout each window in turn, given the focus, has it
and is inside the work area; changed back to bsp, every window is where
the layout says. core-e2e passes 265 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 672a6951bd feat(nix): the lifecycle_hidden scenario
A window put away on another workspace is managed again after the
daemon stops and starts, and the ones in view are inside the work area
and clear of each other. KdePlatform.start_komorebi waits for the unit
to be gone first: systemctl start does nothing for a unit that is still
stopping, and a daemon with a window put away took longer to exit.
core-e2e passes 261 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 74ddcce4d9 feat(nix): the tiling_off scenario
toggle-tiling leaves the windows where they are, a layout change moves
none of them, and toggled again every window is tiled where the layout
says. core-e2e passes 254 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 6e111411e7 feat(nix): the pausing scenario
A window that opens while the daemon is paused is not managed; after
toggle-pause again the next one is, and every window is where the
layout says. core-e2e passes 248 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z d58353d22e feat(nix): the flipping scenario
flip-layout horizontal puts every window where the mirror of its place
is, with every window where the layout says, and flipping again gives
the places back. core-e2e passes 244 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 63d5833a84 feat(nix): the promoting scenario
promote puts the focused window on the first tile and keeps its focus,
with every window where the layout says. core-e2e passes 241 checks on
KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 9b1162dcbe feat(nix): the resize_commands scenario
resize-axis horizontal increase widens the focused window and decrease
gives the width back, with every window inside the work area and none
over another, and no pointer. core-e2e passes 237 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z a8b30e1c1b feat(nix): the workspace_moves scenario
move-to-workspace takes a window to another workspace and the focus
with it, focus-last-workspace goes back and forth, and moving the window
home tiles everything again. core-e2e passes 233 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z f1ea111fd0 feat(nix): the maximizing scenario
toggle-maximize gives a window the work area, with the others where they
were and the daemon naming it as the maximized window; toggled again,
every window is tiled where the layout says. core-e2e passes 225 checks
on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z d4d356c70e feat(nix): the padding scenario, and padding in Snapshot
Raising the workspace padding moves the windows in from the edge by as
much, and raising the container padding leaves them less room; putting
the padding back gives back the windows' frames. The measure is of the
padding the scenario sets itself: on KDE the state says 0 and 0 while
the windows sit 10 px in, and the first run's padding is not what the
state says. Workspace has workspace_padding and container_padding now.
core-e2e passes 220 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 4471cc01a8 feat(nix): the minimizing scenario, and Platform.minimize
A minimized window leaves its room to the others, and a restored one
takes it back. Platform.minimize is new: the title bar button on KDE;
activate restores. core-e2e passes 213 checks on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 4835907b2e feat(nix): the layouts and floating scenarios
layouts changes the layout of the first workspace to each of eight, with
three windows and with five, and checks every window is where the
daemon's layout says, inside the work area and clear of the others.
floating floats a window, checks the others take its room, and that
floating it again tiles it back. Both run in core-e2e: 209 checks pass
on KDE.
2026-10-30 12:03:00 -07:00
LGUG2Z 4158f63557 fix(nix): focus_follows_mouse rests the pointer over the focused window
On again, the scenario moved the pointer over the first window, which
already had the focus, so it waited for nothing and moved on to the
second at once. A platform that follows the pointer by a hover delay
never saw it enter the first. The pointer now rests there for a
moment, as it would for a person.
2026-10-30 12:03:00 -07:00
LGUG2Z ddab35b5b9 feat(nix): the focus_follows_mouse scenario, with a pointer
With focus follows mouse on, the pointer over a window gives it the
focus, and the daemon follows; turned off, it moves nothing; turned on
again, it follows again. The scenario needs a pointer and is skipped
without one. The toggle passes --implementation windows, which kfw's
subcommand requires. drag-resize runs it after resize.
2026-10-30 12:03:00 -07:00
LGUG2Z efeaafad28 feat(nix): the startup_rules scenario, workspace rules of a file
A window that was open before the daemon, and one that opens after, go
to the workspace a rule in the config names, by the start of their
title; a window no rule names stays on the first. The rule is in the
file, so what is checked is how the file is read at start. core-e2e
runs it as section 12a2.
2026-10-30 12:03:00 -07:00
LGUG2Z b1e041f53d feat(nix): placement takes known failures by case
A port that cannot start with a case's rules, or orders its windows
otherwise, is recorded as a known failure for that case, and the other
cases run on. kfw does not accept the place as a JSON number, so
BEHAVIOUR.md lists the case as a known failure there.
2026-10-30 12:03:00 -07:00
LGUG2Z b5e9cf5301 feat(nix): the placement scenario, and Platform.restart_with
Where a window that opens goes, from the placement rules of the
config: none, Primary, a number as a number and as text, and rules by
title for the first and the last place. restart_with starts the daemon
afresh with a komorebi.json the scenario gives. KdePlatform.spawn
quotes the title, which a title with spaces needs. core-e2e runs it as
section 12a.
2026-10-30 12:03:00 -07:00
LGUG2Z 8fc7c961d0 feat(nix): known failures, with unknown_monitor the first
Checks.known_failure records a check that fails for a reason that is
to be followed up on: the suite does not fail, the totals say how many
known failures there are, and one that holds fails the suite so the
marker goes. unknown_monitor takes the reason, and core-e2e runs it
last, because the window it loses stays lost. BEHAVIOUR.md says so.
2026-10-30 12:03:00 -07:00
LGUG2Z 54d866f83a feat(nix): rules, a window the cleared rules matched stays put
After clear-all-workspace-rules a window that the old rules matched
opens on the workspace in view and stays there. The first window of
that title is closed before the next opens, because the title is how
a window is named on both ports.
2026-10-30 12:03:00 -07:00
LGUG2Z 6dbc4d8f63 feat(nix): the lifecycle scenario, a daemon that starts again
The daemon stops, every window stays, and a daemon that starts again
manages the windows that were in view, tiled inside the work area and
clear of each other, and also a window opened afterwards. The fake
platform learns to stop and to start with no memory of workspaces.
core-e2e runs it before its final stop.
2026-10-30 12:03:00 -07:00
LGUG2Z 93c786242b feat(nix): give the sweep's toggle-focus-follows-mouse its option
kfw declares the subcommand with arg_required_else_help, so without an
argument it prints help and exits 2, although the option has a default.
kfde accepts the same option, so the sweep passes it explicitly:
--implementation windows, the default on both ports.
2026-10-30 12:03:00 -07:00
LGUG2Z 32b08d1b77 feat(nix): unknown_monitor, a window sent to no monitor must stay managed
The scenario sends the focused window to monitor 7 with send-to-monitor and
move-to-monitor, which no display has, and checks that the daemon still
manages every window. A port may refuse or ignore the command, but a window
that was managed has to stay so: one that is not is left on the screen with
nothing tiling it.

It found a bug in both ports. kfw managed one window fewer than the OS had
afterwards (seen by hand on a Windows guest), and kfde failed it in
core-e2e on a real KWin: move_container_to_monitor takes the focused
container out of its workspace before it looks the monitor up, so the
error for a monitor that is not there comes after the container is gone.
It is not fixed, so the scenario is not in core-e2e, which would fail;
BEHAVIOUR.md has the finding. Its unit tests run it against a fake that
loses the window and one that ignores the command.
2026-10-30 12:03:00 -07:00
LGUG2Z b22ae83e6a feat(nix): the command sweep plugs in a second display when it needs one
The sweep has commands that name the second monitor, send-to-monitor 1 and
the ones after it, so it needs two displays. The KDE suite runs with two
outputs and never noticed. On Windows, with one display, the first run of
the sweep reported that after send-to-monitor 1 kfw managed one window
fewer than the OS had, and every command after it was reported unhealthy;
whether that is kfw losing a window sent to a monitor that does not exist
has not been confirmed by hand. The sweep now plugs in a display first if
the platform has one, and a fake with one display shows it does.
2026-10-30 12:03:00 -07:00
LGUG2Z 1c0bc9eae9 feat(nix): the commands, rules and hotplug scenarios, for every platform
commands is every layout, a sweep of 216 commands and the commands that
only print, each of which must be understood and leave the daemon healthy
(it answers state and manages the windows the OS has). A command the port
lacks, which komorebic says with 'unrecognized subcommand', is skipped with
its name, which is what a behaviour matrix is made of: Checks.skip records
it and finish prints how many. The commands suite runs it instead of its
own copy of the list: 270 checks pass, none skipped.

rules gives the daemon an initial rule, a rule that is not, and an ignore
rule, by title, and checks where each window goes. It found that
enforce-workspace-rules applies initial rules again on purpose, so the
scenario asks whether the daemon sends the window back on its own.

hotplug unplugs a display, plugs one in and sends a window to it, and
starts by plugging one in if the platform has only one. Platform gets
displays, add_display and remove_display, and KdePlatform does them with
kscreen-doctor. The hotplug suite runs it: 34 checks pass.

core-e2e runs rules after the others, then leaves a window for the stop to
leave behind: 130 checks pass on KVM. One run failed the check that the
daemon had exited after komorebic stop and the next did not; the cause is
not known, and the suite now prints the unit's status when it happens.
Snapshot.workspace_of tells which workspace has a window.
2026-10-30 12:03:00 -07:00
LGUG2Z ed792445d0 feat(nix): the monocle and closing scenarios, and Platform.close
monocle toggles monocle on the focused window and checks that it fills the
work area up to the layout's padding, that the state has it as the monocle
container, that every other window is put away, that it keeps the focus,
and that toggling back puts every window in view on the tile it had.
closing closes a window and checks that the OS has no frame for it, that
the daemon manages one window fewer, and that the windows left in view
take more room between them, inside the work area and clear of each other.

Platform.close closes a window as its button would; KdePlatform does it
with kdotool. The fake daemon models monocle and closing, and its
os_window now knows the workspace a window is on, which the workspaces
scenario had passed without. core-e2e runs both: 120 checks pass on KVM.
2026-10-30 12:03:00 -07:00
LGUG2Z 37b75f8205 feat(nix): the resize scenario and a pointer on the Platform
Platform.has says whether a platform can do what a scenario needs, and
Platform.pointer is a Pointer (move, down, up, drag) where it has one;
KdePlatform takes the pointer of a session node. scenarios.resize drags the
edge two tiles share by 60 pixels and checks that the tiles that end at the
edge are that much wider, the ones that start after it start that much
later and end where they did, nothing moves up or down, and tiles that do
not touch the edge are where they were. A platform with no pointer skips
it, and says so.

The fake daemon has a pointer that moves an edge. The scenario runs on KDE
at the end of drag-resize: 19 checks pass on KVM. Its first run failed one
check that was the scenario's: both tiles of a BSP column share the dragged
edge, and the check took the second for one that had not moved.
2026-10-30 12:03:00 -07:00
LGUG2Z e385bace05 test(nix): Snapshot against states recorded from both ports
core-e2e writes the komorebic state of kfde, with three tiled windows and
with one stacked onto another, into its output, and the files are kept in
tests/fixtures beside kfw's three, recorded from a Windows guest (tiled,
stacked, one window floated). test_recorded.py reads all five with the
same checks: three containers of one window, a layout rectangle for each
inside the work area, each window where its container's rectangle is up to
a terminal cell (foot rounds to cells, kfw's test window does not), and a
stack that is a container of two whose focused window is the one the ring
names. Nothing in the parser had to change; the checks passed on the first
real kfw state.

The scenes written from the serializers stay for the shapes no run has
recorded. The sync script copies the fixtures too. The workspaces scenario
prints which windows are in view after the switch: one run of core-e2e
failed that check and passed on the next, and the log did not say which
window had been in view.
2026-10-30 12:03:00 -07:00