PowerShell/test/xUnit
2021-07-07 09:33:19 +05:00
..
Asserts Enable CA1050: Declare types in namespaces (#13872) 2020-10-26 22:34:26 +05:00
csharp Enable IDE0044: MakeFieldReadonly (#13880) 2021-07-07 09:33:19 +05:00
README.md Fix broken urls (#8653) 2019-01-15 16:20:45 -08:00
xunit.runner.json Make xUnit tests run sequentially to avoid race conditions caused by manipulating 'powershell.config.json' in tests (#8945) 2019-02-22 11:57:10 -08:00
xUnit.tests.csproj Bump Microsoft.NET.Test.Sdk from 16.9.4 to 16.10.0 (#15458) 2021-06-07 13:56:19 -07:00

xUnit Tests

The folder contains xUnit tests for PowerShell Core project.

Running xUnit Tests

Go to the top level of the PowerShell repository and run full set of tests: Start-PSxUnit inside a self-hosted copy of PowerShell.

Go to the test project folder and run dotnet test -c Release.

Use filter parameter to run only needed tests:

dotnet test -c Release --filter "FullyQualifiedName~UnitTest1   # Runs tests which have UnitTest1 in FullyQualifiedName
dotnet test --filter Name~TestMethod1   # Runs tests whose name contains TestMethod1

Creating xUnit Tests

Keep the folder structure that is for Pester ../../test/powershell and C# files ../../src.

Use namespace names started with PSTests.

namespace PSTests.YourNameSpace
{
}