ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

testing-quality-standards

Cross-plugin testing quality metrics, coverage thresholds, and anti-patterns

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/athola/nm-leyline-testing-quality-standards
Or

Night Market Skill — ported from claude-night-market/leyline. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

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

LevelCoverageUse Case
Minimum60%Legacy code
Standard80%Normal development
High90%Critical systems
detailed95%+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:

  • Anti-Patterns - Common testing mistakes with before/after examples
  • Best Practices - Core testing principles and exit criteria
  • Content Assertion Levels - L1/L2/L3 taxonomy for testing LLM-interpreted markdown files

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

Metadata

Author@athola
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-athola-nm-leyline-testing-quality-standards": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.