testing-expert

Debug flaky tests and migrate across Jest, Vitest, Playwright, and Testing Library.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex testing ecosystems across Jest, Vitest, Playwright, and Testing Library can become brittle, hard to maintain, and difficult to migrate between frameworks. This skill provides comprehensive guidance on test structure, mocking, async testing, coverage analysis, and cross-framework debugging to improve reliability and developer confidence.

Core Features & Use Cases

  • Structured test patterns: clear organization, shared utilities, and consistent naming across unit/integration/e2e boundaries.
  • Mocking, timing & debugging: principled use of spies, stubs, and mocks with robust async patterns and flaky test debugging strategies.
  • Framework migration & CI: actionable guidance for migrating between frameworks, optimizing tests for CI, and achieving deterministic results in diverse environments.

Quick Start

Audit your project’s tests and apply the recommended reliability patterns.

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 across Jest, Vitest, and Playwright?

Fix flaky tests by applying principled spies, stubs, and mocks alongside robust async timing patterns to isolate non-deterministic behavior across Jest, Vitest, and Playwright environments.

What is the best way to migrate tests between Vitest and Jest?

Migrate tests between Vitest and Jest using actionable framework migration guidance, adapting configuration files, and aligning test structure to maintain deterministic CI results.

How do I structure unit, integration, and e2e tests with Testing Library?

Structure tests with Testing Library using clear organization, shared utilities, and consistent naming conventions to enforce strict boundaries between unit, integration, and e2e tests.

Does this testing approach support mocking and coverage analysis in CI automation?

Yes, this approach supports mocking and coverage analysis by providing actionable patterns, configuration guidance, and concrete workflows to satisfy CI and test-automation requirements deterministically.

Why do my Playwright async tests fail intermittently in CI environments?

Playwright async tests fail intermittently due to timing issues and flaky debugging strategies; applying robust async patterns and concrete workflows stabilizes diverse CI environments.