Skip to content

code refactored

code refactored #7

Triggered via push November 11, 2025 04:58
Status Success
Total duration 3m 7s
Artifacts 1

mockme-api.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build: MockMe.UnitTest/TradeControllerTests.cs#L93
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/TradeControllerTests.cs#L71
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/JwtAuthManagerTests.cs#L98
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/JwtAuthManagerTests.cs#L73
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/FileControllerTest.cs#L22
TestContext property 'TestName' cannot be accessed in 'ClassInitialize' method (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0048)
build: MockMe.UnitTest/TradeControllerTests.cs#L93
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/TradeControllerTests.cs#L71
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/JwtAuthManagerTests.cs#L98
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/JwtAuthManagerTests.cs#L73
Use 'Assert.ThrowsExactly' instead of 'Assert.ThrowsException' (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0039)
build: MockMe.UnitTest/FileControllerTest.cs#L22
TestContext property 'TestName' cannot be accessed in 'ClassInitialize' method (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0048)

Artifacts

Produced during runtime
Name Size Digest
.net-app Expired
22.8 MB
sha256:aabf574bf8dde6712fa68026c4053c6d75bbaecdb18e9437743445cc1ba09d7b