Loading...
Loading...
Found 25 Skills
Use when writing E2E tests with Playwright, setting up test infrastructure, debugging flaky browser tests, organizing project structure, or testing REST APIs. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing, project scaffolding, folder layout, API testing, JSON schema validation.
Use when creating step definitions with Given, When, Then, using createBdd() for step functions, implementing Page Object Model patterns, and sharing fixtures between steps.
Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).
Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow). For Prowler-specific UI conventions under ui/tests, also use prowler-test-ui.
Plan and build comprehensive Playwright E2E test suites with Page Object Model, authentication state persistence, custom fixtures, visual regression, and CI integration. Uses interview-driven planning to clarify critical user flows, auth strategy, test data approach, and parallelization before writing any tests.
Browser automation toolkit using Selenium WebDriver 4+ with Java 21+ and JUnit 5. Use when asked to create, debug, or run Selenium tests, implement Page Object Model, handle explicit waits with WebDriverWait, capture screenshots, verify UI elements with AssertJ assertions, test forms, validate user flows, or set up Maven test projects. Supports Chrome, Firefox, and Edge browsers.
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
Selenium browser automation framework. Use for web testing.
Use this for writing end-to-end (E2E) tests that simulate real user interactions in browsers (Playwright, Cypress, Selenium).
Generates production-grade Selenium WebDriver automation scripts and tests in Java, Python, JavaScript, C#, Ruby, or PHP. Supports local execution and TestMu AI cloud with 3000+ browser/OS combinations. Use when the user asks to write Selenium tests, automate with WebDriver, run cross-browser tests on Selenium Grid, or mentions "Selenium", "WebDriver", "RemoteWebDriver", "ChromeDriver", "GeckoDriver". Triggers on: "Selenium", "WebDriver", "browser automation", "Selenium Grid", "cross-browser", "TestMu", "LambdaTest".
End-to-end testing patterns with Playwright for full-stack Python/React applications. Use when writing E2E tests for complete user workflows (login, CRUD, navigation), critical path regression tests, or cross-browser validation. Covers test structure, page object model, selector strategy (data-testid > role > label), wait strategies, auth state reuse, test data management, and CI integration. Does NOT cover unit tests or component tests (use pytest-patterns or react-testing-patterns).