Skip to content

Fix 12 non-interactive failing Pester tests #324

Closed

Description

VSO create date - 11/5/2015 10:14:00

Activity

  1. andyleejordan commented on Jan 23, 2016

    @andyleejordan
    MemberAuthor

    I believe there are now 12 tests that fail due to lack of a TTY.

    We do not know how to fix this, it heavily involves the implementation of the PSHost (and its UserInterface and that's RawUserInterface).

  2. changed the title [-]Fix 7 non-interactive failing Pester tests[/-] [+]Fix 12 non-interactive failing Pester tests[/+] on Jan 23, 2016
  3. andyleejordan commented on Jan 23, 2016

    @andyleejordan
    MemberAuthor

    Jason Shirk (@lzybkr) perhaps you could help us out here. Do we need a "dumber" PSHost implementation specifically for the non-interactive use case? I had to tunnel through to our RawUserInterface in 9a5c010 to make our Pester tests run on AppVeyor.

    What do the Windows hosts do for this kind of thing?

  4. lzybkr commented on Jan 25, 2016

    @lzybkr
    Contributor

    I'm not sure how much help I can be w/o specifics, but I noticed one possible issue - new Size(0,0) seems like it has the potential to cause problems. I'm guess we need to assume a non-zero width somewhere to decide how to wrap lines or whatever.

  5. andyleejordan commented on Feb 3, 2016

    @andyleejordan
    MemberAuthor

    Jason Shirk (@lzybkr) You were on the right track! As soon as we were able to revert our use of WindowWidth/Height back to BufferWidth/Height, these tests all started passing. Hurray for .NET Core getting updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions