Why our CLI does everything the GUI does

Sat, 22 Aug 2026 06:00:00 -0500

Every team that ships a desktop app eventually learns that the GUI is the worst possible place to test the product, because a Qt window needs a display server, a compositor, a font stack, and a small miracle to run in CI, and the test that clicks a button headlessly is the test that flakes at 2 AM the night before a release. The way out is not a better GUI-testing framework but a rule about where features live: the feature lands in a shared core library, the GUI is one consumer of that library, and the CLI is the other, and once the rule actually holds, the “how do we test the app” problem collapses into “test a library and a command,” both of which a CI runner does in its sleep.

Ci on VisorCraft News

Why our CLI does everything the GUI does