robot-testing

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

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill robot-testing-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: robot-testing
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/robot-testing
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill robot-testing-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Salesforce Lightning uses 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/, including 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 validates syntax. - Use Case: When adding a new setup toggle suite, follow the documented patterns to create the .robot file, wrap it in a Python CCI task, register it in cumulusci.yml, and verify it against a scratch org before merging. ## Quick Start Ask the agent to write a new Robot Framework setup test that enables a Salesforce org setting, following the shadow DOM and 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?▼

Use SeleniumLibrary combined with recursive JavaScript traversal to pierce LWC shadow DOM, since standard XPath locators cannot cross shadow boundaries. Import shared resources like E2ECommon.robot or SetupToggles.robot and follow the documented combobox and toggle interaction patterns.

How to automate Salesforce org settings that have no API?▼

Create a setup suite under tests/setup/ that drives the Setup UI with shadow DOM JavaScript helpers, then wrap it in a Python CCI task registered in cumulusci.yml. Wire the task into the prepare flow so it runs mid-provisioning.

Why do Selenium clicks fail on Salesforce Lightning components?▼

Lightning Web Components render inside synthetic shadow roots that standard Selenium locators cannot reach. Use recursive shadowRoot traversal in Execute JavaScript blocks, and dispatch events with composed: true so they cross shadow boundaries.

Is robot --dryrun enough to verify Robot Framework test changes?▼

No, dryrun only resolves keyword names, argument counts, and syntax without launching a browser. Behavioral changes to keywords, locators, or JavaScript logic must be run against a live scratch org before being marked verified.

Why does Input Text not work on Lightning web component fields?▼

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