testing-expert

Analyze software testing practices across Jest, Vitest, Playwright, and Testing Library.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/phuxp17/demo_web --skill testing-expert-phuxp17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-expert
Source: https://github.com/phuxp17/demo_web/tree/main/.agent/skills/testing-expert
Command: npx skills add https://github.com/phuxp17/demo_web --skill testing-expert-phuxp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams design and implement robust testing practices by providing expert guidance on test structure, mocking strategies, asynchronous testing patterns, coverage considerations, and cross-framework debugging across Jest, Vitest, Playwright, and Testing Library.

Core Features & Use Cases

  • Comprehensive testing guidance across multiple frameworks, including how to structure unit, integration, and end-to-end tests.
  • Practical mocking and test doubles strategies, with patterns for spies, stubs, and mocks, plus proper cleanup.
  • Async and timing best practices, race-condition debugging, and reliable UI testing with Testing Library.
  • Framework-aware debugging playbooks, migration guidance, and CI/CD recommendations for reliable test runs.

Quick Start

Analyze your project's test suite to identify gaps in structure, mocking strategy, and coverage, then produce an actionable plan to improve reliability and migration readiness.

Frequently Asked Questions about testing-expert

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

FAQPage Schema
How do I debug flaky tests in Jest and Vitest caused by async race conditions?

To debug flaky tests caused by async race conditions, apply timing best practices and framework-aware debugging playbooks. This provides race-condition diagnostics and reliable UI testing patterns to resolve asynchronous failures in Jest and Vitest.

What is the best way to structure mocking strategies across different testing frameworks?

The best way to structure mocking strategies is using practical test doubles patterns with spies, stubs, and mocks. This delivers framework-aware guidance on proper cleanup and mocking implementations across Jest, Vitest, Playwright, and Testing Library.

How do I migrate my test suite from Jest to Vitest?

To migrate your test suite from Jest to Vitest, use the provided migration guidance and framework-aware debugging playbooks. This delivers an actionable plan analyzing your current test structure, mocking strategies, and coverage to ensure migration readiness.

Does this testing guidance support end-to-end tests with Playwright and Testing Library?

Yes, this testing guidance supports end-to-end tests with Playwright and Testing Library. It delivers comprehensive testing guidance on structuring unit, integration, and end-to-end tests, including reliable UI testing patterns and async handling.

Why does my test coverage analysis show gaps in reliability and maintainability?

Your test coverage analysis shows gaps because of insufficient test structure, mocking strategies, or async handling. Analyze your project's test suite to identify these specific reliability and maintainability gaps across your chosen frameworks.