Skip to content

feat(testo): add junit-file input for JUnit report and update additional args handling. - #89

Merged
terabytesoftw merged 1 commit into
mainfrom
feat/improve-testo
Oct 28, 2026
Merged

terabytesoftw merged 1 commit into
mainfrom
feat/improve-testo

Conversation

@terabytesoftw

Copy link
Copy Markdown
Contributor

Pull Request

  • Breaking change (fix or feature that would cause existing functionality to change)
  • Bugfix (non-breaking change that fixes an issue)
  • CI/build configuration
  • Documentation update
  • New feature (non-breaking change that adds functionality)
  • Refactoring (no functional changes)

@terabytesoftw terabytesoftw added the enhancement New feature or request label Oct 28, 2026
@coderabbitai

coderabbitai Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Caution

Review failed

The pull request is closed.

📝 Summary

Summary by CodeRabbit

  • New Features
    • JUnit report output can now be configured with a file name or disabled.
  • Bug Fixes
    • Additional test and PHPUnit arguments containing line breaks are handled more reliably.
    • Test-result and coverage uploads now run only when the workflow is not cancelled and the relevant settings are provided.

The Testo workflow and action now support a configurable JUnit report file. Testo and PHPUnit actions also normalize line breaks in additional arguments and require a nonempty coverage driver before coverage uploads.

Changes: Test action reporting and input handling

Layer / File(s) Summary
Configurable Testo JUnit reporting
.github/workflows/testo.yml, actions/testo/action.yml, CHANGELOG.md
The workflow exposes and passes a JUnit-file input. Linux and Windows commands add the JUnit option when the input is nonempty. Test-results upload requires a nonempty input and uploads that file.
Argument normalization and coverage upload conditions
actions/testo/action.yml, actions/phpunit/action.yml
Both actions replace line breaks in additional arguments with spaces. Coverage uploads require a nonempty driver other than none, and a non-cancelled workflow.

Priority: Not assessed

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant Workflow as Testo workflow
  participant Action as Testo action
  participant CLI as Testo command
  participant Upload as Test-results upload
  Workflow->>Action: pass junit-file
  Action->>CLI: add --log-junit=<file> when nonempty
  CLI->>Upload: provide the configured report file
Loading

Possibly related PRs

Suggested labels: enhancement

Merge Risk: Low · up to a9254

Existing workflows may change JUnit behavior or fail to publish custom reports; document the migration and keep report generation aligned with upload before merging.

Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit sets a report file just right,
Then sends the test results into sight.
It smooths the args where newlines grew,
And checks the driver is set, too.
The hare hops off beneath the moon.

Comment @coderabbitai help to get the list of available commands.

@terabytesoftw
terabytesoftw merged commit 7e505a9 into main Oct 28, 2026
18 of 19 checks passed
@terabytesoftw
terabytesoftw deleted the feat/improve-testo branch October 28, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant