diff --git a/doc/releases/0.83.0/tests-checklist-jaime.md b/doc/releases/0.83.0/tests-checklist-jaime.md index bf2cfbdcd4..ba12fd6f2c 100644 --- a/doc/releases/0.83.0/tests-checklist-jaime.md +++ b/doc/releases/0.83.0/tests-checklist-jaime.md @@ -195,26 +195,26 @@ Mouse Jump: ## 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. + - [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. * 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. + - [x] Verify the module is not enabled. + - [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. * 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. + - [x] Verify the module is enabled. + - [x] Open settings and verify the module is enabled and you can't disable it. + - [x] 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. + - [x] 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. + - [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. * 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. + - [x] Verify the module is not enabled. (Markdown files won't appear in the preview pane) + - [x] 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. ## Mouse Without Borders