Validate HTTP test naming conventions
spec-naming-validatorsubagentsetup L1★0
st0o0/Schleusenwerk ↗What it does
Validate test file naming conventions
Best for
Enforcing consistent BDD-style test naming across multi-component C# test suites
Inputs
- · component folder paths (Http10/, Http2/, etc.)
- · optional specific files to check
Outputs
- · .txt report with errors/warnings, or stdout listing violations
Requires
- ·
Preconditions
TurboHTTP test project structure; post-Feature-040 convention rules known
Failure modes
- · False positives on pre-Feature-040 files
- · Rule 7 (async timeout) may need project adjustment
Trust signals
- · 9 detailed rules with examples
- · Integration with CI/CD quality gates documented