PowerShell/test
Travis Plunk d29349bb4d
Default to DefaultConsoleWidth when DotNet says WindowWidth is 0 (#7465)
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.
* Port changes from #6883 by @kalgiz
2018-08-07 15:27:42 -07:00
..
common/markdown Fix broken links due to PR 6899 that removed GitHub docs on installation docs, known issues and breaking changes due to complete migration to docs.microsoft.com (#6981) 2018-06-05 19:37:14 -07:00
csharp Add xunit project to PowerShell.sln and make it runable from within VisualStudio (#7254) 2018-08-02 11:51:04 -07:00
docker/networktest Update copyright and license headers (#6134) 2018-02-13 09:23:53 -08:00
hosting Add xunit project to PowerShell.sln and make it runable from within VisualStudio (#7254) 2018-08-02 11:51:04 -07:00
packaging/windows Simplify the paths the MSI uses (#6442) 2018-04-02 10:47:29 -07:00
powershell Default to DefaultConsoleWidth when DotNet says WindowWidth is 0 (#7465) 2018-08-07 15:27:42 -07:00
shebang
tools Make sure that SettingFile arg is parsed before we load the settings (#7449) 2018-08-07 15:01:31 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props update to latest package references, runtime framework, and SDK (#7272) 2018-07-13 09:00:35 +05:00

Testing

The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.