PowerToys/doc/releases/0.81.0/tests-checklist-anirudha.md

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

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\modules\ShortcutGuide\ShortcutGuide\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.

Always on Top

• Pin/unpin a window, verify it's topmost/not topmost.
• Pin/unpin a window, verify the border appeared/disappeared.
• Switch virtual desktop, verify border doesn't show up on another desktop.
• Minimize and maximize pinned window, verify the border looks as usual.
• Change border color and thickness.
• Verify if sound is played according to the sound setting.
• Exclude app, try to pin it.
• Exclude already pinned app, verify it was unpinned.
• Try to pin the app in the Game Mode.

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

Text Extractor

• Enable Text Extractor. Then:
  • Press the activation shortcut and verify the overlay appears.
  • Press Escape and verify the overlay disappears.
  • Press the activation shortcut and verify the overlay appears.
  • Right-click and select Cancel. Verify the overlay disappears.
  • Disable Text Extractor and verify that the activation shortuct no longer activates the utility.
• With Text Extractor enabled and activated:
  • Try to select text and verify it is copied to the clipboard.
  • Try to select a different OCR language by right-clicking and verify the change is applied.
• In a multi-monitor setup with different dpis on each monitor:
  • Verify text is correctly captured on all monitors.
• Test the different settings and verify they are applied:
  • Activation shortcut
  • OCR Language

File Locksmith

• Start the PowerToys installer executable and let it stay in the initial screen.
  • Right-click the executable file, select "What's using this file?" and verify it shows up. (2 entries will show, since the installer starts two processes)
  • End the tasks in File Locksmith UI and verify that closes the installer.
  • Start the installer executable again and press the Refresh button in File Locksmith UI. It should find new processes using the files.
  • Close the installer window and verify the processes are delisted from the File Locksmith UI. Close the window
• Start the PowerToys installer executable again and let it stay in the initial screen.
  • Right click the directory where the executable is located, select "What's using this file?" and verify it shows up.
  • Right click the drive where the executable is located, select "What's using this file?" and verify it shows up. You can close the PowerToys installer now.
• Restart PowerToys as admin.
  • Right click "Program Files", select "What's using this file?" and verify "PowerToys.exe" doesn't show up.
  • Press the File Locksmith "Restart as an administrator" button and verify "PowerToys.exe" shows up.

• Right-click the drive where Windows is installed, select "What's using this file?" and scroll down and up, verify File Locksmith doesn't crash with all those entries being shown. Repeat after clicking the File Locksmith "Restart as an administrator" button.
• Disable File Locksmith in Settings and verify the context menu entry no longer appears.

GPO

• Copy the "PowerToys.admx" file to your Policy Definition template folder. (Example: C:\Windows\PolicyDefinitions) and copy the "PowerToys.adml" file to the matching language folder in your Policy Definition folder. (Example: C:\Windows\PolicyDefinitions\en-US)
  • Open the "Local Group Policy Editor" on Windows and verify there is a "Microsoft PowerToys" folder in Administrative Templates for both Computer Configuration and User Configuration.
• In GPO, disable a module that can run as a standalone (FancyZones sounds good for this). Restart PowerToys.
  • Verify the module is not enabled.
  • Open settings and verify the module is not enabled and you can't enable it.
  • Try to open FancyZones Editor directly from the install folder and verify it doesn't run and adds a message to the log saying it didn't run because of GPO.
  • Verify the module can't be launched from the quick launcher system tray flyout launcher screen (FancyZones editor in this case).
  • Verify the module can't be enabled/disabled from the quick launcher system tray flyout.
• In GPO, enable a module that can run as a standalone (FancyZones sounds good for this). Restart PowerToys.
  • Verify the module is enabled.
  • Open settings and verify the module is enabled and you can't disable it.
  • Verify the module can't be enabled/disabled from the quick launcher system tray flyout.
