5717a5dffc
* add csproj ref to sln * Remove Microsoft.NET.Test.Sdk NuGet reference. The xunit.runner.visualstudio package is now sufficient for running tests in VS in the latest version (15.7.5) * use RTM versions of XUnit 2.4.0 that got published today * Update XUnit in hosting project as well to newer release |
||
|---|---|---|
| .. | ||
| 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.