PowerToys/doc/releases/0.77.0/tests-checklist-laszlo.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.

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

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

Appearance

• Change colors, opacity and Show zone number options. Verify they're applied.

Excluded apps

• Exclude some apps, verify that they're not applicable to a zone.

Dragging

• Hold Shift key to activate zones while dragging on, Use a non-primary mouse button to toggle zone activation off. Start dragging a window, then press shift. Zones are shown when dragging a window with shift pressed, hidden when you released shift or snapped zone.
• Hold Shift key to activate zones while dragging on, Use a non-primary mouse button to toggle zone activation off. Press shift first, then start dragging a window. Zones are shown when dragging a window with shift pressed, hidden when you released shift or snapped zone.
• Hold Shift key to activate zones while dragging off, Use a non-primary mouse button to toggle zone activation on. Zones are shown immediately when dragging a window and hidden when you click a non-primary mouse button or press shift.
• Hold Shift key to activate zones while dragging off, Use a non-primary mouse button to toggle zone activation off. Zones are shown immediately when dragging a window, hidden when you press shift.
• Hold Shift key to activate zones while dragging on, Use a non-primary mouse button to toggle zone activation on. Zones aren't shown immediately, only when shift is pressed or when a non-primary mouse click changes the state.
• Show zones on all monitor whilw dragging a window - turn on,off, verify behavior.
• Create a canvas layout with overlapping zones, check zone activation behavior with all When multiple zones overlap options
• Make dragged window transparent - turn on, off, verify behavior

Snapping

Disable FZ and clear app-zone-history.json before starting. FancyZones should be disabled, otherwise, it'll save cashed values back to the file.

• Snap a window to a zone by dragging, verify app-zone-history.json contains info about the window position on the corresponding work area.
• Snap a window to a zone by a keyboard shortcut, verify app-zone-history.json contains info about the window position on the corresponding work area.
• Snap a window to another monitor, verify app-zone-history.json contains positions about zones on both monitors.
• Snap a window to several zones, verify zone numbers in the json file are correct.
• Snap a window to a zone, unsnap it, verify this app was removed from the json file.
• Snap the same window to a zone on two different monitors or virtual desktops. Then unsnap from one of them, verify that info about unsnapped zone was removed from app-zone-history.json. Verify info about the second monitor/virtual desktop is kept.
• Enable Restore the original size of windows when unsnapping, snap window, unsnap window, verify the window changed its size to original.
• Disable Restore the original size of windows when unsnapping, snap window, unsnap window, verify window size wasn't changed.
• Disable Restore the original size of windows when unsnapping, snap window, enable Restore the original size of windows when unsnapping, unsnap window, verify window size wasn't changed.
• 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.

• 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.

Snapped window behavior

• Keep windows in their zones when the screen resolution changes on, snap a window to a zone, change the screen resolution or scaling, verify window changed its size and position.
• Keep windows in their zones when the screen resolution changes on, snap a window to a zone on the secondary monitor. Disconnect the secondary monitor (the window will be moved to the primary monitor). Reconnect the secondary monitor. Verify the window returned to its zone.
• Keep windows in their zones when the screen resolution changes off, snap a window to a zone, change the screen resolution or scaling, verify window didn't change its size and position.

Enable During zone layout changes, windows assigned to a zone will match new size/positions and prepare layouts with 1 and 3 zones where zone size/positions are different.

• Snap a window to zone 1, change the layout, verify window changed its size/position.
• Snap a window to zone 3, change the layout, verify window didn't change its size/position because another layout doesn't have a zone with this zone number.
• Snap a window to zones 1-2, change the layout, verify window changed its size/position to fit zone 1.
• Snap a window to zones 1-2, change the layout (the window will be snapped to zone 1), then return back to the previous layout, verify the window snapped to 1-2 zones.
• Disable During zone layout changes, windows assigned to a zone will match new size/positions, snap window to zone 1, change layout, verify window didn't change its size/position

Enable Move newly created windows to their last known zone.

• Snap a window to the primary monitor, close and reopen the window. Verify it's snapped to its zone.
• Snap a window to zones on the primary and secondary monitors. Close and reopen the app. Verify it's snapped to the zone on the active monitor.
• Snap a window to the secondary monitor (use a different app or unsnap the window from the zone on the primary monitor), close and reopen the window. Verify it's snapped to its zone.
• Snap a window, turn off FancyZones, move that window, turn FZ on. Verify window returned to its zone.
• Move unsnapped window to a secondary monitor, switch virtual desktop and return back. Verify window didn't change its position and size.
• Snap a window, then resize it (it's still snapped, but doesn't fit the zone). Switch the virtual desktop and return back, verify window didn't change its size.

Enable Move newly created windows to the current active monitor.

• Open a window that wasn't snapped anywhere, verify it's opened on the active monitor.

• Open a window that was snapped on the current virtual desktop and current monitor, verify it's opened in its zone.

• Open a window that was snappen on the current virtual desktop and another monitor, verify it's opened on the active monitor.

• Open a window that was snapped on another virtual desktop, verify it's opened on the active monitor.

• Enable Allow popup windows snapping and Allow child windows snapping, try to snap Notepad++ search window. Verify it can be snapped.

• Enable Allow popup windows snapping, snap Teams, verify a popup window appears in its usual position.

• Enable Allow popup windows snapping, snap Visual Studio Code to a zone, and open any menu. Verify the menu is where it's supposed to be and not on the top left corner of the zone.

• Enable Allow child windows snapping, drag any child window (e.g. Solution Explorer), verify it can be snapped to a zone.

