rf-results

Robot Framework Results

Use the bundled script to read Robot Framework output.xml and return JSON. It supports:

• summary totals
• detailed suite/test breakdowns
• tag statistics
• execution errors, failed test messages, and keyword-level errors
• timing (keyword timing is opt-in)
• single or multiple outputs (merge or combine with rebot)

If robotcode is on PATH, robotcode results summary|show|log|stats|diff is usually quicker and uses the project's robot.toml. See rf-robotcode.

When to use

Load this skill first, before reading or searching for output.xml yourself, when the user asks about the results of a Robot Framework run:

• why tests failed, pass/fail totals, failed suites, tag statistics, slowest tests, execution errors;
• a nightly or CI run to summarise, even if they only say "the robot run" or "the results" and never mention output.xml;
• merging pabot or rerun (--rerunfailed) outputs into one report with rebot.

Not this skill: prefer rf-robotcode (robotcode results) when the robotcode CLI is installed or named.

Quick start

Run the bundled script through the project environment, so it parses output.xml with the Robot Framework version that wrote it. Script paths are relative to this skill's directory (the folder containing this SKILL.md), not to the project.

Single file summary:

uv run python "${CLAUDE_SKILL_DIR}/scripts/rf_results.py" --output output.xml --sections summary

Multiple outputs, merged (--merge replaces earlier results when tests overlap):

uv run python "${CLAUDE_SKILL_DIR}/scripts/rf_results.py" --outputs out1.xml out2.xml --merge --sections summary,details

Multiple outputs, combined under a new top-level suite (no --merge):

uv run python "${CLAUDE_SKILL_DIR}/scripts/rf_results.py" --outputs out1.xml out2.xml --name Combined --sections summary

Include keyword timing in timing output:

uv run python "${CLAUDE_SKILL_DIR}/scripts/rf_results.py" --output output.xml --sections timing --include-keyword-timing