microsoft
/
Xaml-Controls-Gallery
зеркало из https://github.com/microsoft/WinUI-Gallery.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
Xaml-Controls-Gallery/WinUIGalleryUnitTests/WinUIGalleryUnitTests.csproj

66 строки
3.0 KiB
XML
Исходник Постоянная ссылка Обычный вид История

Add a unit test project (#1444) 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>
2024-02-07 03:58:05 +03:00
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>$(SamplesTargetFrameworkMoniker)</TargetFramework>
Update to support submodule builds (#1498) WinUIGallery's dependencies now require latest SDKs, so should specify these regardless of how the project is built (standalone vs submodule). The unit test project was not setting standalone properties properly - factored out common directory.build.props. Added a workaround for conflicting build and publish deps.json files until WinAppSDK provides the fix.
2024-03-14 19:56:01 +03:00
<TargetPlatformVersion>$(WindowsSdkTargetPlatformVersion)</TargetPlatformVersion>
<TargetPlatformMinVersion>$(WindowsAppSdkTargetPlatformVersion)</TargetPlatformMinVersion>
Add a unit test project (#1444) 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>
2024-02-07 03:58:05 +03:00
<RootNamespace>WinUIGalleryUnitTests</RootNamespace>
<ApplicationManifest>app.manifest</ApplicationManifest>
<Platforms>x86;x64;ARM64</Platforms>
Update to WinAppSDK 1.5 and .NET8; PublishSingleFile for unpackaged configs; fix compile warnings (#1483)
2024-03-12 20:40:00 +03:00
<RuntimeIdentifiers>win-x86;win-x64;win-arm64</RuntimeIdentifiers>
Add a unit test project (#1444) 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>
2024-02-07 03:58:05 +03:00
<PublishProfile>win-$(Platform).pubxml</PublishProfile>
<UseWinUI>true</UseWinUI>
<EnableMsixTooling>true</EnableMsixTooling>
<ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles>
<SelfContained>true</SelfContained>
</PropertyGroup>
<ItemGroup>
<Page Remove="UnitTestApp.xaml" />
<ApplicationDefinition Include="UnitTestApp.xaml" />
<ProjectCapability Include="TestContainer" />
</ItemGroup>
<ItemGroup>
<Content Include="Assets\SplashScreen.scale-200.png" />
<Content Include="Assets\LockScreenLogo.scale-200.png" />
<Content Include="Assets\Square150x150Logo.scale-200.png" />
<Content Include="Assets\Square44x44Logo.scale-200.png" />
<Content Include="Assets\Square44x44Logo.targetsize-24_altform-unplated.png" />
<Content Include="Assets\StoreLogo.png" />
<Content Include="Assets\Wide310x150Logo.scale-200.png" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.WindowsAppSDK" Version="$(WindowsAppSdkPackageVersion)" />
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22621.756" />
<PackageReference Include="MSTest.TestAdapter" Version="3.1.1" />
<PackageReference Include="MSTest.TestFramework" Version="3.1.1" />
<PackageReference Include="Microsoft.TestPlatform.TestHost" Version="17.7.2">
<ExcludeAssets>build</ExcludeAssets>
</PackageReference>
<Manifest Include="$(ApplicationManifest)" />
</ItemGroup>
<!--
Defining the "Msix" ProjectCapability here allows the Single-project MSIX Packaging
Tools extension to be activated for this project even if the Windows App SDK Nuget
package has not yet been restored.
-->
<ItemGroup Condition="'$(DisableMsixProjectCapabilityAddedByProject)'!='true' and '$(EnableMsixTooling)'=='true'">
<ProjectCapability Include="Msix" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\WinUIGallery\WinUIGallery.csproj" />
</ItemGroup>
<!--
Defining the "HasPackageAndPublishMenuAddedByProject" property here allows the Solution
Explorer "Package and Publish" context menu entry to be enabled for this project even if
the Windows App SDK Nuget package has not yet been restored.
-->
<PropertyGroup Condition="'$(DisableHasPackageAndPublishMenuAddedByProject)'!='true' and '$(EnableMsixTooling)'=='true'">
<HasPackageAndPublishMenu>true</HasPackageAndPublishMenu>
</PropertyGroup>
</Project>