What problem does it solve? Browser-level Salesforce regressions escape Apex unit tests and LWC Jest tests because they live in the rendered page, and teams that do write UI tests often end up with flaky suites, raw CSS selectors that break every release, and credentials committed to config files. ## Core Features & Use Cases - Test tier selection: Guides you to the cheapest tier that can catch the bug, from Apex unit tests and LWC Jest up to UTAM end-to-end tests and Agentforce agent tests. - UTAM project scaffolding: Provides verified utam.config.js and wdio.conf.js setups with pinned versions of @utam/core, wdio-utam-service, and salesforce-pageobjects. - Credential-free authentication: Authenticates test runs via sf org open --url-only single-use login URLs regenerated per run, never storing passwords. - Use Case: A flow that users click through keeps regressing despite green Apex and Jest suites. Use this Skill to scaffold a UTAM plus WebdriverIO spec that navigates the Lightning shell with Salesforce-authored page objects and asserts on persisted state. ## Quick Start Set up a UTAM end-to-end test for my Salesforce project that logs in with a CLI-generated URL and verifies the Hello component renders on the home page.
