rf-step-author

Generates Robot Framework test steps from natural-language checklist items using Browser library conventions.

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill rf-step-author-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rf-step-author
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/rf-step-author
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill rf-step-author-wu-mao-chia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Robot Framework test scripts by hand from checklist items is slow and error-prone, especially when locators must match the actual frontend code and project conventions must be enforced consistently. ## Core Features & Use Cases - Checklist-to-RF Conversion: Transforms natural-language Checklist items into structured Robot Framework test cases with Settings, Variables, and Test Cases sections. - Locator Verification: Cross-checks every locator against the actual Vue page components under frontend/src/pages/ to avoid brittle selectors. - Convention Enforcement: Applies project rules such as Browser library preference, no Sleep statements, no absolute XPath, and mandatory [Documentation] and [Tags] on every test case. - Use Case: Given a Checklist record describing a login flow, generate a .robot suite that uses role-based locators verified against the real login page, with shared steps extracted into a .resource file. ## Quick Start Convert this checklist item into a Robot Framework test case following the project conventions and verify the locators against the corresponding Vue page.

Frequently Asked Questions about rf-step-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a checklist item into Robot Framework test steps?▼

Read the Checklist model and related TestCase for pre-conditions, find the matching Vue page to extract real locators, then draft Settings, Variables, and Test Cases sections using the Browser library skeleton with Documentation and Tags on each case.

Should I use Browser library or SeleniumLibrary in Robot Framework?▼

Prefer the Browser library (Playwright-based) for new scripts in this project. Never mix SeleniumLibrary and Browser in a single suite, as their locator syntaxes and wait mechanisms are incompatible.

What locator strategy works best with robotframework-browser?▼

Prefer role-based locators like role=button[name="送出"], then visible text, then stable id or data-testid attributes. Avoid brittle XPath expressions and absolute CSS paths that break on UI changes.

Why should I avoid Sleep statements in Robot Framework tests?▼

Sleep creates flaky, slow tests because fixed delays do not adapt to actual page load times. Use Browser library's auto-waiting keywords like Click and Fill Text, or explicit waits, so interactions proceed as soon as elements are ready.

When should repeated Robot Framework steps be moved to a resource file?▼

Extract any step sequence repeated three or more times into a user keyword inside a .resource file under backend/robot_scripts/resources/. This keeps suites readable and centralizes maintenance when the UI changes.