Re-enable TerminalApp tests SettingsTests and TabsTests #1609

Closed
opened 2026-01-30 22:31:54 +00:00 by claunia · 1 comment
Owner

Originally created by @zadjii-msft on GitHub (Jun 11, 2019).

This is a follow up from #1164.

Right now our CI isn't running a windows version high enough to be able to run these tests, so they're commented out.

Once #1012 is checked in, we can re-enable those tests.

Originally created by @zadjii-msft on GitHub (Jun 11, 2019). This is a follow up from #1164. Right now our CI isn't running a windows version high enough to be able to run these tests, so they're commented out. Once #1012 is checked in, we can re-enable those tests.
Author
Owner

@zadjii-msft commented on GitHub (Jul 25, 2019):

We might be able to re-enable the SettingsTests without re-enabling the TabTests. The TabTests rely on XAML Islands, which isn't supported on the build machines. the TabTests require deploying a appx on the test machine, but we can't just skip the test if the build machine isn't a high enough version.

However, since the SettingsTests only rely on SxS activation, we might be able to check the version in the CLASS_SETUP, and skip the test if the machine isn't the right version.

@zadjii-msft commented on GitHub (Jul 25, 2019): We might be able to re-enable the SettingsTests without re-enabling the TabTests. The TabTests rely on XAML Islands, which isn't supported on the build machines. the TabTests require deploying a appx on the test machine, but we can't just skip the test if the build machine isn't a high enough version. However, since the SettingsTests only rely on SxS activation, we might be able to check the version in the CLASS_SETUP, and skip the test if the machine isn't the right version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1609