PowerShell/test
Steve Lee efbdea5cfe Fix importing remote module using version filters and added tests (#4900)
- Add tests for remote import-module
- Fix issue with remotely importing module where it was checking the version filter incorrectly against the proxy module
   - The filters are applied when importing the module remotely
   - After proxy module is generated it always has a module version of 1.0, so the filters will always fail when importing the proxy locally
2017-09-25 21:37:56 -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 Fix importing remote module using version filters and added tests (#4900) 2017-09-25 21:37:56 -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 Replace httpbin.org/delay Tests with WebListener (#4905) 2017-09-25 12:50:15 -07: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.