Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default to DefaultConsoleWidth when DotNet says WindowWidth is 0 #7465

Merged
merged 5 commits into from
Aug 7, 2018

Conversation

TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Aug 6, 2018

PR Summary

Default to DefaultConsoleWidth when DotNet says WindowWidth is 0

This resolves an issue in an environment like VSTS when pwsh is spawned and DotNet is not able to determine the Console Width.

PR Checklist

@iSazonov
Copy link
Collaborator

iSazonov commented Aug 7, 2018

@TravisEz13 Please look #6883 - could we move commits from #6883 to the PR?

@TravisEz13
Copy link
Member Author

@iSazonov I knew I saw this before, thanks

@@ -1387,12 +1387,16 @@ public static class InternalTestHooks
// Simulate 'System.Diagnostics.Stopwatch.IsHighResolution is false' to test Get-Uptime throw
internal static bool StopwatchIsNotHighResolution;
internal static bool DisableGACLoading;
internal static bool SetConsoleWidthToZero;
<<<<<<< HEAD
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merge headers are left here.

# Fill the console window with the string, so that it reaches its max width.
# Check if the max width is equal to default value (120), to test test hook set.
$testObject = @{ test = '1' * 200}
Format-table -inputobject $testObject | Out-String -Stream | ForEach-Object{$_.length} | Sort-Object | Select-Object -Last 1 | Should -Be 120
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use

Format-table -inputobject $testObject | Out-String -Stream | ForEach-Object{$_.length} | Sort-Object -Bottom 1

# Check if the max width is equal to default value (120), to test test hook set.
$testObject = @{ test = '1' * 200}
Format-table -inputobject $testObject | Out-String -Stream | ForEach-Object{$_.length} | Sort-Object | Select-Object -Last 1 | Should -Be 120
Format-Table -inputobject $testObject | Should -Not -BeNullOrEmpty
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No needed i guess

@adityapatwardhan
Copy link
Member

@TravisEz13 There seems to be a new CodeFactor issue. Can you have a look.

@TravisEz13
Copy link
Member Author

The CodeFactor issue is basically an existing design issue around the test hooks

@TravisEz13 TravisEz13 merged commit d29349b into PowerShell:master Aug 7, 2018
@TravisEz13 TravisEz13 deleted the fix_vsts_subprocess_issue branch August 7, 2018 22:27
@iSazonov
Copy link
Collaborator

iSazonov commented Aug 8, 2018

We have test\tools\Modules\HelpersHostCS\ - can we use it or we need a test system console?

@TravisEz13
Copy link
Member Author

We would have to have something that allows us to mock System.Console

@iSazonov
Copy link
Collaborator

I found related discussion https://stackoverflow.com/questions/5852862/mocking-system-console-behaviour
There is a link to https://blogs.msdn.microsoft.com/ploeh/2006/10/21/console-unit-testing/

[console]::SetOut looks interesting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants