PowerToys/doc/releases/0.55.0/tests-checklist-seraphima.md

Install tests

• install a previous version on a clean machine (a clean machine doesn't have the %localappdata%\Microsoft\PowerToys folder)
• open the Settings and for each module change at least one option
• open the FancyZones editor and create two custom layouts:
  • a canvas layout with 2 zones, use unicode chars in the layout's name
  • one from grid template using 4 zones and splitting one zone
  • apply the custom canvas layout to the primary desktop
  • create a virtual desktop and apply the custom grid layout
  • if you have a second monitor apply different templates layouts for the primary desktop and for the second virtual desktop
• install the new version (it will uninstall the old version and install the new version)

• verify the settings are preserved and FancyZones configuration is still the same

General Settings

Admin mode:

• restart PT and verify it runs as user
• restart as admin and set "Always run as admin"
• restart PT and verify it runs as admin

• if it's not on, turn on "Run at startup"

• reboot the machine and verify PT runs as admin (it should not prompt the UAC dialog)

• turn Always run as admin" off

• reboot the machine and verify it now runs as user

Modules on/off:

• turn off all the modules and verify all module are off
• restart PT and verify that all module are still off in the settings page and they are actually inactive
• turn on all the module, all module are now working
• restart PT and verify that all module are still on in the settings page and they are actually working

FancyZones Editor

• Open editor from the settings
• Open editor with a shortcut
• Create a new layout (grid and canvas)
• Duplicate a template and a custom layout
• Delete layout
• Edit templates (number of zones, spacing, distance to highlight adjacent zones). Verify after reopening the editor that saved settings are kept the same.
• Edit canvas layout: zones size and position, create or delete zones.
• Edit grid layout: split, merge, resize zones.
• Check Save and apply and Cancel buttons behavior after editing.
• Assign a layout to each monitor.
• Assign keys to quickly switch layouts (custom layouts only), Win + Ctrl + Alt + number.

FancyZones

• Switch between Allow zones to span across monitors on and off. Verify that layouts are applied correctly in both cases.
• Change zone colors and opacity.
• Exclude some apps, verify that they're not applicable to a zone.
• Launch PT in user mode, try to assign a window with administrator privileges to a zone. Verify the notification is shown.
• Launch PT in administrator mode, assign a window with administrator privileges.
• Create virtual desktop, verify that there are the same layouts as applied to the previous virtual desktop.
• After creating a virtual desktop apply another layout or edit the applied one. Verify that the other virtual desktop layout wasn't changed.
• Delete an applied custom layout in the Editor, verify that there is no layout applied instead of it.

• Switch between layouts with quick keys.
  • Switch with Win + Ctrl + Alt + key
  • Switch with just a key while dragging a window.
• Change screen resolution or scaling.
  • Assign grid layout, verify that the assigned layout fits the screen. NOTE: canvas layout could not fit the screen if it was created on a monitor with a different resolution.

• Disable FZ
• Re-enable FZ, verify that everything is in the same state as it was before disabling.

• Test layout resetting. Before testing
  • Remove all virtual desktops
  • Remove CurrentVirtualDesktop from \HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\VirtualDesktops
  • Remove VirtualDesktopIDs from \HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\VirtualDesktops

• Test screen locking

  • Set custom layouts on each monitor
  • Lock screen / unplug monitor / plug monitor
  • Verify that layouts weren't reset to defaults

• Test restart

  • Set custom layouts on each monitor
  • Restart the computer
  • Verify that layouts weren't reset to defaults

File Explorer Add-ons

• Running as user:
  • go to PowerToys repo root
  • verify the README.md Preview Pane shows the correct content
  • go to PowerToys repo and visit src\modules\ShortcutGuide\ShortcutGuide\svgs
  • verify Preview Pane works for the SVG files
  • verify the Icon Preview works for the SVG file (loop through different icon preview sizes)
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-PdfPreviewHandler\HelperFiles
  • verify Preview Pane works for the PDF file
  • verify the Icon Preview works for the PDF file (loop through different icon preview sizes)
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-GcodePreviewHandler\HelperFiles
  • verify Preview Pane works for the gcode file
  • verify the Icon Preview works for the gcode file (loop through different icon preview sizes)
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-StlThumbnailProvider\HelperFiles
  • verify the Icon Preview works for the stl file (loop through different icon preview sizes)
  • go to PowerToys repo and visit src\runner
  • verify Preview Pane works for source files (shows syntax highlighting)
• Running as admin (or user since recently):
  • open the Settings and turn off the Preview Pane and Icon Previous toggles
  • go to PowerToys repo root
  • verify the README.md Preview Pane doesn't show any content
  • go to PowerToys repo and visit src\runner\svgs
  • verify Preview Pane doesn't show the preview for the SVG files
  • the Icon Preview for the existing SVG will still show since the icons are cached (you can also use cleanmgr.exe to clean all thumbnails cached in your system). You may need to restart the machine for this setting to apply as well.
  • copy and paste one of the SVG file and verify the new file show the generic SVG icon
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-PdfPreviewHandler\HelperFiles
  • verify Preview Pane doesn't show the preview for the PDF file
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-GcodePreviewHandler\HelperFiles
  • verify Preview Pane doesn't show the preview for the gcode file
  • go to PowerToys repo and visit src\modules\previewpane\UnitTests-StlThumbnailProvider\HelperFiles
  • verify Preview Pane doesn't show the preview for the stl file (a generated thumbnail would show when there's no preview)
  • go to PowerToys repo and visit src\runner
  • verify Preview Pane doesn't show the preview for source code files or that it's a default previewer instead of Monaco

