PowerToys/doc/releases/0.74.0/tests-checklist-andrey.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
• test installing as SYSTEM (LocalSystem account)
  • Download PsTools from https://learn.microsoft.com/en-us/sysinternals/downloads/psexec
  • Run PowerToys installer with psexec tool psexec.exe -sid <path_to_installer_exe
  • Brief check if all modules are working

• PER-USER and PER-MACHINE TESTS:
  • Install previous version on a clean machine and update with new per-machine version. Ensure that it is installed in Program files and that registry entries are under HKLM/Software/Classes/PowerToys. Go trhough different modules and ensure that they are working correctly.
  • Try installing per-user version over already installed per-machine version and ensure that proper error message is shown.
  • Remove PowerToys and install per-user version. Ensure that it is installed in /Local/PowerToys and that registry entries are under HKCU/Software/Classes/PowerToys. Go trhough different modules and ensure that they are working correctly.
  • Create a new user and install per-user version there as well. Go trhough different modules and ensure that they are working correctly. Ensure that changing settings for one user does not change settings of other user.

Functional tests

Regressions:

• https://github.com/microsoft/PowerToys/issues/1414#issuecomment-593529038
• https://github.com/microsoft/PowerToys/issues/1524

Localization

Change the Windows language to a language different than English. Then verify if the following screens change their language:

