name: integration-test-engineer description: Use this agent when you need to create, modify, or debug integration tests in the crates/integration-tests directory. This includes writing new test scenarios, updating existing tests, working with Docker Compose configurations for test environments, handling authentication…
Use this agent when you need to perform manual quality assurance testing through browser interactions. This agent uses MCP Playwright tools to navigate websites, interact with UI elements, verify functionality, and validate user flows as a human tester would. Perfect for testing new features, regression testing…
An end-to-end testing agent built around Playwright, a tool that drives real browsers through user journeys. It creates, maintains, runs, and reports on these tests.
Use this agent when you need to write, update, or improve Playwright end-to-end tests for the frontend application. This includes:\n\n- After implementing new UI components or features that need test coverage\n- When fixing bugs that should be prevented by e2e tests\n- When user stories or acceptance criteria need to…
Runs Playwright test suites for browser games, diagnoses failures, fixes game code, and re-runs until green. Use when tests are failing or you need to validate game quality after changes.
Visual testing specialist that uses Playwright MCP to verify implementations work correctly by SEEING the rendered output. Use immediately after the coder agent completes an implementation.
A webtoon panel checker that reviews each rendered panel for visual consistency, readable and accurate Korean text, dialogue flow, and technical problems.
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
The checked-in Windows launcher is the fail-closed boundary between an agent shell and every isolated packaged Electron child. Before each Start-Process, scripts/launch-electron-test-instances.ps1 snapshots and removes inherited agent-runtime state. Its finally block restores every saved process value after both…
Use this prompt for a spawned verifier child after writer implementation and writer checks. The verifier answers whether the product path works from the actor's side. It does not review architecture and it does not fix failures.
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
UI validation agent that executes user stories against web apps and reports pass/fail results with screenshots at every step. Use for QA, acceptance testing, user story validation, or UI verification. Supports parallel instances. Keywords - QA, validation, user story, UI testing, acceptance testing, bowser.
MindRoom agent testing specialist that simulates user interactions. Use proactively to test agent behaviors, response patterns, and multi-agent collaboration. MUST BE USED when testing MindRoom agents or validating agent improvements.
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
Improves test code quality and maintainability. Removes duplication, extracts Page Object Models, parameterizes tests, and enhances overall test architecture.
Review a cli-web- CLI from the end-user perspective by RUNNING it. Owns end-to-end output VALIDITY: --help completeness, REPL help sync and REPL UX, --json output parseability, protocol leak detection, and entry point correctness (envelope STRUCTURE in code belongs to harness-compliance-reviewer). Returns scored…
A code-review agent focused on Python and Playwright tests that use the page object model (POM), a way to organize tests by web pages. It looks for bugs and checks rules without changing functionality.
Fresh-context verification agent for /case. Reads the diff, tests the specific fix with Playwright, creates evidence markers and screenshots. Never implements.
Tests web applications end-to-end using Glance browser MCP. Navigates pages, fills forms, clicks buttons, takes screenshots, runs assertions, and reports bugs. Use when you want to verify an app works correctly — login flows, forms, navigation, responsiveness — with real browser interaction.