PowerShell/test
Andrew Schwartzmeyer 7e65fa448e Mark as pending Travis CI OS X failing tests
These tests *do not* fail locally, nor on the Linux test runner. They do
not fail when accessing the OS X runner under debug mode. The *only*
cause is the lack of a TTY on the OS X runner, which is a Travis CI
regression. Moreover, the formatting tests do not fail when the TTY is
removed locally.

These absolutely should be fixed at some point, but it is not worth
spending any more time on it.
2016-05-17 13:28:44 -07:00
..
csharp Remove platform tests 2016-05-17 13:28:44 -07:00
fullclr Run FullCLR sanitary tests in AppVeyor 2016-02-03 17:29:27 -08:00
powershell Mark as pending Travis CI OS X failing tests 2016-05-17 13:28:44 -07:00
PSReadLine Remove CaptureScreen binding 2016-04-28 11:00:40 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08: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.