Conversation
| <XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" /> | ||
| <!-- Other merged dictionaries here --> | ||
| </ResourceDictionary.MergedDictionaries> | ||
| <ResourceDictionary.ThemeDictionaries> |
There was a problem hiding this comment.
Are these resources pasted over from WinUI Gallery? If not all resources are required, may be worth it to clean it up.
azure-pipelines.yml
Outdated
| displayName: 'List contents of ArtifactStagingDirectory and DefaultWorkingDirectory' | ||
|
|
||
| - task: VSTest@2 | ||
| displayName: 'Run Unit Tests' |
There was a problem hiding this comment.
Might be worth it to label it as "Run Sample Unit Tests" since these mostly serve as a demonstration rather than an actual test.
|
I'm wondering if having unit tests also warrants having a |
| namespace AppUIBasics | ||
| { | ||
| class IdleSynchronizer | ||
| public class IdleSynchronizer |
There was a problem hiding this comment.
Is this related to the unit tests?
There was a problem hiding this comment.
At one point I was using it from one of the unit tests. I'll leave it as it is.
| @@ -0,0 +1,65 @@ | |||
| <Project Sdk="Microsoft.NET.Sdk"> | |||
There was a problem hiding this comment.
Do we not need a certificate for the unit types project?
There was a problem hiding this comment.
We're not creating an msix so we don't need the cert.
This adds a set of unit tests to WinUIGallery. The initial set of tests are mostly just to serve as a demonstration of how to write tests in MSTest for WinUI. But as new features are added to WinUI we can optionally write them in a more unit-testable way and add new tests here. Unit tests have the advantage of being quicker and more reliable that UI Interaction tests which is where we are getting most of the coverage now. I've also updated the Azure Pipeline job to execute the unit tests as part of the build. This PR updates the version of WinAppSDK from 1.4 to 1.5 Preview1. Once 1.5.0 stable is released we should update to that. --------- Co-authored-by: Keith Mahoney <you@example.com>
This adds a set of unit tests to WinUIGallery.
The initial set of tests are mostly just to serve as a demonstration of how to write tests in MSTest for WinUI. But as new features are added to WinUI we can optionally write them in a more unit-testable way and add new tests here. Unit tests have the advantage of being quicker and more reliable that UI Interaction tests which is where we are getting most of the coverage now.
I've also updated the Azure Pipeline job to execute the unit tests as part of the build.
This PR updates the version of WinAppSDK from 1.4 to 1.5 Preview1. Once 1.5.0 stable is released we should update to that.