PowerShell/test
James Truher [MSFT] 0d1e1919f2 Improve test coverage for CDXML cmdlet infrastructure (#4537)
Create custom CIM classes (via MOF) and CDXML cmdlets against the new CIM class
Create tests for CRUD operations for CDXML cmdlets
Coverage for Microsoft.PowerShell.Cmdletization namespace is nearly 50%
2017-08-16 16:33:53 -07:00
..
common/markdown Get macOS working and fix misc issue 2017-07-25 17:55:42 -07:00
csharp Move powershell to 2.0.0-preview3-25426-01 using the .NET CLI 2.0.0-preview2-006502 (#4144) 2017-06-30 13:07:14 -07:00
docker/networktest PSScriptAnalyzer fixes by category (#4261) 2017-07-21 21:03:49 -07:00
powershell Improve test coverage for CDXML cmdlet infrastructure (#4537) 2017-08-16 16:33:53 -07:00
PSReadLine Move powershell to 2.0.0-preview3-25426-01 using the .NET CLI 2.0.0-preview2-006502 (#4144) 2017-06-30 13:07:14 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Opencover and Code coverage improvements (#4550) 2017-08-14 10:40:11 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Move powershell to 2.0.0-preview3-25426-01 using the .NET CLI 2.0.0-preview2-006502 (#4144) 2017-06-30 13:07:14 -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.