This document contains the comprehensive Playwright API reference and advanced patterns. For quick-start execution patterns, see SKILL.md. Before using this ski
The Api_Reference skill provides a thorough and detailed guide to the Playwright testing framework’s API and advanced usage patterns. It covers core automation techniques, selector best practices, common user interaction methods, and strategies for handling asynchronous page behavior, network testing, and performance validation. This skill acts as a central resource for mastering Playwright’s capabilities from setup through debugging and CI/CD integration.
This skill is best suited for growth leads and agency strategists who need to implement or oversee automated testing workflows for web products, ensuring consistent user experience and performance. Performance marketers and SEO/PPC operators involved in conversion rate optimization can leverage Playwright to validate front-end changes and user flows across browsers. Teams managing continuous deployment pipelines will find the detailed CI/CD integration and parallel execution patterns particularly valuable.
Practitioners typically start by installing and configuring Playwright in their environment, defining projects and browser contexts tailored to their test requirements. Next, they create scripts using stable selectors and locators—favoring data attributes or accessibility roles—to reliably interact with page elements. The third stage involves building and running automated tests that include form interactions, navigation waits, and assertions to verify expected outcomes. Finally, users integrate these tests into CI/CD pipelines to enable parallel execution, retries on failures, and detailed reporting for ongoing quality assurance.
How do I choose selectors that won’t break with UI changes? Use data-test attributes or role-based selectors rather than CSS classes or IDs, which are more prone to change. Can Playwright tests simulate mobile devices? Yes, device emulation is supported through predefined device descriptors like “Desktop Chrome” or mobile profiles. What retry strategies are recommended in CI environments? It’s common to configure 2 retries on CI to handle flaky tests while limiting retries during local development.
Attach the Api_Reference skill to any Metaflow agent task that requires Playwright automation or testing capabilities. Expect detailed guidance on setting up your environment, authoring robust scripts, and integrating tests into larger workflows. This skill complements task execution by providing ready access to patterns and troubleshooting advice, enabling smoother automation development and maintenance. You can then...
For broader context, see our roundup of claude skills for marketing, and read connect Claude Desktop to Google Ads with MCP for related setup guidance.