Test execution bugs in specific TFMs addressed.

[Haplois]

• Fixed test execution under net5+ TFMs.

• Fixed UWP test execution.

• Fixed MSTest V2 tests won't run when targeting net5.0-windows10.0.19041 #991

• Fixed Tests are ignored for OS version-specific TFMs #982

• Fixed MSTest.TestFramework 2.2.4: 'TestContext' does not contain a definition for 'TestRunDirectory' in net5.0-windows10.0.19041 project #851

• Fixed .NET 5 TFM Support? #750

Remarks

Sample	Type
PackagedAppTestSample.zip	Packaged Test
UnpackagedAppTestSample.zip	Unpackaged Test

From now on, WinUI packaged tests are required to specify UseWinUI property in *.csproj and set it true.

<PropertyGroup>
    <UseWinUI>true</UseWinUI>
</PropertyGroup>

Packaged apps

This blog post form @azchohfi is still current, just make sure you're using WinUI 1.0.0 or later.

Also, UseWinUI property needs to be specified.

Unpackaged apps

1. Create a packaged WinUI application.
2. Open .csproj file and add

    <ItemGroup>
        <ProjectCapability Include="TestContainer" />
    </ItemGroup>

    <PropertyGroup>
        <TestPlatformVersion>17.1.0-release-20220113-05</TestPlatformVersion>
        <MSTestVersion>5.0.30-dev</MSTestVersion>
        <GenerateProgramFile>false</GenerateProgramFile>
        <WindowsPackageType>None</WindowsPackageType>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.NET.Test.Sdk" Version="$(TestPlatformVersion)" />
        <PackageReference Include="MSTest.TestAdapter" Version="$(MSTestVersion)" />
        <PackageReference Include="MSTest.TestFramework" Version="$(MSTestVersion)" />
    </ItemGroup>

3. In .csproj file make sure you're referencing 1.0.1+ version of Microsoft.WindowsAppSDK package.
4. Add your test classes, if you need to run any tests in UI thread you need to specify this attribute in your test application

using Microsoft.VisualStudio.TestTools.UnitTesting.AppContainer;

[assembly: WinUITestTarget(typeof(App4.App))]

Building this branch to test

1. Open a terminal window at your source root
2. Run

.\scripts\Build.ps1 -FrameworkVersion "5.0.30" -AdapterVersion "5.0.30" 

# If a preview version of VS fails to compile you can instead run:
# .\scripts\Build.ps1 -FrameworkVersion "5.0.30" -AdapterVersion "5.0.30" -DisallowPrereleaseMSBuild

3. You should increment the version to bypass package cache when testing - also add ./artifacts/Debug/MSTestPackages/ to your nuget.config file.

[Scottj1s]

I'm concerned about false positives/negatives, as using WinUI is not equivalent to executing in a packaged app.

[Haplois]

@Scottj1s
I'm concerned about false positives/negatives, as using WinUI is not equivalent to executing in a packaged app.

Currently we only support packaged WinUI applications. I am experimenting with non packaged ones. I might amend this PR to include support this weekend.

[Scottj1s]

@Scottj1s
I'm concerned about false positives/negatives, as using WinUI is not equivalent to executing in a packaged app.

Currently we only support packaged WinUI applications. I am experimenting with non packaged ones. I might amend this PR to include support this weekend.

Sounds good. Also note that in addition to packaged non-WinUI apps, you can have an unpackaged WinUI app.

[Haplois]

Support for unpackaged-apps are also here. See PR description for details.

[Evangelink]

Could we add some integration test (probably the test case we used for manual testing).

[Evangelink]

A few nit comments - feel free to ignore them.

[dotMorten]

WinUI packaged tests are required to specify UseWinUI

looking over the code it seems it is more about testing packaged apps rather than testing WinUI, or am I missing something here?

[Haplois]

It also supports unpackaged apps, you can find a sample here. I'll also update the documentation.