mirror/PowerToys
1
0
Fork 0
mirror of https://github.com/microsoft/PowerToys.git synced 2024-12-04 20:21:18 +08:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
b12fa3f007
PowerToys/doc/releases/0.81.0/tests-checklist-jaime.md
Jaime Bernardo a9f792fc6c
Update tests-checklist-jaime.md
2024-05-15 11:52:17 +01:00

21 KiB
Raw Blame History

Image Resizer

  • Disable the Image Resizer and check that Resize images is absent in the context menu

  • Enable the Image Resizer and check that Resize images is present in the context menu. (On Win11) Check if both old context menu and Win11 tier1 context menu items are present when module is enabled.

  • Remove one image size and add a custom image size. Open the Image Resize window from the context menu and verify that changes are populated

  • Resize one image

  • Resize multiple images

  • Open the image resizer to resize a .gif file and verify the "Gif files with animations may not be correctly resized." warning appears.

  • Resize images with Fill option

  • Resize images with Fit option

  • Resize images with Stretch option

  • Resize images using dimension: Centimeters

  • Resize images using dimension: Inches

  • Resize images using dimension: Percents

  • Resize images using dimension: Pixels

  • Change Filename format to %1 - %2 - %3 - %4 - %5 - %6 and check if the new format is applied to resized images

  • Check Use original date modified and verify that modified date is not changed for resized images. Take into account that Resize the original pictures(don't create copy) should be selected

  • Check Make pictures smaller but not larger and verify that smaller pictures are not resized

  • Check Resize the original pictures (don't create copies) and verify that the original picture is resized and a copy is not created

  • Uncheck Ignore the orientation of pictures and verify that swapped width and height will actually resize a picture if the width is not equal to the height

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

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.

PowerToys Run

  • Enable PT Run in settings and ensure that the hotkey brings up PT Run
    • 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 settings.
  • Check that each of the plugins is working:
    • Program - launch a Win32 application
    • Program - launch a Win32 application as admin
    • Program - launch a packaged application
    • Calculator - ensure a mathematical input returns a correct response and is copied on enter.
    • Windows Search - open a file on the disk.
    • Windows Search - find a file and copy file path.
    • Windows Search - find a file and open containing folder.
    • Shell - execute a command. Enter the action keyword >, followed by the query, both with and without space (e.g. > ping localhost).
    • Folder - Search and open a sub-folder on entering the path.
    • Uri - launch a web page on entering the uri.
    • Window walker - Switch focus to a running window.
    • Service - start, stop, restart windows service. Enter the action keyword ! to get the list of services.
    • Registry - navigate through the registry tree and open registry editor. Enter the action keyword : to get the root keys.
    • Registry - navigate through the registry tree and copy key path.
    • System - test lock.
    • System - test empty recycle bin.
    • System - test shutdown.

  • Disable PT Run and ensure that the hotkey doesn't bring up PT Run.

  • Test tab navigation.

  • Test Plugin Manager
    • Enable/disable plugins and verify changes are picked up by PT Run
    • Change Direct activation phrase and verify changes are picked up by PT Run
    • Change Include in global result and verify changes picked up by PT Run
    • Clear Direct activation phrase and uncheck Include in global result. Verify a warning message is shown.
    • Disable all plugins and verify the warning message is shown.

OOBE

  • Quit PowerToys
  • Delete %localappdata%\Microsoft\PowerToys
  • Start PowerToys and verify OOBE opens
  • Change version saved on %localappdata%\Microsoft\PowerToys\last_version.txt
  • Start PowerToys and verify OOBE opens in the "What's New" page
  • Visit each OOBE section and for each section:
    • open the Settings for that module
    • verify the Settings work as expected (toggle some controls on/off etc.)
    • close the Settings
    • if it's available, test the Launch module name button
  • Close OOBE
  • Open the Settings and from the General page open OOBE using the Welcome to PowerToys link

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
    • Change activation method to shake and activate by shaking your mouse pointer
    • Excluded apps

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

Mouse Jump:

  • Enable Mouse Jump. Then:
    • Press the activation shortcut and verify the screens preview appears.
    • Change activation shortcut and verify that new shorctut triggers Mouse Jump.
    • Click around the screen preview and ensure that mouse cursor jumped to clicked location.
    • Reorder screens in Display settings and confirm that Mouse Jump reflects the change and still works correctly.
    • Change scaling of screens and confirm that Mouse Jump still works correctly.
    • Unplug additional monitors and confirm that Mouse Jump still works correctly.
    • Disable Mouse Jump and verify that the module is not activated when you press the activation shortcut.

Awake

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

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

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.

Paste As Plain Text

  • Copy some rich text (e.g word of the text is different color, another work is bold, underlined, etd.). Then:
    • Paste the text using standard Windows Ctrl + V shortcut and ensure that rich text is pasted (with all colors, formatting, etc.)
    • Paste the text using Paste As Plain Text activation shortcut and ensure that plain text without any formatting is pasted.
    • Paste again the text using standard Windows Ctrl + V shortcut and ensure the text is now pasted plain without formatting as well.
    • Change the activation shorctut and ensure that Paste As Plain Text is triggered using new shortcut.
    • Disable the module and ensure that text is not being pasted using activation shortcut.

Crop And Lock

  • Thumbnail mode

    • Test with win32 app
    • Test with packaged app

  • Reparent mode (there are known issues where reparent mode doesn't work for some apps)

    • Test with win32 app
    • Test with packaged app

Environment Variables

  • NOTE: Make backup of USER and SYSTEM Path and TMP variables before testing so you can revert those is something goes wrong!

  • Open Environment Variables settings

    • Launch as administrator ON - Launch Environment Variables and confirm that SYSTEM variables ARE editable and Add variable button is enabled
    • Launch as administrator OFF - Launch Environment Variables and confirm that SYSTEM variables ARE NOT editable and Add variable button is disabled

  • User/System variables

    • Add new User variable. Open OS Environment variables window and confirm that added variable is there. Also, confirm that it's added to "Applied variables" list.
    • Edit one User variable. Open OS Environment variables window and confirm that variable is changed. Also, confirm that change is applied to "Applied variables" list.
    • Remove one User variable. Open OS Environment variables window and confirm that variable is removed. Also, confirm that variable is removed from "Applied variables" list.
    • Repeat the steps for System variables.

  • Profiles - Basic tests

    • Add new profile with no variables and name it "Test_profile_1" (referenced below by name)
    • Edit "Test_profile_1": Add one new variable to profile e.g. name: "profile_1_variable_1" value: "profile_1_value_1"
    • Add new profile "Test_profile_2": From "Add profile dialog" add two new variables (profile_2_variable_1:profile_2_value_1 and profile_2_variable_2:profile_2_value_2). Set profile to enabled and click Save. Open OS Environment variables window and confirm that all variables from the profile are applied correctly. Also, confirm that "Applied variables" list contains all variables from the profile.
    • Apply "Test_profile_1" while "Test_profile_2" is still aplpied. Open OS Environment variables window and confirm that all variables from Test_profile_2 are unapplied and that all variables from Test_profile_1 are applied. Also, confirm that state of "Applied variables" list is updated correctly.
    • Unapply applied profile. Open OS Environment variables window and confirm that all variables from the profile are unapplied correctly. Also, confirm that "Applied variables" list does not contain variables from the profile.

  • Overriding existing variable

    • To "Test_profile_1" add one existing variable from USER variables, e.g. TMP. After adding, change it's value to e.g "test_TMP" (or manually add variable named TMP with value test_TMP).
    • Apply "Test_profile_1". Open OS Environment variables window and confirm that TMP variable in USER variables has value "test_TMP". Confirm that there is backup variable "TMP_PowerToys_Test_profile_1" with original value of TMP var. Also, confirm that "Applied variables" list is updated correctly - there is TMP profile variable, and backup User variable..
    • Unapply "Test_profile_1". Open OS Environment variables window and confirm that TMP variable in USER variable has original value and that there is no backup variable. Also, confirm that "Applied variables" list is updated correctly.

  • PATH variable

    • In "Applied variables" list confirm that PATH variable is shown properly: value of USER Path concatenated to the end of SYSTEM Path.
    • To "Test_profile_1" add variable named PATH with value "path1;path2;path3" and click Save. Confirm that PATH variable in profile is shown as list (list of 3 values and not as path1;path2;path3).
    • Edit PATH variable from "Test_profile_1". Try different options from ... menu (Delete, Move up, Move down, etc...). Click Save.
    • Apply "Test_profile_1". Open OS Environment variables window and confirm that profile is applied correctly - Path value and backup variable. Also, in "Applied variables" list check that Path variable has correct value: value of profile PATH concatenated to the end of SYSTEM Path.

  • Loading profiles on startup

    • Close the app and reopen it. Confirm that the state of the app is the same as before closing.
  • "Test_profile_1" should still be applied (if not apply it). Delete "Test_profile_1". Confirm that profile is unapplied (both in OS Environment variables window and "Applied variables" list).
  • Delete "Test_profile_2". Check profiles.json file and confirm that both profiles are gone.