PowerShell/test
Steve Lee 40446c80a7 Support Link Header pagination in WebCmdlets (#3828)
* Support Link Header pagination in WebCmdlets to make it easier for the end user implementing:
https://github.com/PowerShell/PowerShell-RFC/blob/master/2-Draft-Accepted/RFC0021-Link-header-based-pagination-for-WebCmdlets.md

When the response includes a Link Header (https://tools.ietf.org/html/rfc5988#page-6), for Invoke-WebRequest we
create a RelationLink property that is a Dictionary representing the URLs and rel attributes and ensure the
URLs are absolute to make it easier for the developer to use.  For Invoke-RestMethod, we expose a -FollowRelLink
switch to automatically follow 'next' rel links to the end until we hit the optional -MaxRelLink parameter value.

* removed unnecessary refs to namespaces

* addressed code review feedback
2017-05-24 15:54:02 -07:00
..
common/markdown Fix markdown lint issues for SSH Remoting demo and enable related tests (#3484) 2017-04-11 09:42:37 -07:00
csharp Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
docker/networktest Add dockerfile and test so we can test simple remoting behaviors (#3470) 2017-04-21 17:23:08 -07:00
fullclr Remove trailing whitespace (#3001) 2017-01-16 13:31:14 -08:00
powershell Support Link Header pagination in WebCmdlets (#3828) 2017-05-24 15:54:02 -07:00
PSReadLine Move powershell to .NET Core 2.0 (#3556) 2017-04-17 11:52:38 -07:00
shebang Reorganize tests 2016-01-14 17:00:06 -08:00
tools Support Link Header pagination in WebCmdlets (#3828) 2017-05-24 15:54:02 -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

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.