How we test

Guides on CrunchBangLinux are tested, not transcribed. Every guide carries a Tested On block stating the distribution and version, kernel, desktop environment, the software and version in question, the hardware it was run on, who tested it, and the date. If a guide has not been re-tested against current versions, a visible staleness notice says so.

Why versions matter

A shell command that was correct on one release can be wrong — or destructive — on another. AI-generated instructions are especially prone to plausible, wrong commands, which in this subject means data loss for a reader. So our procedures are run on real systems before they are published, and re-run on a schedule.

Re-testing

Guides flag automatically when the tested version falls behind current releases, and are re-tested and re-dated rather than silently left to rot.