PowerShell/test
Steve Lee a9d10dda42 Fix two tests that are failing on nightly run (#6723)
- For ConsoleHosts tests, the test is validating error condition, but did not redirect stderr to stdout so the output isn't captured and thus an empty string failing the assertion.
- For SSHConnectionInfo API tests, it's calling a constructor that got overwritten with a new parameter. Fix is to put back that public API and overload it with a new one.
2018-04-24 16:25:55 -07:00
..
common/markdown Remove extraneous SSH and install docs from the 'demos' folder (#6628) 2018-04-13 15:50:54 -07:00
csharp Update copyright and license headers (#6134) 2018-02-13 09:23:53 -08:00
docker/networktest Update copyright and license headers (#6134) 2018-02-13 09:23:53 -08:00
packaging/windows Simplify the paths the MSI uses (#6442) 2018-04-02 10:47:29 -07:00
powershell Fix two tests that are failing on nightly run (#6723) 2018-04-24 16:25:55 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Add PowerShell logging tests for macOS and Linux (#6025) 2018-03-29 14:46:08 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Update to DotNet 2.0.6 (#6403) 2018-03-15 14:54:00 -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.