✅Unit Testing Status Check (preview branch) #98
Triggered via pull request
September 4, 2023 21:58
renovate[bot]
renovate[bot]
opened
#292
Status
Success
Total duration
1m 14s
Artifacts
–
unit-test-status-check.yml
on: pull_request_target
CASL Test Status Check
/
Print & Validate Run DotNet Tests Workflow
4s
CASL Test Status Check
/
...
/
Resolve Project File Path
7s
CASL Test Status Check
/
Run Unit Tests
37s
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:
Testing/CASLTests/Helpers/AssertExtensions.cs#L51
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:
Testing/CASLTests/Helpers/AssertExtensions.cs#L74
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:
Testing/CASLTests/Helpers/AssertExtensions.cs#L51
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:
Testing/CASLTests/Helpers/AssertExtensions.cs#L74
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020)
|