testing-quality-standards
Set testing benchmarks with tiered coverage targets (60–95%+) and quality checklists spanning structure, maintainability, and reliability. Includes anti-patterns, best practices, and assertion levels for LLM-interpreted content to guide test validation across your projects.
Testing Quality Standards defines coverage thresholds and quality metrics for establishing test gates across your test suite.
AI-generated summary based on this skill's SKILL.md
Install
athola/claude-night-market/testing-quality-standards · repository language: Python
git clone https://github.com/athola/claude-night-market
cp -r claude-night-market/plugins/leyline/skills/testing-quality-standards ~/.claude/skills/testing-quality-standardsnpx skillfed install athola/claude-night-market/testing-quality-standardsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What test coverage thresholds does testing-quality-standards recommend?
testing-quality-standards recommends tiered coverage targets ranging from 60% to 95%+ depending on project type and criticality. The skill provides benchmarks for different scenarios: foundational projects start at 60%, standard applications target 80%, and mission-critical systems aim for 90–95%+. These thresholds serve as quality gates to validate that your test suite meets organizational standards and catches regressions effectively.
How can I establish quality gates for my test suites?
testing-quality-standards guides you through setting up quality gates by combining coverage thresholds with a multi-faceted checklist covering structure, maintainability, and reliability. The framework helps you define assertion levels, validate test organization, prevent flakiness, and document standards. You can configure pytest and other tools to enforce these gates automatically, ensuring consistent quality across your projects.
What are common anti-patterns in unit testing and how do I avoid them?
testing-quality-standards identifies key anti-patterns such as brittle assertions, inadequate test isolation, and poor naming conventions. The skill teaches best practices to counter these: use descriptive test names, maintain clear setup/teardown patterns, avoid over-mocking, and keep tests focused on single responsibilities. Learning these patterns helps you build reliable, maintainable test suites that scale with your codebase.
How should I define assertion levels for LLM-interpreted markdown testing?
testing-quality-standards provides guidance on content assertion levels specifically for LLM-interpreted markdown testing. The framework helps you calibrate assertion strictness—from lenient (semantic matching) to strict (exact content validation)—based on your use case. This ensures your tests validate meaningful behavior without brittleness when working with language model outputs.
What quality metrics should I implement for test suite organization?
testing-quality-standards recommends implementing metrics across test organization, maintainability, and reliability. Key metrics include coverage percentage, test execution time, flakiness rates, and assertion clarity. The skill provides a quality checklist to assess structure (logical grouping, naming), maintainability (readability, DRY principles), and reliability (isolation, determinism) to guide continuous improvement of your test infrastructure.
What are the testing best practices and metrics for reliable test suites?
testing-quality-standards emphasizes reliable testing practices including proper test isolation, deterministic execution, and flakiness prevention. Best practices cover test organization, clear naming, appropriate assertion levels, and documentation. Metrics to track include coverage thresholds, test execution time, and failure patterns. Combined, these practices and metrics create a validation framework that ensures your test suite remains trustworthy and maintainable as your project grows.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
Coverage Thresholds
| Level | Coverage | Use Case
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 4 files
plugins/leyline/skills/testing-quality-standards/SKILL.md
plugins/leyline/skills/testing-quality-standards/modules/anti-patterns.md
plugins/leyline/skills/testing-quality-standards/modules/best-practices.md
plugins/leyline/skills/testing-quality-standards/modules/content-assertion-levels.md