Testing guide

This guide covers recommended testing for alpha or release candidate builds. Found problems? See the reporting issues page.

If you need to set up a virtual machine, see the Playbook contributing page for instructions. You can also test on real hardware, especially for release candidates.

Your personally used Windows features

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.

Your personally used apps/games

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:

• Testing each script and checking if it does its functionality
  • Especially the significant scripts like disabling Defender
  • If prompted for anything, test various inputs
  • Make sure to restart if prompted
• Suggesting improvements for:
  • Structure
  • User experience
  • Folder organization