testing-preferred-patterns

Detect flaky, brittle, and skipped test patterns in test suites.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill testing-preferred-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-preferred-patterns
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/testing/testing-preferred-patterns
Command: npx skills add https://github.com/notque/vexjoy-agent --skill testing-preferred-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces test flakiness and brittleness by finding testing mistakes like flaky timing, order dependence, over-mocking, and incomplete assertions so your suite produces trustworthy evidence instead of false confidence.

Core Features & Use Cases

  • Detects test quality failures: scans test code and classifies issues such as implementation-detail assertions, brittle selectors, skipped/ignored failures, incomplete assertions, and slow or flaky execution patterns.
  • Prioritizes the highest-impact defects: ranks findings with HIGH for flaky and order-dependent tests, then guides fixes one pattern at a time to preserve intent.
  • Guides evidence-based verification: recommends fixing tests to assert observable behavior and rerunning suites to confirm deterministic results.
  • Use Case: A Go or JS/TS project has CI failures that are hard to reproduce locally; use this Skill to identify root quality smells (e.g., time.Sleep-based waits, over-mocked setups, or skipped tests) and turn them into deterministic, behavior-focused tests.

Quick Start

Use the testing-preferred-patterns skill to audit the target failing test file for flaky, brittle, and skipped test patterns, then apply one targeted pattern fix and rerun the suite until everything passes.

Frequently Asked Questions about testing-preferred-patterns

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

FAQPage Schema
How do I fix flaky tests in my CI pipeline that pass locally but fail remotely?▼

Fix flaky tests by scanning your suite for timing-based waits, order dependence, and over-mocking, then applying targeted behavior-first fixes. This Skill identifies those exact quality smells and guides single-pattern fixes to restore deterministic test execution and reliable evidence.

What causes brittle tests and how can I make my test suite more reliable?▼

Brittle tests are caused by implementation-detail assertions, over-mocking, and brittle selectors that break on harmless refactoring. You can make your suite reliable by auditing for these test quality smells and rewriting tests to assert observable behavior instead of internal implementation.

How do I refactor over-mocked unit tests to use behavior-driven testing?▼

Refactor over-mocked tests by scanning for implementation-detail assertions and replacing them with behavior-first assertions. This Skill prioritizes high-impact defects and guides you to fix tests one pattern at a time, verifying deterministic results by rerunning the affected suite.

Can I use this testing skill to audit skipped or ignored test failures in Go and JS projects?▼

Yes, you can audit skipped or ignored test failures in Go and JS/TS projects. The Skill scans test code to classify skipped failures as a quality smell, ranks them by impact, and guides targeted fixes to ensure your suite produces trustworthy evidence without false confidence.

What is the best way to identify incomplete assertions in an E2E test suite?▼

The best way to identify incomplete assertions is to scan your E2E test suite for quality smell categories like missing validations and over-mocking. This Skill reports findings with file:line evidence and prioritizes single-pattern fixes to enforce observable behavior verification.