testing-expert

Guide testing strategy for JavaScript/TypeScript projects using Jest, Vitest, Playwright, and Testing Library.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Testing Expert helps teams reduce flaky and unreliable test suites by providing deep guidance on test strategy, framework selection, and robust testing patterns.

Core Features & Use Cases

  • Assess and optimize test structure across unit, integration, and E2E levels.
  • Provide framework-appropriate best practices for mocking, asynchronous flows, and assertions.
  • Help with test plan creation, risk assessment, and architecture decisions across CI/CD pipelines.

Quick Start

Provide a comprehensive testing strategy for your project, outlining recommended frameworks, patterns, and steps.

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 my JavaScript test suite?

Fix flaky tests by applying framework-appropriate patterns for mocking and asynchronous flows. This guidance targets unreliable JavaScript and TypeScript suites, restructuring tests to ensure consistent execution across unit, integration, and E2E levels.

What is the best way to structure mocking in Vitest and Jest?

Structure mocking in Vitest and Jest by applying framework-appropriate best practices for assertions and async handling. This ensures reliable test execution and improves overall coverage quality without introducing state leakage between tests.

Does this testing strategy support Playwright and Testing Library for E2E tests?

Yes, this testing strategy supports Playwright and Testing Library for end-to-end testing scenarios. It provides framework-specific guidance to optimize test structure, asynchronous flows, and assertions across your JavaScript and TypeScript projects.

How do I optimize testing performance and coverage quality in CI/CD pipelines?

Optimize testing performance in CI/CD pipelines by assessing test architecture and implementing risk-based test plan creation. This approach addresses coverage quality and pipeline execution speed across unit, integration, and E2E testing levels.

Vitest vs Jest: how do I choose the right testing framework for my project?

Choose between Vitest and Jest by assessing your project architecture and specific testing requirements. This guidance helps with framework selection and architecture decisions, ensuring your testing tooling matches your JavaScript or TypeScript environment.

When should I not use mocks in my integration tests?

Avoid using mocks in integration tests when you need to validate true system behavior and asynchronous data flows. Over-mocking limits coverage quality; this guidance helps balance test structure and risk assessment to prevent false positives.