Skip to content

Re-enable TerminalApp tests SettingsTests and TabsTests #1210

Closed

Description

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.

Activity

  1. added
    Issue-TaskIt's a feature request, but it doesn't really need a major design.
    Area-CodeHealthIssues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
    on Jun 11, 2019
  2. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Jun 11, 2019
  3. zadjii-msft commented on Jul 25, 2019

    @zadjii-msft
    MemberAuthor

    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.

  4. ghost added
    In-PRThis issue has a related PR
    on Aug 6, 2019
  5. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Aug 13, 2019
  6. ghost removed
    In-PRThis issue has a related PR
    on Aug 13, 2019
  7. ghost added
    Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.
    on Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-CodeHealthIssues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.Issue-TaskIt's a feature request, but it doesn't really need a major design.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions