Writing Playwright Tests

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.