- Basic/App-with-error-output -- fixed (again)
- Basic/App-with-error-output -- the old behaviour comes back
- Basic/App-with-error-output -- fixed (again)
- Basic/String-equality-operators
--
'ae' -ceq 'æ'gets true.
- Basic/App-with-error-output -- the old behaviour comes back
- Basic/App-with-error-output -- fixed standard errors causing PowerShell errors
Set-Location -LiteralPath fails on odd paths, e.g. with brackets.
Weird, it works in demo scripts but fails in batch tests.
The following tests are disabled for v7:
- Cmdlets\Get-Item\Directory-with-brackets
- Cmdlets\Remove-Item\Directory-with-brackets
- Cmdlets\Set-Content\Directory-with-brackets
- Cmdlets\Start-Process
- Cmdlets\Test-Path\Incorrect-in-odd-location
- Basic/Strict-mode-ErrorRecord-formatting -- fixed regression v7.0.0-rc.1
- Basic/Strict-mode-ErrorRecord-formatting -- started to fail again, was fixed in v6 - v7.0.0-preview.6
- Cmdlets/ConvertFrom-Json/Not-unrolled-result -- The result is unrolled, "more expected"
- PowerShell.exe/Exit-code-0-with-Command-syntax-error -- exit code is 1 as usual but there is no error message printed
- Basic/Missing-ternary-operator -- PowerShell introduces the ternary operator
- Basic/Invocation-with-odd-paths -- Some fixes or changes
- Basic/Provider-specific-Filter -- Changed as it was before v6
- Group-Object/Expression-with-no-value -- Fixed
- Basic/FormatEnumerationLimit -- Different representation of truncated outputs.
- Test-Path/Incorrect-in-odd-location -- Fixed
- Basic/Provider-specific-Filter
-- Changed,
*.*works more like PowerShell wildcard. - Get-Item/Directory-with-brackets -- Fixed
- Remove-Item/Directory-with-brackets -- Fixed
- Test-Path/Incorrect-in-odd-location -- Fixed
- Get-ChildItem/Directory-with-backticks -- Regression, it worked better in v6.1.0-preview.3
- Group-Object/AsHashTable -- Fixed Test-2.expression.string.ps1
- Count-and-Length/PSCustomObject -- Fixed
- Number-of-returned-objects
-- Fixed for
PSCustomObject, same as above - Get-ChildItem/Directory-with-backticks
--
Get-ChildItemdoes not fail in the empty directory but still fails in not empty - Get-ChildItem/v5-LiteralPath-Recurse-ignores-Include -- Fixed the v5 regression
- PowerShell.exe/Unexpected-start-location -- Fixed
- Strict-mode-ErrorRecord-formatting -- Fixed
- PowerShell.exe/Not-current-version -- The trap is back due to the renamed powershell.exe to pwsh.exe
- PowerShell.exe/Version-parameter
-- Anything after
-Versionis silently ignored.
- PowerShell.exe/Not-current-version -- Fixed the v6 specific issue (Example 2, Not-same-exe.ps1)
- PowerShell.exe/Version-parameter
--
-Versionhas different meaning in v6 (revealed in this update). - PowerShell.exe/Version-scriptblock-host-problem
--
-Versionhas different meaning in v6 (revealed in this update).
- PowerShell.exe/Switch-parameter-with-value -- Allow passing $true/$false as a parameter to scripts using powershell.exe -File
- PowerShell.exe/Positional-Command-File
-- Breaking change: Change positional parameter from
-Commandto-File
- Basic/DynamicParam/ExpectingInput-is-false -- Fixed
- Basic/Properties-of-XmlNode -- Fixed "Adapted properties accept only string values"
- Cmdlets/ConvertFrom-Json/v6-long-integers
-- Integers are returned as
[long], not[int] - Cmdlets/ConvertTo-Json/Array-as-PSObject -- Fixed
- PowerShell.exe/Not-current-version -- Minor traps on playing with v6 on Windows