PowerShell/test
Steve Lee 99e3fe586e Enable transcription of native commands on non-Windows (#4871)
Transcription was relying on reading the screen buffer to record output from native commands.
This resulted in an unhandled exception calling an unimplemented API on non-Windows.
The fix is to use redirected output/error if reading the screen buffer is not supported.
We check whether screen scraping is supported or not only when the application is running standalone.
2017-09-28 17:15:37 -07:00
..
common/markdown Update docs about the pull-request-process (#4710) 2017-09-04 10:29:20 -07:00
csharp Build powershell core using the generic RID 'linux-x64' (#4841) 2017-09-18 09:31:07 -07:00
docker/networktest PSScriptAnalyzer fixes by category (#4261) 2017-07-21 21:03:49 -07:00
powershell Enable transcription of native commands on non-Windows (#4871) 2017-09-28 17:15:37 -07:00
PSReadLine Build powershell core using the generic RID 'linux-x64' (#4841) 2017-09-18 09:31:07 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Add source files for coverage run (#4925) 2017-09-27 15:36:21 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Move to the official .NET Core 2.0 (#4603) 2017-08-16 17:32:46 -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.