testing-engineer

Enforces deterministic Vitest and Playwright testing patterns to prevent flaky tests.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Yoraexe/ceobe --skill testing-engineer-yoraexe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-engineer
Source: https://github.com/Yoraexe/ceobe/tree/main/skills/testing-engineer
Command: npx skills add https://github.com/Yoraexe/ceobe --skill testing-engineer-yoraexe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing maintainable, fast, and reliable tests across unit, integration, and E2E scopes by enforcing deterministic patterns and best practices to reduce flakiness and false positives.

Core Features & Use Cases

  • AAA Pattern: Encourages Arrange, Act, Assert structure to improve readability, isolation, and reliability of tests.
  • Mocking & Isolation: Guidance on isolating units, mocking external dependencies, and avoiding brittle tests tied to implementation details.
  • Integration & E2E Guidance: Strategies for end-to-end tests, API interaction, and database integration with stable, repeatable setups.
  • Flaky Test Prevention: Techniques such as deterministic timers, controlled environments, and rigorous setup/teardown to minimize flakiness and improve test confidence.

Quick Start

Start by enabling deterministic timers and applying the AAA pattern in unit tests, then extend these practices to integration and end-to-end tests.

Frequently Asked Questions about testing-engineer

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

FAQPage Schema
How do I fix flaky tests in my Vitest unit testing suite?

Fix flaky tests by enforcing deterministic patterns in Vitest, such as utilizing deterministic timers, applying the AAA structure, and isolating units through controlled mocking to eliminate unreliable external dependencies.

What is the best way to structure integration and E2E tests with Playwright?

The best way to structure integration and E2E tests is applying the AAA pattern alongside rigorous setup and teardown routines, ensuring stable, repeatable environments for API interactions and database integration testing.

Why does my test suite have false positives tied to implementation details?

False positives occur when tests are brittle and tied to implementation details; prevent this by isolating units and mocking external dependencies to ensure your tests validate functional requirements rather than internal code structure.

Can I use deterministic testing patterns for both frontend and backend projects?

Yes, you can apply deterministic testing patterns across diverse frontend and backend codebases, utilizing Vitest for unit and integration tests alongside Playwright for end-to-end tests to ensure robust reliability.

How do I mock external dependencies without creating brittle tests?

Mock external dependencies by focusing on isolating units and avoiding tests tied to implementation details, utilizing controlled environments and deterministic timers to prevent flakiness and improve test confidence.