src/modules/fancyzones/FancyZonesEditor.UITests/release-test-checklist.md
Refer to [release check list] (https://github.com/microsoft/PowerToys/blob/releaseChecklist/doc/releases/tests-checklist-template.md) for all manual tests.
For existing manual test-cases, we will convert them to UI-Tests and run them in CI and Release pipeline
Add test data and start → verify data is correct (custom layouts, template layouts, defaults, shortcut keys)
Create a new canvas - verify layout exists
Create a new canvas - cancel - doesn’t exist
Create a new grid - verify the layout exists
Create a new grid - cancel - doesn’t exist
Duplicate template by button (+ check default)
Duplicate template by menu (+ check default)
Duplicate custom by button (+ check shortcut key and default)
Duplicate custom by menu (+ check shortcut key and default)
Delete non-applied layout
Delete applied layout
Delete-cancel
Delete from context menu
Delete: hotkey released
Delete: default layout reset to default-default
Edit template and save
Edit template and cancel
Edit custom and save
Edit custom and cancel
Edit canvas: add zone
Edit canvas: delete zone
Edit canvas: move zone
Edit canvas: resize zone
Edit grid: split zone
Edit grid: merge zones
Edit grid: move splitter
UI Init: assigned layouts selected
UI Init: applied default - check params
UI Init: assigned custom layout, but id not found
Assign the same template but with different params to monitors
Assign layout on each monitor
Assign custom
Assign template
Assign shortcut key and save
Assign shortcut key and cancel
Reset shortcut key and save
Reset shortcut key and cancel
Set default layout + verify both prev and current after reopening
applied-layouts.json keeps info about not connected devices - verify they’re present after closing
applied-layouts.json keeps info about other virtual desktops
first launch without custom-layouts.json, default-layouts.json, layout-hotkeys.json and layout-templates.json