Agent skill · software engineering · metabase
e2e-test-create
Analyze React component source code to understand UI structure, then generate idiomatic Cypress E2E tests following Metabase conventions. Falls back to Playwright MCP browser exploration only when code reading and screenshot debugging are insufficient.
Why this skill is useful
Generates Cypress E2E tests based on specific Metabase conventions and React component analysis, which the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 48,568 stars on the source repository.
What this skill does
Code-Reading-First → Generate Cypress Tests (Metabase) You are writing Cypress E2E tests for the Metabase codebase. Before generating ANY test code, you MUST analyze React component source code to understand DOM structure, selectors, and user flows. Phase 0 — Research 1. Read existing helpers before writing anything: e2e/support/helpers/ — all shared helpers (restore, signInAs, openOrdersTable, etc.) e2e/support/cypresssampledatabase.ts — table/field schema constants (ORDERS, PRODUCTS, etc.) e2e/support/cypresssampleinstancedata.ts — instance-specific IDs (ORDERSDASHBOARDID, NORMALUSERID, etc.) 2. Glob e2e/test/scenarios/ to find the closest existing spec to the area under test. Study its patterns — match them exactly. 3. Glob frontend/src/metabase/ to find React components for the feature area. Phase 1 — Code Analysis Read React component source to understand DOM structure. No browser needed — source code has everything. 1. Find relevant components: Glob and grep frontend/src/metabase/ for the feature area. 2. Extract selectors: Grep for data-testid in relevant components. 3. Note visible text: Read component JSX for button labels, headings, placeholders. 4. Note aria attributes: Grep for aria-label in relevant components. 5. Understand user flows: Read event handlers (onClick, onSubmit, onChange) to understand interactions. 6. Find API calls: Grep for Api.use, fetch, useQuery, endpoint definitions to identify API calls to intercept. 7. Cross-reference with existing specs: Find specs in the same area and reuse their proven selectors and cy.intercept patterns. Phase 2 — Start Backend Use MBEDITION=oss by default. Only use MBEDITION=ee when the user explicitly asks to write an enterprise test. Start the backend using runinbackground: true (NOT &). bin/e2e-backend automatically detects if a backend is already running and reuses it. Do NOT manually generate snapshots by running unrelated test specs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills metabase/e2e-test-create