redpanda-data/e2e-tester
frontend/.claude/skills/e2e-tester/SKILL.md
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'.
$ install --global
skillsauthnpx skillsauth add redpanda-data/console e2e-testerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 10:59 PM38.9s4 files scanned
SKILL.md
- name:
- e2e-tester
- description:
- 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'.
- allowed-tools:
- Read, Write, Edit, Bash, Glob, Grep, Task, mcp__ide__getDiagnostics, mcp__playwright-test__test_run, mcp__playwright-test__test_list, mcp__playwright-test__test_debug
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 buildbefore running E2E tests (frontend assets required) - Use
testcontainersAPI for container management (never manualdockercommands in tests) - Use
page.getByRole()andpage.getByLabel()selectors (avoid CSS selectors) - Add
data-testidattributes when semantic selectors aren't available - Use Task tool with MCP Playwright agents to analyze failures
- Clean up test data using
afterEachto call cleanup API endpoints
NEVER:
- Test UI component rendering (use unit/integration tests)
- Use brittle CSS selectors like
.class-nameor#id - Use
force:trueon.click()orwaitForTimeout - Hard-code wait times (use
waitForwith 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 accessibilitygetByLabel()- For form inputsgetByText()- For content verificationgetByTestId()- 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
Related Skills
redpanda-data/frontend/.claude/skills/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance
4,258SKILL.mdUpdated Apr 11, 2026
redpanda-data/ui-development
development
VerifiedTrustedCommunity
Build UI with Redpanda Registry components, Tailwind v4, and accessibility best practices.
4,258SKILL.mdUpdated Apr 11, 2026
redpanda-data/testing
testing
VerifiedTrustedCommunity
Write and maintain tests with Vitest v4 dual configuration, mock utilities, and Zustand store testing patterns.
4,258SKILL.mdUpdated Apr 11, 2026
redpanda-data/tanstack-router-migration
development
VerifiedTrustedCommunity
Migrate React applications from React Router to TanStack Router with file-based routing. Use when user requests: (1) Router migration, (2) TanStack Router setup, (3) File-based routing implementation, (4) React Router replacement, (5) Type-safe routing, or mentions 'migrate router', 'tanstack router', 'file-based routes'.
4,258SKILL.mdUpdated Apr 11, 2026