mirror of https://github.com/PowerShell/PowerShell synced 2026-06-08 12:12:50 +00:00

Files

T

Ilya dc76c86f7a ValidateSetAttribute enhancement: support set values to be dynamically generated from a custom ValidateSetValueGenerator (#3784 )

Currently `ValidateSetAttribute` accepts only explicit constants as valid values. This is a significant limitation. Sometimes we need to get valid values dynamically, ex., Azure VMs, logged-on users and so on. The PR add follow possibilities:
- pass a _custom type_ (a valid values generator) implementing `IValidateSetValuesGenerator` interface to get valid values dynamically.
- pass a _custom type_ (a valid values generator) derived from `CachedValidValuesGeneratorBase` abstract class to get valid values dynamically and _cache_ the list to share with other ValidateSetAttribute attributes.

2017-07-13 21:28:32 -07:00

common/markdown

Fix maintainer readme syntax (#4226 )

2017-07-11 16:15:11 -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

Add dockerfile and test so we can test simple remoting behaviors (#3470 )

2017-04-21 17:23:08 -07:00

fullclr

Remove trailing whitespace (#3001 )

2017-01-16 13:31:14 -08:00

powershell

ValidateSetAttribute enhancement: support set values to be dynamically generated from a custom ValidateSetValueGenerator (#3784 )

2017-07-13 21:28:32 -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

Updated Code Coverage badge and filtered out PSReadline module (#4121 )

2017-07-07 09:29:23 -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

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

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.