PowerShell/test
Staffan Gustafsson fa901b646f Add ErrorMessage property to ValidatePattern, ValidateSet and ValidateScript attributes (#2728)
This makes it possibe to write for example
[ValidatePattern('[A-Z]:',  ErrorMessage='The Drive should be specified as a single letter followed by a colon, for example "D:"')]
[string] $Drive,

The element being validated is also passed, so {0} can be used in the custom error message
2017-04-20 11:31:57 -07:00
..
common/markdown Fix markdown lint issues for SSH Remoting demo and enable related tests (#3484) 2017-04-11 09:42:37 -07:00
csharp Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
fullclr Remove trailing whitespace (#3001) 2017-01-16 13:31:14 -08:00
powershell Add ErrorMessage property to ValidatePattern, ValidateSet and ValidateScript attributes (#2728) 2017-04-20 11:31:57 -07:00
PSReadLine Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -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.