Run this on a machine that is not your dev PC: a fresh Windows install in a virtual machine or a spare laptop. Each item has a reason and a way to check it.
Install and uninstall
- Clean install works without developer tools. Why: your PC has runtimes and certificates the user lacks. Check: install on a fresh VM; launch without installing anything else.
- Standard user can install and run. Why: many users have no admin rights. Check: install and use with a non-admin account; note every elevation prompt.
- Installer warnings are expected. Why: an unsigned or unfamiliar installer may trigger a SmartScreen-style warning that scares users. Check: download the installer through a browser, as a user would, and record what appears.
- Uninstall removes the app cleanly. Why: leftovers annoy users and break reinstalls. Check: uninstall, then look at the install folder, Start menu and Apps list. Decide deliberately what user data stays.
Update
- Update over an older version keeps settings and data. Check: install the previous release, create data, update, compare.
- Update while the app is running. Check: start the update with the app open; it should not corrupt files.
Environment
- High DPI and scaling. Why: blurry text or cut-off dialogs at 125-200 percent scaling. Check: change the scaling in Windows settings and reopen the app.
- Two monitors with different scaling; unplugging one. Check: move the window across, close, unplug, reopen. It must appear on a visible screen.
- Permissions and folders. Why: writing next to the .exe fails in protected folders. Check: confirm settings and logs go to a user-writable location.
- Paths with spaces, accents and non-Latin characters. Check: open a file from such a path and a user name with such characters.
- Offline and flaky network. Check: disable the network at start, mid-task and on save. The app should show a clear message, not hang.
- Sleep, hibernate, resume. Check: sleep during a long task, wake it.
Crashes
- Crash leaves useful information. Check: force a failure in a test build and confirm a log or report exists and contains no secrets. See how to read and prioritize crash reports.
- Testers can report problems consistently. Hand them a bug report template with OS version and build number.
Record results
Mark each item pass, fail or not tested. A short honest list beats a long unchecked one.
AppReviewX accepts apps by store link from Google Play, the Apple App Store, the Mac App Store and the Microsoft Store. Windows and Mac apps must already be published in their store, and AppReviewX does not distribute builds or installers. Feedback is private and structured, one accepted feedback = one credit, and store ratings are voluntary, unpaid and never required. Back to the Windows and Mac apps hub. See also the Mac app testing checklist and the Microsoft Store submission checklist. If you also ship on mobile, start free.