75ba74cce6
Add support to experimental features RFC: https://github.com/PowerShell/PowerShell-RFC/pull/114 Goals: Allow experimental features to be declared by PowerShell engine and modules. Allow experimental features to be enabled via powershell.config.json Allow Function, Cmdlet, parameters and parameter sets to be shown to the user or hiden from the user depending on whether the associated experimetnal feature is on or off. Allow discover experimental features using cmdlet Get-ExperimentalFeature |
||
---|---|---|
.. | ||
common/markdown | ||
csharp | ||
docker/networktest | ||
hosting | ||
packaging/windows | ||
powershell | ||
shebang | ||
tools | ||
README.md | ||
Test.Common.props |
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.