Calculator's UI tests currently run on Server 2022 VM images. However, the production app is primarily developed for Windows 11. This change moves the UI test jobs to run on Windows 11, so we can run our tests in an environment that's closer to what real users will experience.
- Use Visual Studio 2022
- Use an Azure Pipelines image which has Visual Studio 2022 installed
- Use the v143 C++ build tools
- Use the Windows SDK version 22000
- Raise the minimum platform version to 17763
- As a consequence of this change, we will use the "msix" file extension instead of "appx" for our packages
- Update UI tests from .NET Core 2.1 to .NET Core 3.1
* Added testcasefilter to the UI tests yaml
* Set priorities on UI tests
* Add UI tests for PRs yaml file, conditionally add it to the CI build yaml
* Update priority on functional tests
* Use a conditional task input instead of an additional yaml file to determine if UI tests should be filtered to P0 only
* Add condition:succeeded() back into the run-ui-tests.yaml
* Add back line
Co-authored-by: Matt Cooley <matt@mattcooley.net>
Fixes#462
- Add x64 and x86 UI tests to the release builds (internal builds for the store)
- UI tests now accept the target app ID as a parameter in the runsettings file
- Added the CalculatorUIFramework to handle the WinAppDriver logic.
- Added Standard Mode smoke tests and BVTs to the CalculatorUITests project.
- Removed old UI tests that did not use the CalculatorUIFramework
