Skip to content

✅Unit Testing Status Check (preview branch) #129

✅Unit Testing Status Check (preview branch)

✅Unit Testing Status Check (preview branch) #129

Triggered via pull request October 24, 2023 16:09
@thestbarthestbar
synchronize #301
Status Success
Total duration 1m 37s
Artifacts

unit-test-status-check.yml

on: pull_request_target
CASL Test Status Check  /  Print & Validate Run DotNet Tests Workflow
9s
CASL Test Status Check / Print & Validate Run DotNet Tests Workflow
CASL Test Status Check  /  ...  /  Resolve Project File Path
10s
CASL Test Status Check / Resolving CASLTests Project File Path / Resolve Project File Path
CASL Test Status Check  /  Run Unit Tests
45s
CASL Test Status Check / Run Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 2 notices
CASL Test Status Check / Print & Validate Run DotNet Tests Workflow
The 'net-sdk-version' workflow input is valid.
CASL Test Status Check / Resolving CASLTests Project File Path / Resolve Project File Path
Project File Path Resolved To: /home/runner/work/CASL/CASL/Testing/CASLTests/CASLTests.csproj
CASL Test Status Check / Run Unit Tests
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
CASL Test Status Check / Run Unit Tests
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
CASL Test Status Check / Run Unit Tests
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
CASL Test Status Check / Run Unit Tests
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)