Test Expert Agent

Description

Complete testing expertise system for Vitest 4.0 + Playwright 1.56 + MSW 2.x (2025). PROACTIVELY activate for: (1) ANY test creation or debugging task, (2) AI-powered test generation (Playwright 1.56 agents), (3) Visual regression testing (Vitest 4.0 stable), (4) Browser Mode testing (Vitest 4.0 production-ready), (5) Test annotation (Vitest 3.2+), (6) Mutation testing quality assurance, (7) Test architecture decisions, (8) Coverage optimization, (9) MSW happy-path-first patterns, (10) Playwright E2E challenges, (11) CI/CD test configuration, (12) Windows/Git Bash cross-platform testing. Provides: Vitest 4.0 features (stable browser mode released Oct 2025, visual regression with toMatchScreenshot, Playwright trace integration, toBeInViewport matcher), Playwright 1.56 features (AI agents - Planner/Generator/Healer, titlePath hierarchy, VS Code 1.105+ integration), MSW 2.x Fetch API primitives, Windows/Git Bash path conversion awareness, comprehensive test strategy, advanced debugging techniques, 2025 testing best practices, domain-based MSW handler organization, role-based Playwright locators, mutation testing guidance, and production-ready cross-platform test infrastructure. Ensures high-quality, maintainable testing with latest 2025 patterns across all platforms.

Tool Access

All tools

Requirements

Requires power tools

Prompt Preview

**MANDATORY: Always Use Backslashes on Windows for File Paths** When using Edit or Write tools on Windows, you MUST use backslashes (`\`) in file paths, NOT forward slashes (`/`). **Examples:** - ❌ WRONG: `D:/repos/project/file.tsx` - ✅ CORRECT: `D:\repos\project\file.tsx` This applies to: - Edit tool file_path parameter - Write tool file_path parameter - All file operations on Windows systems ...

Links

GitHub Stats

1 forks

Updated 9 hours ago

Related Agents

code-architect

47.1K

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

From feature-dev

code-explorer

47.1K

Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development

From feature-dev

code-reviewer

47.1K

Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>

From pr-review-toolkit