|
| 1 | +--- |
| 2 | +description: How we test the AtlasOS Playbook |
| 3 | +icon: material/test-tube |
| 4 | +--- |
| 5 | + |
| 6 | +# :material-test-tube: What you can test for in Atlas |
| 7 | + |
| 8 | +This page covers what we recommend testing in an in-development build. See [the reporting issues page](reporting-issues.md) if you find any problems. |
| 9 | + |
| 10 | +If you haven't set up a virtual machine, see the [Playbook contributing page](../playbook.md) on how to do so. However, feel free to test it on real hardware, especially if it's a [release candidate](../../faq-and-troubleshooting/common-questions/testing-nightly-builds.md)! |
| 11 | + |
| 12 | +!!! note "Ensure what you test works on stock Windows first" |
| 13 | + To reduce the amount of false reports, please verify that any issues encountered on Atlas do not happen in the same environment and configuration on unmodified Windows. |
| 14 | + |
| 15 | +## :octicons-person-16: Your personally used Windows features |
| 16 | + |
| 17 | +Testing the features you use is recommended, especially if it's not a typical configuration or usage. Some examples of this include: |
| 18 | + |
| 19 | +- Non-English languages |
| 20 | + - Multiple languages & keyboard layouts |
| 21 | +- Touchscreen support |
| 22 | +- ARM-based Windows (11 only) |
| 23 | +- Accessibility features |
| 24 | +- Hyper-V and WSL |
| 25 | + |
| 26 | +## :material-gamepad: Your personally used apps/games |
| 27 | + |
| 28 | +We recommend testing all your personally used software and games in a realistic environment to ensure that Atlas has brought no incompatibilities. |
| 29 | + |
| 30 | +Ensure you install drivers properly beforehand and can't reproduce any encountered issues on stock Windows in the same environment. |
| 31 | + |
| 32 | +## :material-update: Windows Update |
| 33 | + |
| 34 | +As Atlas supports Windows Update, consider testing the following that all make use of Windows Update's components: |
| 35 | + |
| 36 | +- From the [base ISO (no updates)](../playbook.md#which-snapshots-to-make), installing all Windows Updates post-Atlas |
| 37 | +- Language pack installation |
| 38 | +- Various optional Windows features |
| 39 | +- Store and XBOX game installation/updates |
| 40 | + |
| 41 | +## :material-router-network: Remoting and file sharing |
| 42 | + |
| 43 | +Consider testing local network features such as: |
| 44 | + |
| 45 | +- Windows file sharing |
| 46 | + - Enable with the [Atlas script](../../getting-started/post-installation/atlas-folder/general-configuration.md#file-sharing) first |
| 47 | + - Ensure that it works on stock Windows |
| 48 | +- Screencasting |
| 49 | +- Remote Desktop |
| 50 | + |
| 51 | +## :custom-atlas: Atlas folder |
| 52 | + |
| 53 | +We recommend doing lots of testing in the Atlas folder. For this, we recommend the following: |
| 54 | + |
| 55 | +- Testing each script and checking if it does its functionality |
| 56 | + - Especially the significant scripts like disabling Defender |
| 57 | + - If prompted for anything, test various inputs |
| 58 | + - Make sure to restart if prompted |
| 59 | +- Suggesting where we can: |
| 60 | + - Improve the structure |
| 61 | + - Improve user experience |
| 62 | + - Simplify the folder |
0 commit comments