- [x] Disable the Image Resizer and check that `Resize images` is absent in the context menu
- [x] 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.
- [x] 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
- [x] Resize one image
- [x] Resize multiple images
- [x] Open the image resizer to resize a `.gif` file and verify the "Gif files with animations may not be correctly resized." warning appears.
- [x] Change `Filename format` to `%1 - %2 - %3 - %4 - %5 - %6` and check if the new format is applied to resized images
- [x] 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
- [x] Check `Make pictures smaller but not larger` and verify that smaller pictures are not resized
- [x] Check `Resize the original pictures (don't create copies)` and verify that the original picture is resized and a copy is not created
- [x] 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
- [x] 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)
- [x] End the tasks in File Locksmith UI and verify that closes the installer.
- [x] Start the installer executable again and press the Refresh button in File Locksmith UI. It should find new processes using the files.
- [x] Close the installer window and verify the processes are delisted from the File Locksmith UI. Close the window
- [x] Right click the directory where the executable is located, select "What's using this file?" and verify it shows up.
- [x] 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.
- [x] Right click "Program Files", select "What's using this file?" and verify "PowerToys.exe" doesn't show up.
- [x] Press the File Locksmith "Restart as an administrator" button and verify "PowerToys.exe" shows up.
- [x] 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.
- [x] Disable File Locksmith in Settings and verify the context menu entry no longer appears.
- [x] Verify the application exits if "Quit" is clicked on the initial warning.
- [x] 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)
- [x] Enable and disable lines and verify they are applied to the file.
- [x] Add a new entry and verify it's applied.
- [x] 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.
- [x] Try to filter for lines and verify you can find them.
- [x] Click the "Open hosts file" button and verify it opens in your default editor. (likely Notepad)
* 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)
- [x] 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.
- [x] Open settings and verify the module is not enabled and you can't enable it.
- [x] 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.
- [x] Verify the module can't be launched from the quick launcher system tray flyout launcher screen (FancyZones editor in this case).
- [x] Verify the module can't be enabled/disabled from the quick launcher system tray flyout.
- [x] Verify the module is not enabled. (No context menu entry)
- [x] Open settings and verify the module is not enabled and you can't enable it.
- [x] 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.
* 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:
- [x] Uncheck ReadOnly checkbox and 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.
- [x] 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.
- [x] Select some registry key with registry values in visual tree and ensure that registry values are shown properly in bottom-right area.
- [x] Try opening different registry file by pressing Open file button.
- [x] 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!*
- [x] Disable Registry Preview and ensure that Preview context menu option for .reg files no longer appears.
- [x] Try to launch Registry Preview from it's OOBE page while Registry Preview is disabled and ensure that it does not start.
- [x] Enable Registry Preview again and ensure that Preview context menu option for .reg files appears and that it starts Registry Preview correctly.
- [x] Try to launch Registry Preview from it's Settings page and ensure that it is launched properly.
- [x] Try to launch Registry Preview from it's OOBE page and ensure that it is launched properly.
- [x] 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.
- [x] Open MWB's settings on the first PC and click the "New Key" button. Verify that a new security key is generated.
- [x] 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.
- [x] Press "Connect" and verify that the machine layout now includes two PC tiles, each displaying their respective PC names.
- [x] 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.
- [x] 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.
- [x] Open an elevated app on one of the PCs. Verify that without "Use Service" enabled, PowerToys does not control the elevated app.
- [x] 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.
- [x] Toggle "Use Service" again, verify that each time you do that, the MWB processes are restarted.
- [x] Run PowerToys elevated on one of the machines, verify that you can control elevated apps remotely now on that machine.
- [x] 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.
- [x] Test MWB performance under various network conditions (e.g., low bandwidth, high latency). Verify that the tool maintains a stable connection and functions correctly.
- [x] 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.
- [x] While dragging the file, verify that a corresponding icon is displayed under the mouse cursor.
- [x] 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.
- [x] 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.
- [x] 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.
