PowerShell/test
Travis Plunk cd9ddb156d Used method from PR comments to find powershell
replaced dir with get-childitem
used appropriate path when importing pester
verified failure count was 0
split test case verification into individual it's so we get all the info.
2016-07-20 16:28:33 -07:00
..
csharp Remove Platform.HasRegistry query 2016-07-14 17:34:12 -07:00
fullclr Update PowerShellGithubDev.Tests.ps1 2016-07-14 13:46:29 -07:00
powershell Used method from PR comments to find powershell 2016-07-20 16:28:33 -07:00
PSReadLine Update to .NET Core 1.0 packages 2016-06-27 15:30:47 -07:00
shebang
map.json Edit map.json to add in PackageManagement tests 2016-07-12 21:17:11 -07:00
README.md

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.