Skip to main content
AI/MLathola

testing-quality-standards

Defines testing quality metrics, coverage thresholds, and anti-patterns. Use when establishing test gates or validating a test suite's coverage targets.

Stars
294
Source
athola/claude-night-market
Updated
2026-05-30
Slug
athola--claude-night-market--testing-quality-standards
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/athola/claude-night-market/HEAD/plugins/leyline/skills/testing-quality-standards/SKILL.md -o .claude/skills/testing-quality-standards.md

Drops the SKILL.md into .claude/skills/testing-quality-standards.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Testing Quality Standards

Shared quality standards and metrics for testing across all plugins in the Claude Night Market ecosystem.

When To Use

  • Establishing test quality gates and coverage targets
  • Validating test suite against quality standards

When NOT To Use

  • Exploratory testing or spike work
  • Projects with established quality gates that meet requirements

Table of Contents

  1. Coverage Thresholds
  2. Quality Metrics
  3. Detailed Topics

Coverage Thresholds

Level Coverage Use Case
Minimum 60% Legacy code
Standard 80% Normal development
High 90% Critical systems
detailed 95%+ Safety-critical

Quality Metrics

Structure

  • Clear test organization
  • Meaningful test names
  • Proper setup/teardown
  • Isolated test cases

Coverage

  • Critical paths covered
  • Edge cases tested
  • Error conditions handled
  • Integration points verified

Maintainability

  • DRY test code
  • Reusable fixtures
  • Clear assertions
  • Minimal mocking

Reliability

  • No flaky tests
  • Deterministic execution
  • No order dependencies
  • Fast feedback loop

Detailed Topics

For implementation patterns and examples:

Integration with Plugin Testing

This skill provides foundational standards referenced by:

  • pensive:test-review - Uses coverage thresholds and quality metrics
  • parseltongue:python-testing - Uses anti-patterns and best practices
  • sanctum:test-* - Uses quality checklist and content assertion levels for test validation
  • imbue:proof-of-work - Uses content assertion levels to enforce Iron Law on execution markdown

Reference in your skill's frontmatter:

dependencies: [leyline:testing-quality-standards]

Verification: Run pytest -v to verify tests pass.

Troubleshooting

Common Issues

Tests not discovered Ensure test files match pattern test_*.py or *_test.py. Run pytest --collect-only to verify.

Import errors Check that the module being tested is in PYTHONPATH or install with pip install -e .

Async tests failing Install pytest-asyncio and decorate test functions with @pytest.mark.asyncio