PowerShell/test/csharp
2016-07-28 17:07:57 -07:00
..
fixture_AssemblyLoadContext.cs Remove CoreConsoleHost from xUnit tests 2016-05-17 13:28:44 -07:00
project.json Update project.json files to keep sync with the new MMI nuget package 2016-07-28 17:07:57 -07:00
README.md Update test documentation 2016-04-04 19:20:26 -07:00
test_Binders.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00
test_CorePsExtensions.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00
test_CorePsPlatform.cs Rename IsCore to IsCoreCLR 2016-07-26 11:54:08 -07:00
test_ExtensionMethods.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00
test_FileSystemProvider.cs Remove CoreConsoleHost from xUnit tests 2016-05-17 13:28:44 -07:00
test_MshSnapinInfo.cs Re-enable checking of assemblies with strong names 2016-06-27 14:49:46 -07:00
test_PSVersionInfo.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00
test_Runspace.cs Temporarely skip 1 failing test 2016-06-10 17:03:49 +00:00
test_SecuritySupport.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00
test_SessionState.cs Remove CoreConsoleHost from xUnit tests 2016-05-17 13:28:44 -07:00
test_Utils.cs Add all classes to AssemblyLoadContext collection 2016-03-17 18:15:39 -07:00

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.