PowerShell/test
jeffbi ce4c35b9ed Allow use of long paths (#3960)
When calling Windows native API to determine if an item exists,
ensure the path is prepended with "\\?\" when the path is a long path.

Fixes #3891
2017-06-07 17:13:51 -07:00
..
common/markdown Fix markdown lint issues for SSH Remoting demo and enable related tests (#3484) 2017-04-11 09:42:37 -07:00
csharp Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
docker/networktest Add dockerfile and test so we can test simple remoting behaviors (#3470) 2017-04-21 17:23:08 -07:00
fullclr Remove trailing whitespace (#3001) 2017-01-16 13:31:14 -08:00
powershell Allow use of long paths (#3960) 2017-06-07 17:13:51 -07:00
PSReadLine Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Fixed code coverage infrastructure and some failing tests (#3914) 2017-06-05 17:37:48 -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.