Use this checklist on a machine that has never run nbshell. A virtual machine can validate files, but real Wayland hardware is required for display, input, capture, and animation testing.
- Clone the repository into a new user account.
- Run the minimal
./setup.shprofile and read every proposed package. - Enable the integration with
nbshell switch on, then log out and in. - Confirm that the bar, launcher, dashboard, settings, and power menu open.
- Confirm that optional modules fail quietly when their programs are absent.
- Run
nbshell --version,nbshell status, andniri validate. - With the full capture profile installed, use
grimfor reproducible visual comparison screenshots without changing nbshell's native capture workflow.
- Test 100%, 125%, 150%, and 200% scale where the display supports it.
- Test one display, two displays, disconnect/reconnect, rotation, and suspend.
- Open eight tiled windows in grid-scroll mode, close middle windows, toggle back to normal scrolling, and verify that floating windows are untouched.
- Test keyboard-only navigation, Escape behavior, hover previews, and every bar edge and mode.
- Leave the shell idle for at least two hours and compare memory use.
- Change a theme, module arrangement, and plugin setting.
- Pull the next revision and run
./install.sh; personal state must remain. - Disable one bundled plugin and install one reviewed external plugin.
- Verify the Umbriel login first, then choose Niri in the greeter and confirm
the recovery session, shell startup, and
nbshell switch offremain usable. - Re-enable nbshell and confirm that the previous settings return.
Record GPU and driver, display layout, Niri and Quickshell versions, nbshell revision, failed step, reproduction sequence, and sanitized log excerpt. Never include credentials, notification text, clipboard contents, network addresses, or calendar data.