Bumps [XunitXml.TestLogger](https://github.com/spekt/xunit.testlogger) from 2.1.45 to 3.0.56. - [Release notes](https://github.com/spekt/xunit.testlogger/releases) - [Changelog](https://github.com/spekt/xunit.testlogger/blob/master/CHANGELOG.md) - [Commits](https://github.com/spekt/xunit.testlogger/compare/v2.1.45...v3.0.56) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> |
||
---|---|---|
.. | ||
Asserts | ||
csharp | ||
README.md | ||
xunit.runner.json | ||
xUnit.tests.csproj |
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
{
}