Skip to content
TrustedSkillsbeta
Back to all skills

Writing Playwright Tests

Checked
open-metadata·vlatest·testing·Apache-2.0

Helps with writing, Playwright as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add open-metadata/openmetadata --skill writing-playwright-tests -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

open-metadata

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned open-metadata/openmetadata at 65faa8ae09.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
65faa8ae09
Manifest
skills/writing-playwright-tests/SKILL.md
Scanned
1 file, 13 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in writing Playwright end-to-end (E2E) tests, ensuring they adhere to OpenMetadata standards. It provides guidance and structure for test creation within a testing or quality assurance workflow. The skill leverages ESLint with the eslint-plugin-playwright to enforce code style and identify potential issues.

When to use it

  • When creating new Playwright E2E tests for your project.
  • To ensure Playwright tests follow OpenMetadata's established coding standards.
  • During debugging of existing Playwright tests, to help identify and resolve linting errors.
  • As part of a quality assurance process to maintain consistent test code quality.

Key capabilities

  • Guides users in writing Playwright E2E tests according to OpenMetadata standards.
  • Enforces ESLint rules for Playwright tests using eslint-plugin-playwright.
  • Highlights both error-level (blocking CI) and warning-level (suggesting improvements) ESLint rules.
  • Provides references to the PLAYWRIGHT_DEVELOPER_HANDBOOK for detailed information on ESLint enforcement.

Example prompts

  • "Help me write a Playwright test for [specific feature]."
  • "What are the recommended ESLint rules for Playwright tests?"
  • "How do I fix this ESLint error in my Playwright test: '[error message]'?"

Tips & gotchas

  • Before submitting any Playwright tests, run cd openmetadata-ui/src/main/resources/ui && yarn lint:playwright to ensure they pass ESLint checks.
  • Certain error-level rules (e.g., no-networkidle, no-page-pause) will block the CI pipeline.
  • Pay attention to warning-level rules, as they indicate potential anti-patterns in your tests that should be addressed.