Below you will find pages that utilize the taxonomy term “jeantessier”
January 4, 2026
Code Coverage Summary Action
Version updated for https://github.com/jeantessier/code-coverage-summary-action to version v1.0.7.
This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes.
Release notes Use pre-built Docker image.
Full Changelog: https://github.com/jeantessier/test-summary-action/compare/v1.0.6...v1.0.7
January 4, 2026
Test Summary Action
Version updated for https://github.com/jeantessier/test-summary-action to version v1.0.10.
This action is used across all versions by 39 repositories. Go to the GitHub Marketplace to find the latest changes.
Release notes Use pre-built Docker image.
Full Changelog: https://github.com/jeantessier/test-summary-action/compare/v1.0.9...v1.0.10
January 1, 2026
Code Coverage Summary Action
Version updated for https://github.com/jeantessier/code-coverage-summary-action to version v1.0.5.
This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes.
Action Summary The code-coverage-summary-action is a GitHub Action designed to automate the summarization of JaCoCo code coverage results for Gradle builds. It aggregates coverage data from multiple subprojects and generates a concise report, displayed as a table in the GitHub workflow summary. This action simplifies the process of analyzing code coverage metrics across projects, enhancing visibility and aiding developers in tracking testing completeness.
January 1, 2026
Test Summary Action
Version updated for https://github.com/jeantessier/test-summary-action to version v1.0.9.
This action is used across all versions by 39 repositories. Go to the GitHub Marketplace to find the latest changes.
Action Summary The test-summary-action GitHub Action is designed to summarize JUnit test results from Gradle builds. It automates the collection and reporting of test outcomes (e.g., passed, failed, skipped) across multiple subprojects, presenting the results in a clear table format within the GITHUB_STEP_SUMMARY. This action helps developers quickly identify and analyze test statuses, enhancing build transparency and debugging efficiency.