PowerShell/test
Andrew Schwartzmeyer 3a43126a2e Allow creation of symlink to non-existent target
This action is completely valid on both Windows and Linux (and OS X)
operating systems; tested with `mklink` and `ln -s` respectively.

Note that targets for hard links must exist, thus we check specifically
for symbolic links.

Both the path globber in session state and the `New-Item` implementation
needed to be fixed to allow the target not to exist.

Resolves #801.

Also enable symbolic link tests on Windows.
2016-04-09 18:45:23 -07:00
..
csharp Fix whitespace in csharp/project.json 2016-04-08 21:58:05 -07:00
fullclr Run FullCLR sanitary tests in AppVeyor 2016-02-03 17:29:27 -08:00
powershell Allow creation of symlink to non-existent target 2016-04-09 18:45:23 -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.