testing-anti-patterns

Name: testing-anti-patterns
Availability: InStock
Author: notque

Identify and report test anti-patterns in Go, Python, and JavaScript suites.

415|44|Updated Mar 18, 2026

Search Tags:#testing #anti-patterns #refactoring #best-practices #unit-testing #integration-testing #test-quality

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill testing-anti-patterns-notque

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-anti-patterns
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/testing-anti-patterns
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill testing-anti-patterns-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identify and fix common testing mistakes across unit, integration, and E2E test suites. Use when tests are flaky, brittle, over-mocked, order-dependent, slow, poorly named, or providing false confidence. Do NOT use for writing new tests from scratch (use test-driven-development), refactoring architecture (use systematic-refactoring), or performance profiling without a specific test quality symptom.

Core Features & Use Cases

Identify anti-patterns in test code with file:line references.
Classify anti-patterns by severity and impact.
Provide before/after examples and concrete fixes.
Supply guidance for incremental refactoring without rewriting suites.

Quick Start

Scan your test suite to identify anti-patterns and start by fixing the highest-impact issues.

Frequently Asked Questions about testing-anti-patterns

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

FAQPage Schema

How do I identify flaky tests and order dependence in my test suite?▼

To identify flaky tests and order dependence, scan your test suite to detect anti-patterns with file:line references. It classifies issues by severity and impact, providing before/after examples and concrete fixes to improve test reliability across Go, Python, and JavaScript.

What are common test anti-patterns and how do I fix weak assertions?▼

Common test anti-patterns include over-mocking, brittle tests, and weak assertions. You can fix weak assertions by applying the provided before/after examples and concrete fixes, which guide incremental refactoring to improve test quality without completely rewriting your test suites.

Does this test anti-pattern detection work with Go, Python, and JavaScript?▼

Yes, this test anti-pattern detection works with Go, Python, and JavaScript test suites. It applies to unit, integration, and end-to-end tests, focusing on identifying flaky tests, order dependence, weak assertions, and other defined anti-patterns across these languages.

Can I incrementally refactor over-mocked and brittle tests without rewriting the whole suite?▼

Yes, you can incrementally refactor over-mocked and brittle tests without rewriting the entire suite. It supplies cross-referenced guidance for safe, incremental improvements, allowing you to target and fix the highest-impact issues first while maintaining existing test suite structure.

When should I not use a test anti-pattern scanner?▼

You should not use a test anti-pattern scanner when writing new tests from scratch, refactoring architecture, or performance profiling without a specific test quality symptom. It is designed specifically for identifying and fixing existing test mistakes like flaky, brittle, or over-mocked tests.