PowerToys/doc/releases/0.65.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

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 and Power Rename
• 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

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.

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.
• Assign horizontal and vertical default layouts
• Test duplicate layout focus
  • Select any layout X in 'Templates' or 'Custom' section by click left mouse button
  • Mouse right button click on any layout Y in 'Templates' or 'Custom' sections
  • Duplicate it by clicking 'Create custom layout' (Templates section) or 'Duplicate' in 'Custom' section
  • Expect the layout Y is duplicated

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.
• Disable spacing on any grid layout, verify that there is no space between zones while dragging a window.
• 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.

• Open Task view , right-click on the window, check the Show this window on all desktops or the Show windows from this app on all desktops option to turn it on.
  • Turn Show this window on all desktops on, verify you can snap this window to a zone.
  • Turn Show windows from this app on all desktops on, verify you can snap this window to a zone.
• 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.

• Apply 2 windows to the same zone, verify that window swithing works (Win + PgUp/PgDown)
• Verify that window switching still works after switching to another virtual desktop and back.
• 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

• Test applying default layouts on reset

  • Set default horizontal and vertical layouts
  • Delete applied-layouts.json
  • Verify that selected default layout is applied according to configuration

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

Awake

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

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.