testing-anti-patterns

Detect testing anti-patterns and score mock overuse in test suites.

2|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/krzemienski/shannon-framework --skill testing-anti-patterns-krzemienski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-anti-patterns
Source: https://github.com/krzemienski/shannon-framework/tree/main/skills/testing-anti-patterns
Command: npx skills add https://github.com/krzemienski/shannon-framework --skill testing-anti-patterns-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catalogs testing anti-patterns and provides quantitative detection to prevent mock usage, test-only production changes, and dependency misunderstanding.

Core Features & Use Cases

  • Anti-pattern catalogs (mock testing, test-only methods, in-memory tests)
  • Quantitative scoring of detected anti-patterns
  • Prescriptive fixes to enforce NO MOCKS and real-system testing

Quick Start

Run anti-pattern analysis to surface risky testing patterns: /shannon:testing-anti-patterns

Frequently Asked Questions about testing-anti-patterns

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

FAQPage Schema
How do I detect mock overuse in my test suite?

Mock overuse detection identifies when tests rely too heavily on mocks instead of verifying real code behavior. This Skill analyzes your test suite to surface mock-centric assertions, quantify their prevalence, and recommend shifts toward real-system testing to ensure tests reflect actual production behavior.

What are testing anti-patterns and why should I prevent them?

Testing anti-patterns are risky testing practices like excessive mocking, test-only production methods, and incomplete mock setups that hide real bugs. Preventing them ensures your tests validate actual behavior rather than false positives, improving test reliability across frontend and backend suites.

Can I automate anti-pattern detection in my test pipeline?

Yes, this Skill integrates anti-pattern detection directly into test pipelines and code reviews for continuous monitoring. It provides quantitative scoring and actionable recommendations to enforce real-behavior verification automatically during test authoring and quality checks.

How do I identify test-only methods in production code?

Test-only production methods are code paths added solely to satisfy mocks, creating untested branches in production. This Skill catalogs and flags these patterns with prescriptive fixes to eliminate unnecessary production changes and ensure tests exercise genuine code paths.

What's the difference between mock testing and real-system testing?

Mock testing isolates units but can mask integration failures; real-system testing verifies actual behavior across dependencies. This Skill enforces real-system approaches by detecting mock overuse and quantifying anti-patterns so tests catch real-world failures before production.

Does this work with frontend and backend test suites?

Yes, anti-pattern detection applies across both frontend and backend test suites. The Skill analyzes test patterns regardless of technology stack to surface mock-centric assertions, test-only methods, and incomplete mocks in any environment.