---
title: "Discussion on \"Combining multiple test coverage reports for SonarCloud in GitHub Actions workflows\" | Hashnode"
description: "Discussion on \"Combining multiple test coverage reports for SonarCloud in GitHub Actions workflows\". In a typical multi-tier test setup, we run different test suites across several GitHub Actions jobs, each of which produces a coverage report. For example, we might start with unit tests running locally on the GitHub Actions runner and subsequently m..."
url: "https://hashnode.com/posts/combining-test-coverage-reports-for-sonarcloud-in-github-actions-workflows/66252aa0ee9b3fbe63842dda"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Combining multiple test coverage reports for SonarCloud in GitHub Actions workflows](https://pragmaticnotes.hashnode.dev/combining-test-coverage-reports-for-sonarcloud-in-github-actions-workflows?utm_source=hashnode&utm_medium=feed)

In a typical multi-tier test setup, we run different test suites across several GitHub Actions jobs, each of which produces a coverage report. For example, we might start with unit tests running locally on the GitHub Actions runner and subsequently m...

Apr 21, 2024 · 3 min read · pragmaticnotes.hashnode.dev  
Updated May 22, 2024  
Read the article

-   [#github-actions](https://hashnode.com/tag/github-actions)
-   [#github](https://hashnode.com/tag/github)
-   [#sonarcloud](https://hashnode.com/tag/sonarcloud)
-   [#testing](https://hashnode.com/tag/testing)
-   [#cicd](https://hashnode.com/tag/cicd)

## Written by

[Kilian Kluge](https://hashnode.com/@ionicsolutions)

@ionicsolutions

  
[View profile](https://hashnode.com/@ionicsolutions)

My journey into software and infrastructure engineering started in a physics research lab, where I discovered the merits of loose coupling and adherence to standards the hard way. I like automated testing, concise documentation, and hunting complex bugs.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.