Nm Leyline Testing Quality Standards

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

Security Scan

The skill is an instruction-only testing standards document whose requirements and instructions are consistent with its stated purpose, with only minor metadata and operational notes to check before running tests.

Purpose & Capability

The name/description (testing quality standards) align with the content: coverage thresholds, anti-patterns, and assertion-level guidance. The skill requests no credentials, binaries, or installs, which is proportionate. Minor inconsistency: SKILL.md frontmatter claims version 1.8.2 while the registry metadata lists version 1.0.0 — this is likely a packaging/metadata mismatch rather than functional risk, but worth verifying.

Instruction Scope

SKILL.md and included modules are guidance and example tests. They reference running pytest (verification) and include example code that reads/parses skill/module files for content assertions. This is consistent with a test-quality tool, but be aware that executing 'pytest -v' will run whatever tests exist in the repository (i.e., arbitrary code execution within the test suite). The instructions do not request secrets or external endpoints beyond normal test tooling.

Install Mechanism

No install spec and no code files that would be fetched or executed at install time. Instruction-only skills are lowest-risk for install mechanism.

Credentials

The skill declares no required environment variables, credentials, or config paths. The sample validation code references paths inside the repo (skills/, agents/, modules/, commands/) which is appropriate for content assertions and consistent with the stated purpose.

Persistence & Privilege

The skill is not marked always:true and requests no system privileges. It does not modify other skills or system configuration. Autonomous invocation is enabled by default on the platform but is not combined here with broad privileges or credential access.

Scan Findings in Context

[no-regex-findings] expected: The static regex-based scanner had nothing to analyze because this is an instruction-only skill with no code files. That absence of findings is expected but not evidence of safety — the runtime risk comes from executing tests (pytest) in the target repo.

Assessment

This skill is primarily documentation and test guidance and appears coherent with its stated purpose. Before installing or running anything: 1) Note the metadata mismatch (SKILL.md version 1.8.2 vs registry 1.0.0) and confirm you have the intended release. 2) Inspect the test files and modules locally — running 'pytest -v' will execute code in the repository, so run tests in an isolated environment (container, disposable VM, or CI runner) to avoid unintended side effects. 3) Review the content-assertion examples (they parse repo files and assert on content); ensure those assertions won't read or transmit sensitive files in your environment. 4) Because the skill can be invoked by agents, limit autonomous invocation if you don't want agents to run test suites automatically. If you want stronger assurance, request the author/publisher to resolve the version metadata mismatch and provide a short changelog or provenance for this skill.

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

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:

• 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