PowerShell/test
jeffbi bbba61c1f5 Update Get-ComputerInfo test to properly test DeviceGuard items. (#3339)
* Make Get-ComputerInfo tests handle the case of the root\Microsoft\Windows\DeviceGuard namespace not found on the test machine.

Catch CIM exceptions, but don't look specifically for namespace-not-found

* Update Get-ComputerInfo test to properly test DeviceGuard items.
2017-03-17 16:31:21 -07:00
..
csharp Add OpenSUSE 13.2 build support (#3254) 2017-03-06 17:30:14 -08:00
fullclr Remove trailing whitespace (#3001) 2017-01-16 13:31:14 -08:00
powershell Update Get-ComputerInfo test to properly test DeviceGuard items. (#3339) 2017-03-17 16:31:21 -07:00
PSReadLine Add OpenSUSE 13.2 build support (#3254) 2017-03-06 17:30:14 -08:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools corrected use of PSModulePath casing to be consistent with Windows PowerShell (#3255) 2017-03-15 12:04:28 -07:00
vs-csproj Add '<Link>' tag to '<Compile>', '<None>' and '<EmbeddedResource>' tags to make those items look similar as when the *.csproj files were in the original project folders. (#2519) 2016-10-21 17:04:05 -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.