[Hosts] Migrating Hosts-File-Editor Manual Release Check-list to UI-Test

[jamrobot]

Description of the new feature / enhancement

Converting current manual release check-list to UI-Test cases.

Current manual test from [release check list] (https://github.com/microsoft/PowerToys/blob/releaseChecklist/doc/releases/tests-checklist-template.md#hosts-file-editor) are:

• Launch Host File Editor:
  • Verify the application exits if "Quit" is clicked on the initial warning. (HostsSettingTests.TestWarningDialog)
  • Launch Host File Editor again and click "Accept". The module should not close. (HostModuleTests.TestEmptyView)
  • 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. (HostModuleTests.TestFilterControl)
  • 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. (HostsSettingTests.TestWarningDialog)
  • Additional lines position.

Scenario when this would be used?

Hosts File Editor module.

Supporting information

No response

[jamrobot]

4 of 11 converted.
remaining 7 cases would be done in separated PR