PowerShell/test
Jason Shirk cf18010ad5 Fix multi-line input w/ redirected stdin (#2090)
The input loop reading from stdin did not handle multi-line input correctly
because it was adding a newline character where none was expected.

The fix was to not include the final newline character to accept input,
just like Console.ReadLine or PSReadline would.
2016-08-31 13:52:46 -07:00
..
csharp Merge pull request #1669 from andschwa/safe-hostname 2016-08-08 11:10:53 -07:00
fullclr Update PowerShellGithubDev.Tests.ps1 2016-07-14 13:46:29 -07:00
powershell Fix multi-line input w/ redirected stdin (#2090) 2016-08-31 13:52:46 -07:00
PSReadLine Add Ubuntu 16.04 RID 2016-08-05 10:09:40 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
map.json Edit map.json to add in PackageManagement tests 2016-07-12 21:17:11 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07: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.