PowerShell/test
Mark Kraus a8e8b1f8e4 Change UserAgent App WindowsPowerShell -> PowerShell (#4914)
* Change UserAgent App WindowsPowerShell -> PowerShell

* [Feature] Run Feature tests

* [feature] Address PR Feedback with more precise assertion

* [feature] Address PR Feedback and add PSUserAgent Test

* [feature] add tag to describe block

* [feature] Remove describe block Add pattern to User-Agent specific tests

* [feature] Address PF Feedback

Remove all assertions for User-Agent that are not specifically about the User-Agent header.

* [feature] Match -> MatchExactly
2017-09-27 07:44:20 -07:00
..
common/markdown Update docs about the pull-request-process (#4710) 2017-09-04 10:29:20 -07:00
csharp Build powershell core using the generic RID 'linux-x64' (#4841) 2017-09-18 09:31:07 -07:00
docker/networktest PSScriptAnalyzer fixes by category (#4261) 2017-07-21 21:03:49 -07:00
powershell Change UserAgent App WindowsPowerShell -> PowerShell (#4914) 2017-09-27 07:44:20 -07:00
PSReadLine Build powershell core using the generic RID 'linux-x64' (#4841) 2017-09-18 09:31:07 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools [feature] Fix TestValue to avoid double // in Urls (#4920) 2017-09-26 09:05:55 +04:00
README.md Add test/README.md 2016-03-30 23:30:26 -07:00
Test.Common.props Move to the official .NET Core 2.0 (#4603) 2017-08-16 17:32:46 -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.