Skip to content
✅Unit Testing Status Check

✅Unit Testing Status Check (preview branch) #48

Sign in to view logs

✅Unit Testing Status Check (preview branch)

✅Unit Testing Status Check (preview branch) #48

Triggered via pull request July 27, 2023 17:25
@renovaterenovate[bot]
synchronize #248
renovate/kinsondigital-infrastructure-10.x
Status Success
Total duration 1m 6s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

unit-test-status-check.yml

on: pull_request
CASL Test Status Check  /  Print & Validate Run DotNet Tests Workflow
4s
CASL Test Status Check / Print & Validate Run DotNet Tests Workflow
CASL Test Status Check  /  ...  /  Resolve Project File Path
5s
CASL Test Status Check / Resolving CASLTests Project File Path / Resolve Project File Path
CASL Test Status Check  /  Run Unit Tests
33s
CASL Test Status Check / Run Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 2 notices
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.
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.
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.
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.
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