PowerShell/test
Dongbo Wang d261e1f166
Move group policy settings and enable policy controlled logging in PowerShell Core (#5791)
Make PowerShell Core reads group policy settings from different registry keys (Windows only) and the configuration files (both Windows and Unix).
- On Windows, move to different GPO registry keys.
- On both Windows and Unix, read GPO related settings from the configuration file `powershell.config.json`.
- On Windows, the policy settings in registry take precedence over the configuration file.
- Enable policy controlled logging and transcription on Unix.
2018-01-08 12:03:23 -08:00
..
common/markdown Make the experience better when start-pspester doesn't find pester (#5673) 2017-12-12 16:07:12 -08:00
csharp Rename 'PowerShellProperties.json' to 'powershell.config.json' 2018-01-05 16:06:36 -08:00
docker/networktest Rename powershell.exe to pwsh.exe (#5101) 2017-10-17 17:25:11 -07:00
powershell Move group policy settings and enable policy controlled logging in PowerShell Core (#5791) 2018-01-08 12:03:23 -08:00
PSReadLine replace the word hang with something more appropriate (#5358) 2017-11-08 13:47:12 -08:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Replace Remaining HttpBin.org Tests with WebListener (#5665) 2017-12-13 19:28:05 +04:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Update PowerShell to build with .NET Core runtime 2.0.4 (#5677) 2017-12-12 13:53:22 -08: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.