dc9b4c595d
The latest xUnit packages fix the "could not resolve coreclr path" problem we were having. To resolve all dependencies, the cli-deps feed was replaced with the aspnet feeds. However, the latest xUnit packages do not allow us to set the default AssemblyLoadContext. |
||
|---|---|---|
| .. | ||
| fixture_AssemblyLoadContext.cs | ||
| project.json | ||
| README.md | ||
| test_Binders.cs | ||
| test_CorePsExtensions.cs | ||
| test_CorePsPlatform.cs | ||
| test_ExtensionMethods.cs | ||
| test_FileSystemProvider.cs | ||
| test_MshSnapinInfo.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.