Standardize Playwright end-to-end tests for RedisInsight with page objects and UI navigation.
npx skills add https://github.com/redis/RedisInsight --skill e2e-testing-redis
Please help me install this Agent Skill. Skill: e2e-testing Source: https://github.com/redis/RedisInsight/tree/main/.ai/skills/e2e-testing Command: npx skills add https://github.com/redis/RedisInsight --skill e2e-testing-redis
This Skill prevents flaky, hard-to-maintain end-to-end tests by standardizing Playwright test structure, page objects, fixtures, and navigation patterns specifically for RedisInsight.
Use the e2e-testing Skill when adding or modifying tests under tests/e2e-playwright/ to follow the prescribed project structure, stateless page objects, UI-based navigation, and TEST_PLAN.md-driven coverage updates.
High-intent search queries and answers about installing and using this skill.
Prevent flaky Playwright E2E tests by enforcing a standalone package structure with a test plan, using stateless page objects, and applying strict beforeAll/beforeEach setup and cleanup patterns for maintainable test code.
Make Playwright tests work in both browser and Electron modes by using UI-based navigation exclusively. Call page-object goto() methods with databaseId instead of direct page.goto URL routing to ensure Electron compatibility.
A stateless page object model in Playwright uses a hierarchy like BasePage and InstancePage with component-based composition. It passes databaseId to navigation methods rather than holding internal state, ensuring tests remain isolated and maintainable.
Use beforeAll for one-time project setup and beforeEach for test-specific state isolation. Splitting Playwright projects into main, auto-update, and electron categories helps manage execution state correctly and prevents common flakiness anti-patterns.
Yes, using direct page.goto URL routing breaks Electron compatibility in E2E tests. You must use page-object goto() methods for UI navigation so tests execute reliably across both standard browser and Electron environments.
The best way to manage E2E test coverage and sequencing for RedisInsight is maintaining a TEST_PLAN.md file as the single source of truth, ensuring all test additions and modifications follow the prescribed project structure and coverage updates.
browserbaseAutomate browser interactions with persistent Playwright sessions via CLI commands.
ABLER-Digital-ServicesExecute Playwright end-to-end tests and inspect failure artifacts.
orekyuuCollect JUnit XML test reports and summarize pass, fail, and skip results.
ECFN15Run unit, component, and end-to-end tests on websites using Jest, React Testing Library, Cypress, and Playwright.
