History

Steve Lee e64e68bcdc Allow passing $true/$false as parameter to script using -File (#4178 ) Using powershell.exe to execute a PowerShell script using -File currently provides no way to pass $true/$false as parameter values. Current behavior is that -File accumulates passed parameters as strings only. Fix is to special case this based on discussion with PS-Committee to support $true/$false as parsed values to parameters. Switch values is also supported as currently documented syntax doesn't work.		2017-08-01 14:41:31 -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
fullclr	Due to the use of unsupported APIs, we must remove the LocalAccounts module until a better solution is found. (#4302 )	2017-07-19 17:20:35 -07:00
powershell	Allow passing $true/$false as parameter to script using -File (#4178 )	2017-08-01 14:41:31 -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	PSScriptAnalyzer fixes by category (#4261 )	2017-07-21 21:03:49 -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.