• System tray menu items
• Settings
• OOBE (What's new)
• Keyboard Manager Editor
• Color Picker (check the tooltips)
• FancyZones Editor
• Power Rename (new WinUI 3 may not be localized)
• PowerToys Run ("Start typing" string is localized, for example)
• Image Resizer
• Shortcut Guide (Windows controls are localized)
• File Explorer menu entries for Image Resizer, Power Rename and FileLocksmith
• Hosts File Editor
• File Locksmith

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

Quick access tray icon flyout:

• Use left click on the system tray icon and verify the flyout appears. (It'll take a bit the first time)
• Try to launch a module from the launch screen in the flyout.
• Try disabling a module in the all apps screen in the flyout, make it a module that's launchable from the launch screen. Verify that the module is disabled and that it also disappeared from the launch screen in the flyout.
• Open the main settings screen on a module page. Verify that when you disable/enable the module on the flyout, that the Settings page is updated too.

Settings backup/restore:

• In the General tab, create a backup of the settings.
• Change some settings in some PowerToys.
• Restore the settings in the General tab and verify the Settings you've applied were reset.

Color Picker

• Enable the Color Picker in settings and ensure that the hotkey brings up Color Picker
  • when PowerToys is running unelevated on start-up
  • when PowerToys is running as admin on start-up
  • when PowerToys is restarted as admin, by clicking the restart as admin button in the settings

• Change Activate Color Picker shortcut and check the new shortcut is working
• Try all three Activation behaviors(Color Picker with editor mode enabled, Editor, Color Picker only)
• Change Color format for clipboard and check if the correct format is copied from the Color picker
• Try to copy color formats to the clipboard from the Editor
• Check Show color name and verify if color name is shown in the Color picker
• Enable one new format, disable one existing format, reorder enabled formats and check if settings are populated to the Editor
• Select a color from the history in the Editor
• Remove color from the history in the Editor
• Open the Color Picker from the Editor
• Open Adjust color from the Editor
• Check Color Picker logs for errors

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.

PowerRename

• Check if disable and enable of the module works. (On Win11) Check if both old context menu and Win11 tier1 context menu items are present when module is enabled.
• Check that with the Show icon on context menu icon is shown and vice versa.
• Check if Appear only in extended context menu works.
• Enable/disable autocomplete.
• Enable/disable Show values from last use.

• Select several files and folders and check PowerRename options:
  • Make Uppercase/Lowercase/Titlecase (could be selected only one at the time)
  • Exclude Folders/Files/Subfolder Items (could be selected several)
  • Item Name/Extension Only (one at the time)
  • Enumerate Items. Test advanced enumeration using different values for every field ${start=10,increment=2,padding=4}.
  • Case Sensitive
  • Match All Occurrences. If checked, all matches of text in the Search field will be replaced with the Replace text. Otherwise, only the first instance of the Search for text in the file name will be replaced (left to right).
  • Use regular expressions
    • Search with an expression (e.g. (.*).png)
    • Replace with an expression (e.g. foo_$1.png)
    • Replace using file creation date and time (e.g. $hh-$mm-$ss-$fff $DD_$MMMM_$YYYY)
    • Turn on Use Boost library and test with Perl Regular Expression Syntax (e.g. (?<=t)est)
  • File list filters.
    • In the preview window uncheck some items to exclude them from renaming.
    • Click on the Renamed column to filter results.
    • Click on the Original column to cycle between checked and unchecked items.

VCM

• Check "Hide toolbar when both camera and microphone are unmuted" and verify that it works
• Uncheck it, mute the microphone with the hotkey and make sure the toolbar doesn't hide after a timeout
• Go to some video conference application settings, e.g. meet.google.com, Microsoft Teams, Skype. "Select PowerToys VideoConference Mute" camera as an active device and try to mute it with a hotkey
• Go to Control Panel -> Sound -> Recording -> select default mic -> open its properties -> Levels. Now mute the microphone with a corresponding hotkey and verify that mute icon on the right side of volume slider reflects its muted status.
• Go to Control Panel -> Sound -> Recording -> select default mic -> open its properties -> Levels. Now press and release push-to-talk hotkey and verify that mute icon on the right side of volume slider reflects the actions.
• Verify that changing "toolbar position" setting works
• Select an overlay image and verify that muting camera now shows the image instead of black screen. (Don't forget to restart the application which uses the camera).
• Try to select an overlay image when PT process is elevated.

Screen Ruler

• Enable Screen Ruler. Then:

  • Press the activation shortcut and verify the toolbar appears.
  • Press the activation shortcut again and verify the toolbar disappears.
  • Disable Screen Ruler and verify that the activation shortuct no longer activates the utility.
  • Enable Screen Ruler and press the activation shortcut and verify the toolbar appears.
  • Select the close button in the toolbar and verify it closes the utility.

• With Screen Ruler enabled and activated:

  • Use the Bounds utility to measure a zone by dragging with left-click. Verify right click dismisses the utility and that the measurement was copied into the clipboard.
  • Use the Spacing utility to measure something and verify that left-click copies the measurement to the clipboard. Verify that right-click dismisses the utility.
  • Use the Horizontal Spacing utility to measure something and verify that left-click copies the measurement to the clipboard. Verify that right-click dismisses the utility.
  • Use the Vertical Spacing utility to measure something and verify that left-click copies the measurement to the clipboard. Verify that right-click dismisses the utility.
  • While using a Spacing utility, verify that using the mouse scroll wheel will adjust pixel color tolerance while measuring.
  • Open mspaint and draw 1px-thick straight line, also click with a pencil to draw a single pixel. In any Spacing mode, verify that one of line's dimension is 1, and pixel's dimensions are 1x1.

• In a multi-monitor setup with different dpis on each monitor:

  • Verify that the utilities work well on each monitor, with continuous mode on and off.
  • Without any window opened and a solid color as your background, verify the horizontal spacing matches the monitor's pixel width.
  • Move your mouse back and forth around the edge of two monitors really quickly in each mode - verify nothing is broken.

• Test the different settings and verify they are applied:

  • Activation shortcut
  • Continous mode
  • Per color channel edge detection
  • Pixel tolerance for edge detection
  • Draw feet on cross
  • Line color

Hosts File Editor

• Launch Host File Editor:
  • Verify the application exits if "Quit" is clicked on the initial warning.
  • Launch Host File Editor again and click "Accept". The module should not close. Open the hosts file (%WinDir%\System32\Drivers\Etc) in a text editor that auto-refreshes so you can see the changes applied by the editor in real time. (VSCode is an editor like this, for example)
  • Enable and disable lines and verify they are applied to the file.
  • Add a new entry and verify it's applied.
  • Add manually an entry with more than 9 hosts in hosts file (Windows limitation) and verify it is split correctly on loading and the info bar is shown.
  • Try to filter for lines and verify you can find them.
  • Click the "Open hosts file" button and verify it opens in your default editor. (likely Notepad)
• Test the different settings and verify they are applied:
  • Launch as Administrator.
  • Show a warning at startup.
  • Additional lines position.

Peek

• Open different files to check that they're shown properly

  • Image
  • Text or dev file
  • Markdown file
  • PDF
  • HTML
  • Archive files (.zip, .tar, .rar)
  • Any other not mentioned file (.exe for example) to verify the unsupported file view is shown

• Pinning/unpinning

  • Pin the window, switch between images of different size, verify the window stays at the same place and the same size.
  • Pin the window, close and reopen Peek, verify the new window is opened at the same place and the same size as before.
  • Unpin the window, switch to a different file, verify the window is moved to the default place.
  • Unpin the window, close and reopen Peek, verify the new window is opened on the default place.

• Open with a default program

  • By clicking a button.
  • By pressing enter.

• Switch between files in the folder using LeftArrow and RightArrow, verify you can switch between all files in the folder.
• Open multiple files, verify you can switch only between selected files.
• Change the shortcut, verify the new one works.

Mouse Without Borders

• Install PowerToys on two PCs in the same local network:

  • Verify that PowerToys is properly installed on both PCs.

• Setup Connection:

  • Open MWB's settings on the first PC and click the "New Key" button. Verify that a new security key is generated.
  • Copy the generated security key and paste it in the corresponding input field in the settings of MWB on the second PC. Also enter the name of the first PC in the required field.
  • Press "Connect" and verify that the machine layout now includes two PC tiles, each displaying their respective PC names.

• Verify Connection Status:

  • Ensure that the border of the remote PC turns green, indicating a successful connection.
  • Enter an incorrect security key and verify that the border of the remote PC turns red, indicating a failed connection.

• Test Remote Mouse/Keyboard Control:

  • With the PCs connected, test the mouse/keyboard control from one PC to another. Verify that the mouse/keyboard inputs are correctly registered on the other PC.
  • Test remote mouse/keyboard control across all four PCs, if available. Verify that inputs are correctly registered on each connected PC when the mouse is active there.

• Test Remote Control with Elevated Apps:

  • Open an elevated app on one of the PCs. Verify that without "Use Service" enabled, PowerToys does not control the elevated app.
  • Enable "Use Service" in MWB's settings. Verify that PowerToys can now control the elevated app remotely. Verify that MWB processes are running as LocalSystem, while the MWB helper process is running non-elevated.
  • Toggle "Use Service" again, verify that each time you do that, the MWB processes are restarted.
  • Run PowerToys elevated on one of the machines, verify that you can control elevated apps remotely now on that machine.

• Test Module Enable Status:

  • For all combinations of "Use Service"/"Run PowerToys as admin", try enabling/disabling MWB module and verify that it's indeed being toggled using task manager.

• Test Disconnection/Reconnection:

  • Disconnect one of the PCs from network. Verify that the machine layout updates to reflect the disconnection.
  • Do the same, but now by exiting PowerToys.
  • Start PowerToys again, verify that the PCs are reconnected.

• Test Various Local Network Conditions:

  • Test MWB performance under various network conditions (e.g., low bandwidth, high latency). Verify that the tool maintains a stable connection and functions correctly.

• Clipboard Sharing:

  • Copy some text on one PC and verify that the same text can be pasted on another PC.
  • Use the screenshot key and Win+Shift+S to take a screenshot on one PC and verify that the screenshot can be pasted on another PC.
  • Copy a file in Windows Explorer and verify that the file can be pasted on another PC. Make sure the file size is below 100MB.
  • Try to copy multiple files and directories and verify that it's not possible (only the first selected file is being copied).

• Drag and Drop:

  • Drag a file from Windows Explorer on one PC, cross the screen border onto another PC, and release it there. Verify that the file is copied to the other PC. Make sure the file size is below 100MB.
  • While dragging the file, verify that a corresponding icon is displayed under the mouse cursor.
  • Without moving the mouse from one PC to the target PC, press CTRL+ALT+F1/2/3/4 hotkey to switch to the target PC directly and verify that file sharing/dropping is not working.

• Lock and Unlock with "Use Service" Enabled:

  • Enable "Use Service" in MWB's settings.
  • Lock a remote PC using Win+L, move the mouse to it remotely, and try to unlock it. Verify that you can unlock the remote PC.
  • Disable "Use Service" in MWB's settings, lock the remote PC, move the mouse to it remotely, and try to unlock it. Verify that you can't unlock the remote PC.

• Test Settings:

  • Change the rest of available settings on MWB page and verify that each setting works as described.