Keyboard Manager

UI Validation:

• In Remap keys, add and remove rows to validate those buttons. While the blank rows are present, pressing the OK button should result in a warning dialog that some mappings are invalid.
• Using only the Type buttons, for both the remap windows, try adding keys/shortcuts in all the columns. The right-side column in both windows should accept both keys and shortcuts, while the left-side column will accept only keys or only shortcuts for Remap keys and Remap shortcuts respectively. Validate that the Hold Enter and Esc accessibility features work as expected.
• Using the drop downs try to add key to key, key to shortcut, shortcut to key and shortcut to shortcut remapping and ensure that you are able to select remapping both by using mouse and by keyboard navigation.
• Validate that remapping can be saved by pressing the OK button and re-opening the windows loads existing remapping.

Remapping Validation:

For all the remapping below, try pressing and releasing the remapped key/shortcut and pressing and holding it. Try different behaviors like releasing the modifier key before the action key and vice versa.

• Test key to key remapping
  • A->B
  • Ctrl->A
  • A->Ctrl
  • Win->B (make sure Start menu doesn't appear accidentally)
  • B->Win (make sure Start menu doesn't appear accidentally)
  • A->Disable
  • Win->Disable
• Test key to shortcut remapping
  • A->Ctrl+V
  • B->Win+A
• Test shortcut to shortcut remapping
  • Ctrl+A->Ctrl+V
  • Win+A->Ctrl+V
  • Ctrl+V->Win+A
  • Win+A->Win+F
• Test shortcut to key remapping
  • Ctrl+A->B
  • Ctrl+A->Win
  • Win+A->B

• Test app-specific remaps
  • Similar remaps to above with Edge (entered as msedge), VSCode (entered as code) and cmd. For cmd try admin and non-admin (requires PT to run as admin)
  • Try some cases where focus is lost due to the shortcut. Example remapping to Alt+Tab or Alt+F4

• Test switching between remapping while holding down modifiers - Eg. Ctrl+D->Ctrl+A and Ctrl+E->Ctrl+V, hold Ctrl and press D followed by E. Should select all and paste over it in a text editor. Similar steps for Windows key shortcuts.

Mouse Utils

Find My Mouse:

• Enable FindMyMouse. Then, without moving your mouse:
  • Press Left Ctrl twice and verify the overlay appears.
  • Press any other key and verify the overlay disappears.
  • Press Left Ctrl twice and verify the overlay appears.
  • Press a mouse button and verify the overlay disappears.
• Disable FindMyMouse. Verify the overlay no longer appears when you press Left Ctrl twice.
• Enable FindMyMouse. Then, without moving your mouse:
  • Press Left Ctrl twice and verify the overlay appears.
• Enable the "Do not activate on game mode" option. Start playing a game that uses CG native full screen.
  • Verify the overlay no longer appears when you press Left Ctrl twice.
• Disable the "Do not activate on game mode" option. Start playing the same game.
  • Verify the overlay appears when you press Left Ctrl twice. (though it'll likely minimize the game)
• Test the different settings and verify they apply:
  • Overlay opacity
  • Background color
  • Spotlight color
  • Spotlight radius
  • Spotlight initial zoom (1x vs 9x will show the difference)
  • Animation duration

Mouse Highlighter:

• Enable Mouse Highlighter. Then:
  • Press the activation shortcut and press left and right click somewhere, verifying the hightlights are applied.
  • With left mouse button pressed, drag the mouse and verify the hightlight is dragged with the pointer.
  • With right mouse button pressed, drag the mouse and verify the hightlight is dragged with the pointer.
  • Press the activation shortcut again and verify no highlights appear when the mouse buttons are clicked.
  • Disable Mouse Highlighter and verify that the module is not activated when you press the activation shortcut.
• Test the different settings and verify they apply:
  • Change activation shortcut and test it
  • Left button highlight color
  • Right button highlight color
  • Opacity
  • Radius
  • Fade delay
  • Fade duration

Mouse Pointer Crosshairs:

• Enable Mouse Pointer Crosshairs. Then:
  • Press the activation shortcut and verify the crosshairs appear, and that they follow the mouse around.
  • Press the activation shortcut again and verify the crosshairs disappear.
  • Disable Mouse Pointer Crosshairs and verify that the module is not activated when you press the activation shortcut.
• Test the different settings and verify they apply:
  • Change activation shortcut and test it
  • Crosshairs color
  • Crosshairs opacity
  • Crosshairs center radius
  • Crosshairs thickness
  • Crosshairs border color
  • Crosshairs border size

Awake

• Try out the features and see if they work, no list at this time.