testing-quality-standards

athola's avatarfrom athola

Shared testing quality metrics and standards for cross-plugin use. Referencedby pensive:test-review and parseltongue:python-testing.Triggers: testing standards, quality metrics, coverage thresholds, test quality,anti-patterns, testing best practices, quality gatesUse when: evaluating test quality, setting coverage thresholds, identifyingtesting anti-patterns, establishing quality standardsDO NOT use when: simple scripts without quality requirements.Consult this skill when establishing testing quality standards.

⭐83stars🔀11forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The Testing Quality Standards skill provides a comprehensive framework for establishing and maintaining high-quality software testing practices. It offers standardized metrics, coverage thresholds (ranging from 60% to 95%+), and a robust checklist for structural integrity, maintainability, and reliability. By identifying common anti-patterns and promoting best practices, it ensures consistent testing quality across diverse development environments and complex plugin ecosystems.

Use Cases

  • 1. Establishing Coverage Benchmarks: Define clear coverage targets ranging from 60% for legacy systems to 95%+ for safety-critical applications to ensure code reliability.
  • 2. Quality Gate Implementation: Use the provided metrics and checklists as a quality gate during code reviews to verify test isolation, naming conventions, and error handling.
  • 3. Identifying Testing Anti-Patterns: Detect and rectify common testing mistakes such as flaky tests, order dependencies, and excessive mocking using the built-in reference modules.
  • 4. Standardizing Cross-Plugin Testing: Align multiple development teams or plugins under a unified set of quality standards to ensure interoperability and consistent performance.
nametesting-quality-standards
description|
Triggerstesting standards, quality metrics, coverage thresholds, anti-patterns
Cross-plugin testing quality metrics and standards. Referenced by pensivetest-review and parseltongue:python-testing.
Use whentest quality evaluation, coverage thresholds, quality standards
DO NOT use whensimple scripts without quality requirements
categoryinfrastructure
tags[testing, quality, standards, metrics]
dependencies[]
estimated_tokens400
patterns[coverage-thresholds, quality-metrics, anti-patterns]

Testing Quality Standards

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

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 for test validation

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