// Parse Robot Framework test results from output.xml. Use when: analyzing test execution results, extracting pass/fail statistics, filtering failures, summarizing test runs
| name | parse-rf-results |
| description | Parse Robot Framework test results from output.xml. Use when: analyzing test execution results, extracting pass/fail statistics, filtering failures, summarizing test runs |
| argument-hint | Path to output.xml, or describe what to extract (e.g. failed tests, keyword timings, suite stats) |
Uses scripts/parse_results.py to parse output.xml via robot.api.ExecutionResult.
The output.xml file is always at atest/output/output.xml. Do not guess another path unless the user explicitly provides one.
.venv/bin/python .github/skills/parse-rf-results/scripts/parse_results.py atest/output/output.xml
On Windows:
.venv\Scripts\python .github/skills/parse-rf-results/scripts/parse_results.py atest/output/output.xml
The script prints three sections automatically: pass rate summary, individual failures with error messages, and failures grouped by identical error message.
--keyword-logsInclude all keyword log messages for each failing test. Each log entry shows the timestamp, log level, and message text. HTML tags are stripped from messages.
.venv/bin/python .github/skills/parse-rf-results/scripts/parse_results.py atest/output/output.xml --keyword-logs
Example output for a failing test:
FAIL Suite.Test Name
keyword: Some Keyword (SomeLibrary)
AssertionError: expected True but got False
--- keyword logs ---
20260306 14:32:01.123 INFO Clicks the element 'id=submit'.
20260306 14:32:01.456 DEBUG Clicked element: 'id=submit' successfully.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Write Node.js/TypeScript unit tests for the playwright-wrapper layer. Use when: creating new Jest tests, mocking Playwright API calls, testing getters/interaction/browser-control functions in isolation, improving Node.js test coverage.
Write Python unit tests for Python code. Use when: creating new tests, improving test coverage, testing functions or classes in isolation, writing test cases for edge cases, or following TDD practices.
Write or review Robot Framework acceptance tests for the Browser library. Use when: creating new .robot test files, adding test cases, writing user keywords, writing library keywords in atest/library/, or reviewing existing tests for rule compliance.