From ui5
Guides creation, modification, debugging, and review of OPA5 integration tests with page objects, journeys, and waitFor. Covers multi-view handling, teardown, and browser inspection setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ui5:ui5-best-practices-opa5The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Initial Configuration for OPA5 Test** → follow `references/configuration.md`
references/configuration.mdreferences/handle-multiple-views.mdreferences/handle-teardown.mdPurpose: Efficient inspection of test failures with minimal steps.
Prerequisites: A tool to load the OPA5 test in the browser and evaluate javascript in the browser window (e.g. MCP Playwright)
Instructions: → follow references/setup-inspection-tools.md
npx claudepluginhub anthropics/claude-plugins-official --plugin ui5Runs AI-powered adversarial UI testing via the browse CLI — analyzes git diffs, explores full apps, and tests functional correctness, accessibility, responsive layout, and UX heuristics. Use for QA pull requests, auditing accessibility, or exploratory testing.
Generates test plans, manual test cases, automated Playwright tests, regression suites, and bug reports using markdown templates for QA automation.
Generates runnable Vitest unit tests and Playwright E2E specs from BDD/Gherkin test cases and scaffold code. Use when creating test implementations from BDD scenarios.