You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I start the WindowsTerminal.UIA.Tests by Visual Studio Test Explorer, but it fail when I run the "smoke test".
Here is the output :
*********** StartTerminal - Test Start ***********
Property [Architecture] = x64
Property [TaefTestType] = Managed
Property [IsPGO] = true
Windows Terminal will be launched from '.src\cascadia\CascadiaPackage\bin\x64\Debug\terminal-0.0.1.0\WindowsTerminal.exe'
Test Content will be loaded from 'D:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\content'
IsNotNull(System.IntPtr) - Creating job object to hold binaries under test.
Attempting to launch command-line application at '.\src\cascadia\CascadiaPackage\bin\x64\Debug\terminal-0.0.1.0\WindowsTerminal.exe'
IsTrue - Attempting to create child host window process.
Host window PID: 21100
IsTrue - Assigning new host window (suspended) to job object.
IsTrue - Resume host window process now that it is attached and its launch of the child application will be caught in the job object.
IsNotNull(OpenQA.Selenium.Appium.iOS.IOSDriver1[OpenQA.Selenium.Appium.iOS.IOSElement]) IsNotNull(OpenQA.Selenium.Appium.iOS.IOSDriver1[OpenQA.Selenium.Appium.iOS.IOSElement])
System.InvalidOperationException: An unknown error occurred in the remote end while processing the command.
在 OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
在 OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
在 OpenQA.Selenium.Remote.RemoteWebElement.SendKeys(String text)
在 WindowsTerminal.UIA.Tests.SmokeTests.StartTerminal() 位置 .\src\cascadia\WindowsTerminal_UIATests\SmokeTests.cs:行号 29
*********** StartTerminal - Test Failed ***********
I think the problem is the function TerminalApp( .\src\cascadia\WindowsTerminal_UIATests\Elements\TerminalApp.cs-> TerminalApp(TestContext context, string shellToLaunch = "WindowsTerminal.exe") ) can not start successfully .
The comment mentions: "If running locally, set WTPath to where we can find a loose deployment of Windows Terminal. That means you'll need to build the Terminal appx, then use New-UnpackagedTerminalDistribution.ps1 to build an unpackaged layout that can successfully launch. Then, point the tests at that WindowsTerminal.exe"
However, I cannot successfully launch Windows Terminal after building with New-UnpackagedTerminalDistribution.ps1, whether by double-clicking or using PowerShell to open it. So I believe it also fails to launch successfully in the smoke test, causing the UIA.Test to fail.
Therefore, my question is: How should WindowsTerminal.UIA.Tests pass in Visual Studio Test Explorer? If possible, what should I do? Should I deploy a locally runnable WindowsTerminal as mentioned in #926, or are there other methods to pass WindowsTerminal.UIA.Tests?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I start the WindowsTerminal.UIA.Tests by Visual Studio Test Explorer, but it fail when I run the "smoke test".
Here is the output :
I think the problem is the function TerminalApp( .\src\cascadia\WindowsTerminal_UIATests\Elements\TerminalApp.cs-> TerminalApp(TestContext context, string shellToLaunch = "WindowsTerminal.exe") ) can not start successfully .
The comment mentions: "If running locally, set WTPath to where we can find a loose deployment of Windows Terminal. That means you'll need to build the Terminal appx, then use New-UnpackagedTerminalDistribution.ps1 to build an unpackaged layout that can successfully launch. Then, point the tests at that WindowsTerminal.exe"
However, I cannot successfully launch Windows Terminal after building with New-UnpackagedTerminalDistribution.ps1, whether by double-clicking or using PowerShell to open it. So I believe it also fails to launch successfully in the smoke test, causing the UIA.Test to fail.
Therefore, my question is: How should WindowsTerminal.UIA.Tests pass in Visual Studio Test Explorer? If possible, what should I do? Should I deploy a locally runnable WindowsTerminal as mentioned in #926, or are there other methods to pass WindowsTerminal.UIA.Tests?
Beta Was this translation helpful? Give feedback.
All reactions