basetenlabs/action-junit-report

basetenlabs/action-junit-report

Description: Reports junit test results as GitHub Pull Request Check

License: Apache-2.0

Stars: 0

Forks: 0

Open issues: 6

Created: 2025-03-17T14:46:16Z

Pushed: 2026-02-07T12:48:30Z

Default branch: main

Fork: yes

Parent repository: mikepenz/action-junit-report

Archived: no

README:

action-junit-report

... reports JUnit test results as GitHub pull request check.

-------

What's included 🚀 • Setup 🛠️ • Sample 🖥️ • Contribute 🧬 • License 📓

-------

What's included 🚀

• Flexible JUnit parser with wide support
• Supports nested test suites
• Blazingly fast execution
• Lighweight
• Rich build log output

This action processes JUnit XML test reports on pull requests and shows the result as a PR check with summary and annotations.

Based on action for Surefire Reports by ScaCap

Setup

Configure the workflow

name: build
on:
pull_request:

jobs:
build:
name: Build and Run Tests
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v4
- name: Build and Run Tests
run: # execute your tests generating test results
- name: Publish Test Report
uses: mikepenz/action-junit-report@v5
if: success() || failure() # always run even if the previous step fails
with:
report_paths: '**/build/test-results/test/TEST-*.xml'

Inputs

| Input | Description | |----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | report_paths | Optional. Glob expression to junit report paths. Defaults to: **/junit-reports/TEST-*.xml. | | token | Optional. GitHub token for creating a check run. Set to ${{ github.token }} by default. | | group_reports | Optional. Defines if different reports found by a single report_paths glob expression are grouped together. Defaults to true. | | test_files_prefix | Optional. Prepends the provided prefix to test file paths within the report when annotating on GitHub. | | exclude_sources | Optional. Provide , seperated array of folders to ignore for source lookup. Defaults to: /build/,/__pycache__/ | | check_name | Optional. Check name to use when creating a check run. The default is JUnit Test Report. | | suite_regex | REMOVED (as of v5). Instead use check_title_template and configure: {{BREAD_CRUMB}}{{SUITE_NAME}}/{{TEST_NAME}} | | commit | Optional. The commit SHA to update the status. This is useful when you run it with workflow_run. | | fail_on_failure | Optional. Fail the build in case of a test failure. | | require_tests | Optional. Fail if no test are found. | | require_passed_tests | Optional. Fail if no passed test are found. (This is stricter than require_tests, which accepts skipped tests). | | include_passed | Optional. By default the action will skip passed items for the annotations. Enable this flag to include them. | | check_retries | Optional. If a testcase is retried, ignore the original failure. | | check_title_template | Optional. Template to configure the title format. Placeholders: {{FILE_NAME}}, {{SUITE_NAME}}, {{TEST_NAME}}, {{CLASS_NAME}}, {{BREAD_CRUMB}}. | | bread_crumb_delimiter | Optional. Defines the delimiter characters between the breadcrumb elements. Defaults to: /. | | summary | Optional. Additional text to summary output | | check_annotations | Optional. Defines if the checks will include annotations. If disabled skips all annotations for the check. (This does not affect annotate_only, which uses no checks). | | update_check | Optional. Uses an alternative API to update checks, use for cases with more than 50 annotations. Default: false. | | annotate_only | Optional. Will only annotate the results on the files, won't create a check run. Defaults to false. | | transformers | Optional. Array of Transformers offering the ability to adjust the fileName. Defaults to: [{"searchValue":"::","replaceValue":"/"}] | | job_summary | Optional. Enables the publishing of the job summary for the results. Defaults to true. May be required to disable Enterprise Server | | detailed_summary | Optional. Include table with all test results in the summary (Also applies to comment). Defaults to false. | | flaky_summary | Optional. Include table with all flaky results in the summary (Also applies to comment). Defaults to false. | | verbose_summary | Optional. Detail table will note if there were no test annotations for a test suite (Also applies to comment). Defaults to true. | | skip_success_summary | Optional. Skips the summary table if only successful tests were detected (Also applies to comment). Defaults to false. | | include_empty_in_summary | Optional. Include entries in summaries that have 0 count. Defaults to true. | | include_time_in_summary | Optional. Include spent time in summaries. Defaults to false. | | simplified_summary | Optional. Use icons instead of text to indicate status in summary. Defaults to false. | | group_suite | Optional. If enabled, will group the testcases by test suite in the detailed_summary. Defaults to false. | | comment | Optional. Enables a comment being added to the PR with the summary tables (Respects the summary configuration flags). Defaults to false. | | updateComment | Optional. If a prior action run comment exists, it is updated. If disabled, new comments are creted for each run. Defaults to true. | | annotate_notice | Optional. Annotate passed test results along with warning/failed ones. Defaults to false. (Changed in v3.5.0) | | follow_symlink | Optional. Enables to follow symlinks when searching test files via the globber. Defaults to false. | | job_name | Optional. Specify the name of a check to update | | annotations_limit | Optional. Specify the limit for annotations. This will also interrupt parsing all test-suites if the limit is reached. Defaults to: No Limit. | | skip_annotations | Optional. Setting this flag will result in no annotations being added to the run. Defaults to false. | | truncate_stack_traces | Optional. Truncate stack traces from test output to 2 lines in annotations. Defaults to true. | |…