PowerShell/test
kwkam fbfbb4f005 [Feature] Fix Move-Item -Path with wildcard char (#7397)
Unescape non-literal, non-glob path in ProccessRecord and
set the context.SuppressWildcardExpansion in RenameItem.
This solve the issue where Rename-Item complains -Path does not exist
when both -Path and CWD contains special characters.
2018-08-05 17:31:06 +05: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 Add xunit project to PowerShell.sln and make it runable from within VisualStudio (#7254) 2018-08-02 11:51:04 -07:00
docker/networktest Update copyright and license headers (#6134) 2018-02-13 09:23:53 -08:00
hosting Add xunit project to PowerShell.sln and make it runable from within VisualStudio (#7254) 2018-08-02 11:51:04 -07:00
packaging/windows Simplify the paths the MSI uses (#6442) 2018-04-02 10:47:29 -07:00
powershell [Feature] Fix Move-Item -Path with wildcard char (#7397) 2018-08-05 17:31:06 +05:00
shebang
tools Update CI scripts to support running tests for experimental features (#7419) 2018-08-03 11:20:14 -07:00
README.md
Test.Common.props update to latest package references, runtime framework, and SDK (#7272) 2018-07-13 09:00:35 +05: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.