Skip to content
.NET

New major version - v1, which targets XUnit v3. #35

Sign in to view logs

New major version - v1, which targets XUnit v3.

New major version - v1, which targets XUnit v3. #35

Triggered via pull request June 19, 2025 10:35
@christophergunnchristophergunn
opened #23
update-to-xunit-v3
Status Success
Total duration 28s
Artifacts –

dotnet.yml

on: pull_request
build
22s
build
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L234
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L121
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L132
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L91
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L76
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L91
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L57
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/IntegrationTests.cs#L41
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L43
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
build: DockerComposeFixture.Tests/DockerFixtureTests.cs#L27
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)