• In GPO, try to set different settings in the Computer and User Configurations for a PowerToy. Restart PowerToys.
  • Verify that the setting in Computer Configuration has priority over the setting in User Configuration.
• In GPO, disable a module that has a context menu entry (File Locksmith sounds good for this). Restart PowerToys.
  • Verify the module is not enabled. (No context menu entry)
  • Open settings and verify the module is not enabled and you can't enable it.
  • Try to open File Locksmith directly from the install folder and verify it doesn't run and adds a message to the log saying it didn't run because of GPO.
• In GPO, disable a module that is a Preview Handler (Markdown Preview is good for this). Restart PowerToys.
  • Verify the module is not enabled. (Markdown files won't appear in the preview pane)
  • Open settings and verify the module is not enabled and you can't enable it.
• Remember to reset all you Settings to Not Configured after the tests, both in Conputer and User Configurations.

Registry Preview

• Open Registry Editor, add new registry key with 1 string value and 1 binary value in e.g. HKLM/Software/Classes/PowerToysTest. Right click new registry key->export and export it to file.

• Launch Registry Preview by right-clicking exported .reg file->'Preview'. Then:

  • Edit file content. Ensure that visual try is being re-populated while typing. Save the file by pressing Save file button. Confirm that file is properly saved by pressing Edit file... button which will open file in Notepad. Try saving file using Save file as... button.
  • Edit file externaly (e.g. in Notepad) and save it there. Pres Reload from file button and ensure that file content and visual tree are reloaded and show new content.
  • Select some registry key with registry values in visual tree and ensure that registry values are shown properly in bottom-right area.
  • Try opening different registry file by pressing Open file button.
  • Delete newly created registry key from first step manually in Registry Editor, then try writing registry changes to registry by pressing Write to Registry button in Registry Preview. Be careful what you are writing!

• Open Registry Preview Settings. Then:

  • Disable Registry Preview and ensure that Preview context menu option for .reg files no longer appears.
  • Try to launch Registry Preview from it's OOBE page while Registry Preview is disabled and ensure that it does not start.
  • Enable Registry Preview again and ensure that Preview context menu option for .reg files appears and that it starts Registry Preview correctly.
  • Try to launch Registry Preview from it's Settings page and ensure that it is launched properly.
  • Try to launch Registry Preview from it's OOBE page and ensure that it is launched properly.
  • Enable Default app setting. Verify that .reg files are opened with Registry Preview by default. Disable Default app setting. Verify that Registry Editor is now default app.

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.

Command Not Found

• Go to Command Not Found module settings

• If you have PowerShell 7.4 installed, confirm that Install PowerShell 7.4 button is not visible and PowerShell 7.4 is shown as detected. If you don't have PowerShell 7.4, Install it by clicking the button and confirm that it's properly installed. Check Installation logs text box bellow and confirm there are no errors.
• If you have Microsoft.WinGet.Client installed, confirm that Install Microsoft.WinGet.Client button is not visible and Microsoft.WinGet.Client is shown as detected. If you don't have Microsoft.WinGet.Client, Install it by clicking the button and confirm that it's properly installed. Check Installation logs text box bellow and confirm there are no errors.
• Install the Command Not Found module. Check Installation logs text box bellow and confirm there are no errors. Check PowerShell 7 $PROFILE file and confirm Import-Module command is added there. Start new PowerShell 7.4 session and execute "powertoys" (or "atom"). Confirm that suggestion is given to install powertoys (or atom) winget package. (If suggestion is not given, try running the same command few more times, it might take some time for the first time to load the module). Check Installation logs text box bellow and confirm there are no errors.
• Uninstall the module. Check Installation logs text box bellow and confirm there are no errors. Check PowerShell 7 $PROFILE file and confirm Import-Module command is removed. Start new PowerShell 7.4 session and confirm no errors are shown on start.
• Install module again. Uninstall PowerToys. Check PowerShell 7 $PROFILE file and confirm Import-Module command is removed after installer is done.