testing-expert

Diagnose flaky tests and configure deterministic Jest, Vitest, Playwright, and Testing Library setups.

218|14|Updated Apr 5, 2025

Search Tags:#vitest #testing #jest #playwright #testing-library #flaky-tests #test-architecture

Ready to run

npx skills add https://github.com/cin12211/orca-q --skill testing-expert-cin12211

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-expert
Source: https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert
Command: npx skills add https://github.com/cin12211/orca-q --skill testing-expert-cin12211

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design reliable, maintainable tests and diagnose flaky test scenarios across Jest, Vitest, Playwright, and Testing Library, enabling faster feedback and higher confidence in code changes.

Core Features & Use Cases

Expert guidance on choosing the right testing frameworks and patterns for unit, integration, and end-to-end tests.
Flaky test diagnosis & remediation with deterministic testing practices, mocks, and timing control.
CI/CD optimization & coverage strategy to improve reliability and reduce false positives in automated pipelines.
Use Case: When a project struggles with flaky Jest tests, apply this skill to implement stable test architecture and robust verification.

Quick Start

Use the testing-expert skill to stabilize flaky tests in the current project.

Frequently Asked Questions about testing-expert

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

FAQPage Schema

How do I fix flaky tests in Jest and Vitest?▼

To fix flaky tests in Jest and Vitest, apply deterministic testing practices using proper mocks and timing control to eliminate async timing issues and ensure reliable test execution.

Why does my Playwright E2E test fail intermittently in CI/CD?▼

Playwright E2E tests fail intermittently in CI/CD due to async timing gaps and unstable test architecture, requiring deterministic verification steps and configuration patterns to stabilize execution.

What is the best way to architecture unit and integration tests with Testing Library?▼

Test architecture for unit and integration tests with Testing Library involves choosing the right testing patterns to isolate components, applying mocks correctly, and closing coverage gaps for robust verification.

How do I resolve mocking issues causing false positives in my testing pipeline?▼

Resolving mocking issues causing false positives in your testing pipeline requires implementing strict mock configurations and timing control to prevent asynchronous leaks and ensure deterministic test results.

Can I use this testing strategy for both unit and E2E test coverage?▼

Yes, this testing strategy applies across unit, integration, and E2E tests, diagnosing coverage gaps and CI/CD pitfalls by providing tooling and configuration patterns tailored for each testing layer.

When should I not use Playwright for test architecture?▼

You should avoid relying solely on Playwright for test architecture when diagnosing unit or integration coverage gaps, as it is specialized for E2E tests rather than isolated component verification.