DEV Community

Charles Hartmann
Charles Hartmann

Posted on

A three-step smoke test for a Linux alpha in a VM

When a new Linux desktop is still in alpha, “the app launched” tells you less than a small, repeatable task. A VM lets you test the parts you care about without replacing a working OS. The goal isn't a benchmark or a verdict on daily-driver readiness. It's a short record that someone else can reproduce.

Start with a clean boundary

Use the project’s documented VM route and create disposable test data. Note the image and app version before starting. Save a checkpoint if your VM tool supports it. A screenshot helps explain what the interface showed; it doesn't prove a feature worked. Record what was actually opened, played, saved, or reopened as well.

Test one real workflow

For a player, start with a feed you already know. If search misses, paste its RSS URL instead of declaring the feed broken. Play an episode, pause it, close the app, then reopen it and compare the saved position. Directory discovery and feed playback are separate checks. Earshot's RSS walkthrough explains what to try and links to the public build.

For an editor, create a short document, save it as an OpenDocument file, then reopen the saved file instead of trusting the window still in memory. Repeat with a simple sum and a slide if those formats matter to you. Export a PDF as a separate check and open it in a viewer. The Hartmann Office guide covers the app and the GitHub download; a local test does not prove round-trip compatibility with every other office app.

Write down what the VM didn't prove

A passing test applies to that build, that guest, and that workflow. Don't infer native hardware support, a store listing, or production readiness from it. If you’re trying the Luma alpha, the Homelab VM guide points to the official Try Luma route and helps decide what to test first.

AI-assisted write-up based on the linked guides.

Top comments (0)