5dc7a6cb07
To support PowerShell modules built with .NET Windows Compatibility Pack, we decided that it was best to ship the WCP assemblies with PS Core. This also adds many new .NET APIs be default while only adding ~3.5 MB additional disk footprint (to a ~137 MB install currently). Also update the build to adopt the official .NET Core 2.1. |
||
|---|---|---|
| .. | ||
| csharp.tests.csproj | ||
| README.md | ||
| test_Binders.cs | ||
| test_CorePsPlatform.cs | ||
| test_ExtensionMethods.cs | ||
| test_FileSystemProvider.cs | ||
| test_MshSnapinInfo.cs | ||
| test_PSConfiguration.cs | ||
| test_PSVersionInfo.cs | ||
| test_Runspace.cs | ||
| test_SecuritySupport.cs | ||
| test_SessionState.cs | ||
| test_Utils.cs | ||
xUnit Tests
These tests are completely Linux specific.
Every test class must belong to
[Collection("AssemblyLoadContext")]. This ensures that PowerShell's
AssemblyLoadContext is initialized before any other code is executed.
When this is not the case, late initialization fails with
System.InvalidOperationException : Binding model is already locked for the AppDomain and cannot be reset.
Having every class in the same collection is as close to an xUnit global init hook as can be done.
Running xUnit Tests
Go to the top level of the PowerShell repository and run:
Start-PSxUnit inside a self-hosted copy of PowerShell.