report

The report command is used to retrieve the markdown report for a specific test job.

Usage

bytesalt report [job-id]

Arguments

• [job-id] (optional): The ID of the job you want to get the report for. If no ID is provided, the command will fetch the report for the last job run on your machine.

Options

• --output type=<full|summary>,format=<pdf|markdown|html|json>,dest=<path>: Specify output artifacts to download.
  • Can be repeated for multiple outputs.
  • type: Report content type (full or summary).
  • format: File format (pdf, markdown, html, or json).
  • dest: Local destination path (relative or absolute).
• --fail-if "expression": Define a custom failure condition using a CEL expression.
  • Default (if not specified): result.issues.critical > 0 || result.issues.high > 0
  • Example: result.issues.total == 0 (fail if any issues are found)
  • See Policy Expressions for the result schema.
• Default: If --output is not specified, the full markdown report is printed to stdout.

Description

The report command fetches the detailed, human-readable markdown report generated by the AI agent after a test job is completed. This report includes a summary of the test, identified issues, evidence (like screenshots), and suggested fixes.

This command is agent-friendly: default output is Markdown to stdout, so automation can pipe it directly into agent workflows.

When integrated into CI/CD pipelines, this command is particularly useful for extracting the test results and posting them as comments on Pull Requests or including them in build logs.

Example

bytesalt report job_123abc --fail-if "result.issues.critical > 0"

This command will fetch the report for the specified job and evaluate the fail condition. If any critical issues are found, the command will exit with code 1.