PowerShell/test
Sergey Vasin 1be0594f45 Improve code coverage in Export-Csv.Tests.ps1. (#6795)
* Improve code coverage in Export-Csv.Tests.ps1.

* Change test logic.
2018-05-04 09:46:26 -07:00
..
common/markdown Remove extraneous SSH and install docs from the 'demos' folder (#6628) 2018-04-13 15:50:54 -07:00
csharp Update PowerShell to build with .NET Core SDK 2.1.300-rc1-008662 (#6718) 2018-05-02 16:58:39 -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 Improve code coverage in Export-Csv.Tests.ps1. (#6795) 2018-05-04 09:46:26 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Update PowerShell to build with .NET Core SDK 2.1.300-rc1-008662 (#6718) 2018-05-02 16:58:39 -07:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Update PowerShell to build with .NET Core SDK 2.1.300-rc1-008662 (#6718) 2018-05-02 16:58:39 -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.