-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚧 Testing input injector with 1.2.221109.1 WinAppSDK in CI #183
base: main
Are you sure you want to change the base?
Conversation
23c2fb2
to
4603e0f
Compare
Looks like installing the SDK is still broken for MSTest based projects? Added comment here. Also filed microsoft/WindowsAppSDK#2706 in general for MSTest discovery being broken in VS locally with the update to 1.1.x over 1.0.3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just using GitHub to test incrementing the WinAppSDK version to the new hotfix release they did. Need to rebase this branch later, as we centralized these properties in main.
labs/CanvasLayout/samples/CanvasLayout.WinAppSdk/CanvasLayout.WinAppSdk.csproj
Outdated
Show resolved
Hide resolved
labs/SizerBase/samples/SizerBase.WinAppSdk/SizerBase.WinAppSdk.csproj
Outdated
Show resolved
Hide resolved
template/lab/samples/ProjectTemplate.WinAppSdk/ProjectTemplate.WinAppSdk.csproj
Outdated
Show resolved
Hide resolved
7415c91
to
74ac8f5
Compare
Filed microsoft/WindowsAppSDK#2768 for tracking our issues with installing the 1.1.x series of packages still on GitHub Actions. |
7baa9ea
to
7a127a9
Compare
See comments in #124
See microsoft/WindowsAppSDK#2706 Seems like discovery works, but now `Window.Current` fails to activate.
7a127a9
to
f2f2e04
Compare
6ac2a45
to
9f2f637
Compare
9f2f637
to
003be08
Compare
This PR blocked in CI from running by: actions/runner-images#6585 |
(Basically, ensure we're on a version of .NET we're expecting in the CI to build with until we want to upgrade.)
Start instance based fluent pattern for InputSimulator Move Bounds logic to simulator
Fix issue with UWP and WeakReference
Well, the WinUI 3 pipeline failed due to the CommunityToolkit/Tooling-Windows-Submodule#9 issue... and there's some info about NuGet restore in the linux build... BUT The WinUI 3 Injection test ran in the CI: At least this shows that it looks viable to do this as a methodology. Been tinkering with a test for GridSplitter to check the mouse cursor changing when over the splitter for the bug I last called out for #101, that'll be a bit more interesting to run in the CI. |
Should look at the Input helpers from the WinUI library as well to look at how their tests are written and see what makes sense to have similar helpers on in our new API: https://github.com/microsoft/microsoft-ui-xaml/blob/main/test/testinfra/MUXTestInfra/Common/InputHelper.cs |
Not working locally, but want to get output from CI as well, think MSTest discovery is still broken by update from 1.0.3 to 1.1.2. Going to open issue.