Skip to content

Latest commit

 

History

History
25 lines (16 loc) · 1.69 KB

build-test-package-workflow.md

File metadata and controls

25 lines (16 loc) · 1.69 KB
Raw

build-test-package workflow

Build, test and package

This workflow:

  • Builds the code and runs tests on windows-latest and ubuntu-latest.
  • Uploads an opencover code coverage file as a workflow artifact.
  • Generates code coverage report and uploads it as a workflow artifact.
  • Uploades test results as a workflow artifact.
  • Generates NuGet packages and uploads them as a workflow artifact.

Build warnings will make the workflow fail

The dotnet build command includes the -warnaserror flag which will cause the build to fail if there are any errors.

This is used to help keep the code healthy whilst balancing local dev. Meaning, when developing locally there is no need to force all warnings to be fixed to be able to build the code.

Testing loggers

When running tests we use 3 loggers:

  • trx: normal logger, produces test result files which can be downloaded and viewed on Visual Studio.
  • GitHubActions: used to produce annotations on the workflow to give more visibility when tests fail. For more info see GitHub Actions Test Logger. It also adds annotations on PRs.
  • liquid.custom: Uses a template to create a markdown reports for the test results. These markdown reports are uploaded as workflow artifacts and in case of Pull Requests they are added as comments. For more info see Liquid Test Reports.