How do I install the E2e Tester skill?

Run npx skillmds@latest add redpanda-data/e2e-tester in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is E2e Tester safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with E2e Tester?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is E2e Tester free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published E2e Tester?

redpanda-data (@redpanda-data) published this skill. Their other Agent Skills are listed on their SkillMD profile.

E2e Tester by redpanda-data — Agent Skill

Name: E2e Tester
Author: redpanda-data

E2e Tester

Write and run Playwright E2E tests for Redpanda Console using testcontainers. Analyzes test failures, adds missing testids, and improves test stability. Use when user requests E2E tests, Playwright tests, integration tests, test failures, missing testids, or mentions 'test workflow', 'browser testing', 'end-to-end', or 'testcontainers'.

redpanda-data 40972f3 4 files · 15.5 KB Updated Sep 17, 2026 6 repo stars

File contents

E2E Testing with Playwright & Testcontainers

Write end-to-end tests using Playwright against a full Redpanda Console stack running in Docker containers via testcontainers.

When to Use This Skill

Testing 2+ step user journeys (login -> action -> verify)
Multi-page workflows
Browser automation with Playwright

NOT for: Component unit tests -> use testing

Critical Rules

ALWAYS:

Run bun run build before running E2E tests (frontend assets required)
Use testcontainers API for container management (never manual docker commands in tests)
Use page.getByRole() and page.getByLabel() selectors (avoid CSS selectors)
Add data-testid attributes when semantic selectors aren't available
Use Task tool with MCP Playwright agents to analyze failures
Clean up test data using afterEach to call cleanup API endpoints

NEVER:

Test UI component rendering (use unit/integration tests)
Use brittle CSS selectors like .class-name or #id
Use force:true on .click() or waitForTimeout
Hard-code wait times (use waitFor with conditions)
Leave containers running after test failures
Commit test screenshots to git

Commands

bun run build                # Build frontend (REQUIRED first!)
bun run e2e-test             # Run OSS E2E tests
bun run e2e-test-enterprise  # Run Enterprise E2E tests
bun run e2e-test:ui          # Playwright UI mode (debugging)
bun run e2e-test tests/topics/create-topic.spec.ts  # Specific file

Test Architecture

OSS Mode (bun run e2e-test): Redpanda + Backend + OwlShop containers Enterprise Mode (bun run e2e-test-enterprise): Same + RBAC, SSO (requires console-enterprise repo)

File location: tests/<feature>/*.spec.ts

Selector Priority

getByRole() - Best for accessibility
getByLabel() - For form inputs
getByText() - For content verification
getByTestId() - When semantic selectors aren't clear
CSS selectors - Avoid if possible

Test ID Naming

kebab-case: data-testid="feature-action-element"
Specific: include feature name + action + element type
Dynamic: data-testid={\item-delete-${id}`}`

References

Container Setup — Testcontainer lifecycle, configs, CI setup
Test Patterns — Multi-step workflows, forms, tables, API testing
Failure Analysis — Error patterns, debugging, MCP Playwright agents

Output

After completing work:

Confirm frontend build succeeded
Verify all E2E tests pass
Note any new test IDs added to components
Mention cleanup of test containers

---name: e2e-testerdescription: Write and run Playwright E2E tests for Redpanda Console using testcontainers. Analyzes test failures, adds missing testids, and improves test stability. Use when user requests E2E tests, Playwright tests, integration tests, test failures, missing testids, or mentions 'test workflow', 'browser testing', 'end-to-end', or 'testcontainers'.---# E2E Testing with Playwright & TestcontainersWrite end-to-end tests using Playwright against a full Redpanda Console stack running in Docker containers via testcontainers.## When to Use This Skill- Testing 2+ step user journeys (login -> action -> verify)- Multi-page workflows- Browser automation with Playwright**NOT for:** Component unit tests -> use [testing](../testing/SKILL.md)## Critical Rules**ALWAYS:**- Run `bun run build` before running E2E tests (frontend assets required)- Use `testcontainers` API for container management (never manual `docker` commands in tests)- Use `page.getByRole()` and `page.getByLabel()` selectors (avoid CSS selectors)- Add `data-testid` attributes when semantic selectors aren't available- Use Task tool with MCP Playwright agents to analyze failures- Clean up test data using `afterEach` to call cleanup API endpoints**NEVER:**- Test UI component rendering (use unit/integration tests)- Use brittle CSS selectors like `.class-name` or `#id`- Use `force:true` on `.click()` or `waitForTimeout`- Hard-code wait times (use `waitFor` with conditions)- Leave containers running after test failures- Commit test screenshots to git## Commands```bashbun run build # Build frontend (REQUIRED first!)bun run e2e-test # Run OSS E2E testsbun run e2e-test-enterprise # Run Enterprise E2E testsbun run e2e-test:ui # Playwright UI mode (debugging)bun run e2e-test tests/topics/create-topic.spec.ts # Specific file```## Test Architecture**OSS Mode (`bun run e2e-test`):** Redpanda + Backend + OwlShop containers**Enterprise Mode (`bun run e2e-test-enterprise`):** Same + RBAC, SSO (requires `console-enterprise` repo)File location: `tests/<feature>/*.spec.ts`## Selector Priority1. `getByRole()` - Best for accessibility2. `getByLabel()` - For form inputs3. `getByText()` - For content verification4. `getByTestId()` - When semantic selectors aren't clear5. CSS selectors - Avoid if possible## Test ID Naming- kebab-case: `data-testid="feature-action-element"`- Specific: include feature name + action + element type- Dynamic: `data-testid={\`item-delete-\${id}\`}`## References- [Container Setup](references/container-setup.md) — Testcontainer lifecycle, configs, CI setup- [Test Patterns](references/test-patterns.md) — Multi-step workflows, forms, tables, API testing- [Failure Analysis](references/failure-analysis.md) — Error patterns, debugging, MCP Playwright agents## OutputAfter completing work:1. Confirm frontend build succeeded2. Verify all E2E tests pass3. Note any new test IDs added to components4. Mention cleanup of test containers

Frequently asked questions