Testing guide

Use this checklist to test alpha and release-candidate builds. Report every reproducible problem.

Follow the Playbook testing setup to create a virtual machine. Test release candidates on real hardware as well.

Test on Stock Windows First

Verify that issues on Atlas don’t occur on unmodified Windows in the same environment. This reduces false reports.

Windows features you use

Test the features you use, especially if your setup differs from typical. Examples:

  • Non-English languages
    • Multiple languages & keyboard layouts
  • Touchscreen support
  • ARM-based Windows (11 only)
  • Accessibility features
  • Hyper-V and WSL

New user accounts

Try creating new user accounts and logging into them, and verify that all tweaks apply.

Apps and games you use

Test all software and games you use in a realistic environment. Install drivers properly first. Confirm you can’t reproduce issues on stock Windows in the same environment.

Windows Update

Atlas supports Windows Update. Consider testing these components:

  • From the base ISO (no updates), installing all Windows Updates post-Atlas
  • Language pack installation
  • Various optional Windows features
  • Store and XBOX game installation/updates

Remoting and file sharing

Consider testing local network features such as:

  • Windows file sharing
    • Enable with the Atlas script first
    • Confirm it works on stock Windows
  • Screencasting
  • Remote Desktop

Atlas folder

Test the Atlas folder thoroughly:

  • Run each script and confirm that it performs the named action
    • Especially the significant scripts like disabling Defender
    • If prompted for anything, test various inputs
    • Restart when prompted
  • Look for improvements to:
    • Structure
    • User experience
    • Folder organization