PowerShell/test
Jason Shirk (POWERSHELL) 1913244fad Fix powershell -Command - handling of backspace
PowerShell can be started with input redirected in different scenarios.

`powershell -Command -` is one scenario where commands are sent to
PowerShell, but this is not a interactive shell scenario, it's really
a server to run commands from some other process.

`powershell -File -` or just regular redirected input means PowerShell
is an interactive shell, but command line editing must be done via
the redirected standard input handle instead of interacting directly
with a console handle.

In this scenario, we want to provide a good editing experience. Today,
we provide the bare minimum, supporting backspace but no cursor movement.

The bug here is that backspace was treated as a backspace in the server mode
but should not have been.
2016-09-21 15:01:33 -07:00
..
csharp spelling fixes: test 2016-08-25 17:49:32 +00:00
fullclr Update PowerShellGithubDev.Tests.ps1 2016-07-14 13:46:29 -07:00
powershell Fix powershell -Command - handling of backspace 2016-09-21 15:01:33 -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
tools/EchoArgs Rename Publish-EchoArgs to Publish-PSTestTools 2016-09-13 13:37:42 -07: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.