• Disable Allow child windows snapping, drag any child window (e.g. Solution Explorer), verify it can't be snapped to a zone.

Switch between windows in the current zone

Enable Switch between windows in the current zone (default shortcut is Win + PgUp/PgDown)

• Snap several windows to one zone, verify switching works.
• Snap several windows to one zone, switch virtual desktop, return back, verify window switching works.
• Disable Switch between windows in the current zone, verify switching doesn't work.

Override Windows Snap

• Disable Override Windows Snap, verify it's disabled.

Enable Override Windows Snap. Select Move windows based on Zone index.

• Open the previously not snapped window, press Win+LeftArrow / Win+RightArrow, verify it's snapped to a first/last zone.

• Verify Win+LeftArrow moves the window to a zone with the previous index.

• Verify Win+RightArrow moves the window to a zone with the next index.

• Verify Win+ArrowUp and Win+ArrowDown work as usual.

• Move windows between zones across all monitors disabled. Verify Win+LeftArrow doesn't move the window to any zone when the window is in the first zone.

• Move windows between zones across all monitors disabled. Verify Win+RightArrow doesn't move the window to any zone when the window is in the last zone.

One monitor:

• Move windows between zones across all monitors enabled. Verify Win+LeftArrow doesn't move the window to any zone when the window is in the first zone.
• Move windows between zones across all monitors enabled. Verify Win+RightArrow doesn't move the window to any zone when the window is in the last zone.

Two and more monitors:

• Move windows between zones across all monitors enabled. Verify Win+LeftArrow cycles window position moving it from the first zone on the current monitor to the last zone of the left (or rightmost, if the current monitor is leftmost) monitor.
• Move windows between zones across all monitors enabled. Verify Win+RightArrow cycles window position moving it from the last zone on the current monitor to the first zone of the right (or leftmost, if the current monitor is rightmost) monitor.

Select Move windows based on Relative position.

• Open the previously not snapped window, press Win+Arrow, verify it's snapped.

• Extend the window using Ctrl+Alt+Win+Arrow. Verify the window is snapped to all zones.

• Extend the window using Ctrl+Alt+Win+Arrow and return it back using the opposite arrow. Verify it could be reverted while you hold Ctrl+Alt+Win.

• Move windows between zones across all monitors disabled. Verify Win+LeftArrow cycles the window position to the left (from the leftmost zone moves to the rightmost in the same row) within one monitor.

• Move windows between zones across all monitors disabled. Verify Win+RightArrow cycles the window position to the right within one monitor.

• Move windows between zones across all monitors disabled. Verify Win+UpArrow cycles the window position up within one monitor.

• Move windows between zones across all monitors disabled. Verify Win+DownArrow cycles the window position down within one monitor.

• Move windows between zones across all monitors enabled. Verify Win+LeftArrow cycles the window position to the left (from the leftmost zone moves to the rightmost in the same row) within all monitors.

• Move windows between zones across all monitors enabled. Verify Win+RightArrow cycles the window position to the right within all monitors.

• Move windows between zones across all monitors enabled. Verify Win+UpArrow cycles the window position up within all monitors.

• Move windows between zones across all monitors enabled. Verify Win+DownArrow cycles the window position down within all monitors.

Layout apply

Enable Enable quick layout switch, assign numbers to custom layouts.

• Switch with Win + Ctrl + Alt + key.
• Switch with just a key while dragging a window.
• Turn Flash zones when switching layout on/off, verify it's flashing/not flashing after pressing the shortcut.
• Disable Enable quick layout switch, verify shortcuts don't work.
• Disable spacing on any grid layout, verify that there is no space between zones while dragging a window.
• Create a new 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.
• Apply a grid layout, change the screen resolution or scaling, 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.

Layout reset

• 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

Span zones across monitors

• Switch between Allow zones to span across monitors on and off. Verify that layouts are applied correctly in both cases.

Repeat the previous subsections steps after enabling Allow zones to span across monitors

• Dragging
• Snapping
• Snapped window behavior
• Switch between windows in the current zone
• Override Windows Snap
• Layout apply
• Layout reset

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.

Shortcut Guide

• Run PowerToys as user:
  • Verify Win + Shift + / opens the guide
  • Change the hotkey to a different shortcut (e.g. Win + /) and verify it works
  • Set Shortcut Guide to start with a Windows key press and verify it works.
• Restore the Win + Shift + / hotkey.
  • Open the guide and close it pressing Esc
  • Open the guide and close it pressing and releasing the Win key
• With PowerToys running as a user, open an elevated app and keep it on foreground:
  • Verify Win + Shift + / opens the guide
  • Verify some of the shortcuts shown in the guide work and the guide is closed when pressed

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.

Awake

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

Quick Accent

• Enable Quick Accent and open notepad. Then:
  • Press a and the left or right arrow and verify the accent menu appears and adds the accented letter you've selected. Use left and arrow keys to cycle through the options.
  • Press a and the space key and verify the accent menu appears and adds the accented letter you've selected. Use Space to navigate forward, Space + Shift to navigate backward.
  • Disable Quick Accent and verify you can no longer add accented characters through Quick Accent.
• Test the different settings and verify they are applied:
  • Activation key
  • Language (for example, Currency has no accents for 'a' but has for 's')
  • Toolbar position (test every option, some had issues before)
  • Input delay
  • Exclude some apps. Verify that Quick Accent is not activated for them.
  • Sort characters by frequency.
  • Always start on the first character when using left/right arrows as activation method.

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.

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.

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.