UI Tests don't allow for WinUI 2/3 dependencies

[Arlodotexe]

Background

In #132, we gave Lab libraries the ability to declare dependencies under UWP, WinAppSdk and Uno under both WinUI 2 and 3.

The problem

However, we didn't provide a way for test projects to declare dependencies the same way. This means that if a test project needs a nuget package that uses WinUI, they would need to add it to their lab source project, even if that project never used it.

The solution

Allow UI test projects to include WinUI 2/3 dependencies in the same way as #132 did.

[michael-hawker]

Right now the tests include the toolkit at least in the props files here:

Labs-Windows/tests/Labs.Tests.Uwp.props

Line 12 in beda030

<PackageReference Include="Microsoft.Toolkit.Uwp.UI" Version="7.1.2"/>

and here:

Labs-Windows/tests/Labs.Tests.WinAppSdk.props

Line 10 in beda030

<PackageReference Include="CommunityToolkit.WinUI.UI" Version="7.1.2"/>

You're saying to generalize this for other libraries as well?

One difference between the source library change with #132 and the tests though, is the tests right now only target UWP or WinUI 3, so we don't have as tough a time in this space to differentiate between them (at least at the moment) as there's no overlapping uno targets.

[Arlodotexe]

Interesting, I hadn't noticed this when I tried using .FindDescendant() earlier. I suppose this is a non-issue then, closing for now 😄

[michael-hawker]

@Arlodotexe yeah, the only thing would be if there's a case where something needs to be pulled in for testing, but feel that's more likely in the samples for #165 than for tests. Ideally everyone's just using the infrastructure we have in place, or grabbing things through the source library.

We can see how it goes and always re-evaluate and open this up later.

It'll get easier once we ship an 8.0 package as well to unify things (at least in the Toolkit dependency side).