e2e-tester

Name: e2e-tester
Availability: InStock
Author: redpanda-data

Write and run Playwright end-to-end tests for Redpanda Console using testcontainers.

4.3k|428|Updated Sep 29, 2019

Search Tags:#automation #debugging #qa #playwright #e2e-testing #testcontainers

Ready to run

npx skills add https://github.com/redpanda-data/console --skill e2e-tester-redpanda-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-tester
Source: https://github.com/redpanda-data/console/tree/main/frontend/.claude/skills/e2e-tester
Command: npx skills add https://github.com/redpanda-data/console --skill e2e-tester-redpanda-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables writing and running Playwright-based end-to-end tests for Redpanda Console using testcontainers, analyzes failures, adds missing testids, and improves test stability.

Core Features & Use Cases

End-to-end tests: Validate complete user workflows against a running stack via testcontainers.
Failure analysis: Identify flaky tests, suggest missing testids, and stabilize interactions.
Observability & Debugging: Leverage MCP Playwright agents to inspect failures and refine selectors.

Quick Start

Build the frontend assets and run the OSS e2e test suite with bun run e2e-test.

Frequently Asked Questions about e2e-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write end-to-end tests for Redpanda Console with Playwright?▼

End-to-end tests with Playwright validate complete user workflows against a running Redpanda Console stack. Use testcontainers to spin up dependencies, write tests using accessible selectors (getByRole, getByLabel) and data-testid attributes, and run them via bun run e2e-test after building frontend assets.

What are testcontainers and how do they work with Playwright tests?▼

Testcontainers provide Docker-based infrastructure for running tests in isolated environments. They let Playwright tests execute against a live Redpanda stack without manual setup, supporting both OSS and Enterprise mode configurations for multi-page user workflow validation.

How do I debug failing Playwright tests and improve test stability?▼

Analyze failures by identifying flaky tests and missing testids that prevent reliable element selection. Use MCP Playwright agents to inspect failures, refine selectors with accessible patterns, and add data-testid attributes where needed to stabilize multi-page interactions.

Can I run Playwright tests for Redpanda in both OSS and Enterprise mode?▼

Yes, this Skill applies to creating test suites for both OSS and Enterprise mode deployments. Testcontainers configuration adapts to each mode, allowing you to validate user workflows across different Redpanda Console editions.

Do I need to add test IDs to my frontend components to use Playwright tests?▼

Adding data-testid attributes improves test reliability by providing stable selectors independent of styling changes. The Skill identifies missing testids during failure analysis and recommends where to add them, though accessible selectors (getByRole, getByLabel) work without them.

How do I clean up test data after Playwright tests complete?▼

The Skill ensures test data cleanup after each test run, preventing state leakage between tests and maintaining isolation when running against Dockerized deployments via testcontainers.