PowerShell/test
Dongbo Wang dc9b326587 Fix issue #1609 - Get-PSSession -computername fails on nano
Root cause: Microsoft.WSMan.Management  and  Microsoft.PowerShell.Commands.Diagnostics  are not put in the default snapin list for win-ops, and thus when a runspace is created using RunspaceConfiguration, those 2 are not loaded as snapins by default, which is a behavior change compared to Nano PS.
Fix: Replace the guard 'PORTABLE' to be 'UNIX' so that they are in the default snapin list when targeting windows platform.
2016-08-05 11:20:14 -07:00
..
csharp Update project.json files to keep sync with the new MMI nuget package 2016-07-28 17:07:57 -07:00
fullclr Update PowerShellGithubDev.Tests.ps1 2016-07-14 13:46:29 -07:00
powershell Fix issue #1609 - Get-PSSession -computername fails on nano 2016-08-05 11:20:14 -07:00
PSReadLine Update project.json files to keep sync with the new MMI nuget package 2016-07-28 17:07:57 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08: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.