playwright-test
Generate robust, zero-flakiness Playwright E2E tests following OpenMetadata patterns.
Skill by open-metadata
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/open-metadata-playwright-test
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: backend, testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/playwright-test
What's inside
- Skill name
playwright-test- Description
- Generate robust, zero-flakiness Playwright E2E tests following OpenMetadata patterns. Creates comprehensive test files with proper waits, API validation, multi-role permissions, and complete entity lifecycle management.
- License
- Apache-2.0
- Instructions
- 167 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- name: "playwright-test" does not match folder "playwright"
Files (1)
- SKILL.md
SKILL.md (first lines)
# Playwright Test Generator - OpenMetadata Generate production-ready, zero-flakiness Playwright tests following OpenMetadata conventions. ## Usage ``` /playwright-test Feature: <feature name> Category: <Features|Pages|Flow|VersionPages> Entity: <Table|Dashboard|Pipeline|Topic|Database|User|Team|Glossary|Other> Domain: <Governance|Discovery|Platform|Observability|Integration> Scenarios: - <scenario 1 description> - <scenario 2 description> - <scenario 3 description> Roles: <admin|dataConsumer|dataSteward|owner> (optional, defaults to admin) ``` ## Quick Example ``` /playwright-test Feature: Data Quality Rules Category: Features Entity: Table Domain: Observability Scenarios: - Admin can create and configure data quality rules - Data consumer can view test results but not edit rules - Test results are persisted after page reload Roles: admin, dataConsumer ``` --- ## Instructions ### Step 1: Read the Handbook FIRST **CRITICAL**: Before generating any tests, read and apply ALL patterns from: ``` openmetadata-ui/src/main/resources/ui/playwright/PLAYWRIGHT_DEVELOPER_HANDBOOK.md ``` The handbook contains: - Testing philosophy (user-centric, behavior-focused) - Anti-flakiness patterns (the :visible selector chain pattern, controls under the toast stack, etc.) - Test timeout strategies (test.slow() vs test.setTimeout()) - Common test patterns (form submission, dropdowns, multi-role testing) - Locator priority guidelines - Support classes reference - Domain tags - Validation checklist **Apply ALL handbook principles before proceeding.** --- ### Step 2: Generate Test Using Handbook Template Use the **Test File Structure Template** from the handbook. It includes: - Proper imports (performAdminLogin, entity classes, utilities) - test.describe with domain tags - beforeAll/afterAll for entity lifecycle via API - test.slow() for timeout handling - test.step() for clear organization - API response validation pattern --- ### Step 3: Apply Common Test Patterns from Handbook Reference the **Common Test Patterns** section for: - Form submission with API validation - Dropdown selection (with :visible chain pattern) - Multi-role permission testing - Data persistence verification - Navigation patterns - Search and filter patterns --- ### Step 4: Run ESLint Check Before returning the generated test, run the full Playwright lint gate — the same one CI runs: ```bash cd openmetadata-ui/src/main/resources/ui yarn lint:playwright ``` Every `playwright/*` and `om-playwright/*` guardrail rule runs at `error`; repo-wide `openmetadata-playwright/*` rules set their own severity and may be `warn`. Fix any errors before finalizing — never add a new entry to `eslint-suppressions.json` to make this pass. See the handbook's **ESLint Enforcement** section for the full, generated rule reference. ### Step 5: Validate Against Handbook Checklist Before returning the generated test, verify ALL items from the handbook's **Validation Checklist**: - ✅ Structure & Organization (test.step, domain tags, imports, beforeAll/afterAll) - ✅ Anti-Flakiness (no waitForTimeout, no networkidle, no force: true, no positional selectors, no stored :visible locators, `clickIgnoringToasts` for bottom-aligned controls) - ✅ API & Network (waitForResponse before actions, status code validation) - ✅ Waits & Assertions (waitForAllLoadersToDisappear, semantic locators, proper assertions) - ✅ ESLint (`yarn lint:playwright` passes with zero errors) - ✅ Coverage & Roles (multi-role tests, data persistence, error handling) --- ## Key Reminders **All patterns, rules, and best practices are in the handbook.** Read and apply the handbook sections in order: 1. **Anti-Flakiness Patterns** (CRITICAL - #1 cause of flaky tests) 2. **Test File Structure Template** (for proper test structure) 3. **Common Test Patterns** (for specific scenarios) 4. **ESLint Enforcement** (run `yarn lint:playwright` — every rule is `error`)
From open-metadata/OpenMetadata, Apache-2.0.
More from open-metadata/OpenMetadata
- 0.862score
openmetadata-pr-review
open-metadata
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
java-affected-tests
open-metadata
Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer…
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
planning
open-metadata
Use when starting a non-trivial feature, refactor, or multi-file change.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
systematic-debugging
open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
pr-checklist
open-metadata
Use when opening or finalizing a GitHub PR for OpenMetadata.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
tdd
open-metadata
Use when implementing new features or fixing bugs to enforce test-driven development.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
code-review
open-metadata
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
verification
open-metadata
Use before claiming any task is complete.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
ui-pr-recording
open-metadata
Use during PR creation for a UI feature or feature task.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
openmetadata-workflow
open-metadata
Meta-skill loaded at session start.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
connector-audit
open-metadata
Deep reliability audit for OpenMetadata connectors — runs 7 investigation prompts (metadata, errors, auth, lineage, scale, synthesis, implementation) against…
SkillAFreshness: A★ 15.6KClaude Code +9
Compare and alternatives
Featured in
Signals
- Stars
- 15,567
- Forks
- 2,481
- Open issues
- 677
- Contributors
- 519
- Last commit (this folder)
- Oct 7, 2026 (20 days ago)
- Last release
- Oct 21, 2026 (6 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/open-metadata/OpenMetadata
- Website
- open-metadata.org
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from open-metadata
- 0.862score
openmetadata-pr-review
open-metadata
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
pr-checklist
open-metadata
Use when opening or finalizing a GitHub PR for OpenMetadata.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
systematic-debugging
open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
tdd
open-metadata
Use when implementing new features or fixing bugs to enforce test-driven development.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
planning
open-metadata
Use when starting a non-trivial feature, refactor, or multi-file change.
SkillAFreshness: A★ 15.6KClaude Code +9
Cite this page
playwright-test skill. Agent Mart. https://agentmart.dev/skills/open-metadata-playwright-test (last updated 2026-10-24)