Skip to content
✅Unit Testing Status Check

✅Unit Testing Status Check (main branch) #83

Sign in to view logs

✅Unit Testing Status Check (main branch)

✅Unit Testing Status Check (main branch) #83

Triggered via pull request November 17, 2023 17:16
@renovaterenovate[bot]
opened #142
Status Success
Total duration 1m 32s
Artifacts –

unit-test-status-check.yml

on: pull_request_target
PackageMonster Test Status Check  /  Print & Validate Run DotNet Tests Workflow
9s
PackageMonster Test Status Check / Print & Validate Run DotNet Tests Workflow
PackageMonster Test Status Check  /  ...  /  Resolve Project File Path
15s
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
PackageMonster Test Status Check  /  Run Unit Tests
39s
PackageMonster Test Status Check / Run Unit Tests
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 3 notices
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/GlobalUsings.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/GlobalUsings.cs#L6
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/GlobalUsings.cs#L7
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/GlobalUsings.cs#L8
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Program.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Program.cs#L6
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Services/AppService.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Services/ArgParsingService.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Services/GitHubConsoleService.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Run Unit Tests: PackageMonster/Services/IActionOutputService.cs#L5
Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)
PackageMonster Test Status Check / Print & Validate Run DotNet Tests Workflow
The 'net-sdk-version' workflow input is valid.
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
DotNet Lib Release Script URL: https:/raw.githubusercontent.com/KinsonDigital/Infrastructure/v13.3.1/cicd/scripts
PackageMonster Test Status Check / Resolving PackageMonsterTests Project File Path / Resolve Project File Path
Set output 'project-file-path' set to a value of '/home/runner/work/PackageMonster/PackageMonster/Testing/PackageMonsterTests/PackageMonsterTests.csproj'.