robot-testing

Write and debug Robot Framework tests for Salesforce org setup and end-to-end workflows.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill robot-testing-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: robot-testing
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/robot-testing
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill robot-testing-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Salesforce Lightning pages use LWC shadow DOM that standard Selenium locators cannot pierce, and many org settings have no API equivalent, making UI automation fragile and hard to verify. This Skill provides proven patterns for writing, modifying, and debugging Robot Framework suites that configure orgs and validate business workflows. ## Core Features & Use Cases - Shadow DOM traversal patterns: Recursive JavaScript helpers (findEl/findAll), native setter for LWC inputs, and combobox/toggle interaction flows that work across shadow boundaries. - Setup vs E2E test separation: Guidance for org-configuration automation in tests/setup/ versus functional tests in tests/e2e/, with CCI task wiring and Python wrapper conventions. - Mandatory live-org verification: Rules requiring behavioral changes to be run against a live scratch org, since robot --dryrun only checks syntax and never launches a browser. - Use Case: You need to automate enabling the Document Builder toggle during org provisioning. Follow the setup-test pattern, reuse SetupToggles.robot keywords, wrap it in a CCI task, and verify against a live scratch org before committing. ## Quick Start Ask the agent to write a new Robot Framework setup test that enables a Salesforce org toggle, following the shadow DOM patterns and live-org verification rules in this skill.

Frequently Asked Questions about robot-testing

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

FAQPage Schema
How do I write Robot Framework tests for Salesforce Lightning shadow DOM?

Use recursive JavaScript traversal helpers like findEl and findAll instead of standard Selenium locators, which cannot cross shadow boundaries. Prepend the shared helper to Execute JavaScript blocks and dispatch events with composed: true.

How do I automate Salesforce org settings that have no API?

Create a setup suite under tests/setup/ that drives the Setup UI with Robot Framework, then wrap it in a CCI Python task and wire it into the provisioning flow. Reuse SetupToggles.robot keywords for common toggle interactions.

Why does my Robot Framework JavaScript block break with comments?

Robot joins Execute JavaScript continuation lines without newlines, so a // comment swallows the rest of the script. Use /* */ block comments and semicolon-terminate every statement.

Is robot --dryrun enough to verify a Robot Framework test change?

No. Dryrun only resolves keyword names and syntax; it never launches a browser or executes JavaScript. Behavioral changes must be run against a live scratch org via the CCI task wrapper or a direct robot run before committing.

Why doesn't Input Text work on Lightning web component inputs?

Standard input_text does not trigger LWC change detection. Use the native setter pattern: call the HTMLInputElement value setter, then dispatch input and change events with bubbles and composed set to true.