Skip to main content
By default, reqflo run streams results to stdout in a human-readable format. Reporting flags let you change the output format and write results to a file — useful for CI systems that consume structured test reports, or for archiving run output.

​
When to use it

  • CI pipelines that parse JUnit XML for test result integration (GitHub Actions, GitLab CI, Jenkins, etc.).
  • Capturing run results as a JSON artifact for downstream processing or storage.
  • Archiving structured output alongside other build artifacts.

​
Key concepts

Reporter vs. output. --reporter controls the format of the output. --output controls where it’s written (a file path). You can use either independently: reporter alone changes what goes to stdout; output alone writes the default format to a file; both together write the chosen format to the specified file. Default reporter. Without --reporter, the CLI uses a human-readable terminal format (progress indicators, colored pass/fail). This format is not intended for programmatic parsing. Available reporters:
ReporterFormatUse case
junitJUnit XMLCI test result integration
jsonJSONProgrammatic processing, archiving

​
How it works

Pass --reporter to select the format, --output to write to a file, or both together: 
reqflo run <journey> --reporter <format> --output <path>
Results from all steps — pass/fail status, assertions, errors, and timing — are included in the report.

​
Examples

Write JUnit XML to a file (common CI pattern): 
reqflo run my-journey --reporter junit --output ./results/report.xml
Write JSON output to a file: 
reqflo run my-journey --reporter json --output ./results/run.json
Stream JSON to stdout (pipe to another tool): 
reqflo run my-journey --reporter json | jq '.steps[] | select(.status == "failed")'
Data-driven run with JUnit output: 
reqflo run my-journey --data ./test-data/users.csv --reporter junit --output ./results/report.xml
Cloud run with JSON output: 
reqflo run my-journey --cloud --reporter json --output ./results/cloud-run.json
Full combination — environment, case, cloud, and JUnit: 
reqflo run my-journey \
  --env staging \
  --case "Happy path" \
  --cloud \
  --reporter junit \
  --output ./results/staging-happy-path.xml
When using --reporter junit, the output file can be consumed directly by GitHub Actions’ test-results annotations, GitLab CI’s junit artifact spec, and most CI dashboards. See CI examples for wiring this up end to end.