gardenlinux/pytest-multi-results-action
Post pytest results to the workflow summary
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| files | Multiple JUnit XML file patterns for multi-suite aggregation. Each pattern can be a file, directory, or wildcard pattern. See @actions/glob for supported patterns. | yes | — |
| title | Title of the test results section in the workflow summary | no | Test results |
| summary | Add a summary of the results at the top of the report | no | true |
| details | Add details section after the test results | no | true |
| fail-on-empty | Fail the workflow if no JUnit XML was found | no | true |
| metadata-fields | Comma-separated list of metadata fields to extract from XML and display in tables. Supports pytest-metadata properties and custom XML attributes. If not provided, defaults to "Suite" column. Example: "artifact,type,namespace" | no | "" |
| metadata-field-mapping | JSON object mapping XML attribute/property names to display names. Example: '{"artifact": "Artifact", "type": "Type", "namespace": "Namespace"}' | no | {} |
| result-types | Comma-separated list of result types to include, in order. Allowed values: passed, skipped, xfailed, failed, xpassed, error | no | passed,skipped,xfailed,failed,xpassed,error |
| details-result-types | Comma-separated list of result types to include, in order. Allowed values: passed, skipped, xfailed, failed, xpassed, error | no | failed,error |
Outputs
no outputs