PowerShell/test
Aditya Patwardhan 75ba74cce6
Merge pull request #7242 from daxian-dbw/exp
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
2018-07-12 15:52:04 -07:00
..
common/markdown Fix broken links due to PR 6899 that removed GitHub docs on installation docs, known issues and breaking changes due to complete migration to docs.microsoft.com (#6981) 2018-06-05 19:37:14 -07:00
csharp CodeFactor code style cleanup: replace literal empty strings with 'string.Empty' (#6950) 2018-06-12 12:30:10 -07:00
docker/networktest Update copyright and license headers (#6134) 2018-02-13 09:23:53 -08:00
hosting Add tests for PowerShell hosting API to verify MyGet packages (#6737) 2018-04-27 13:25:33 -07:00
packaging/windows Simplify the paths the MSI uses (#6442) 2018-04-02 10:47:29 -07:00
powershell Merge pull request #7242 from daxian-dbw/exp 2018-07-12 15:52:04 -07:00
shebang
tools Move to dotnet core 2.1.1 (#7161) 2018-06-28 23:10:10 -07:00
README.md
Test.Common.props Move to dotnet core 2.1.1 (#7161) 2018-06-28 23:10:10 -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.