WindowsTerminal.UIA.Tests fail to run when launched from Visual Studio > Run Tests

[dmachaj]

Windows Terminal version

No response

Windows build number

10.0.22000.556

Other Software

Visual Studio 2022 (17.1.1)

Steps to reproduce

Build the solution
Right click WindowsTerminal.UI.Tests and Click "Run Tests"

Expected Behavior

The tests should run and pass

Actual Behavior

It fails to launch the private build of Terminal and instead a new OS-installed Termianl window pops up and displays an error.

[miniksa]

Hm this wasn't really defapp.

It's that this specific test doesn't work out of the VS UI. I had to set some assumptions into the test that are true on the build machines but not usually true locally.

For one, /p:WTPath=<path> has to be given to te.exe to say where the extracted complete package is that was staged. This is weird because on the build machine, I use a powershell script to unzip the APPX when CascadiaPackage project is done and then launch that. But I don't have that Powershell script as a part of the MSBuild steps so it can't happen from the VS UI.

Additionally, we need the big.txt content package which I believe I place with another Powershell script that isn't a part of the MSBuild steps.

So I could make this better for interactive local repro.