testing-standards
Skill1 starsChanged 7 months agoMITView on GitHub
Testing standards covering test coverage requirements, test synchronization principles, and test patterns. Use for all testing-related scenarios.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- DaveSkender/Stock.Indicatorstheir own version, first seen Oct 8, 2026
- alibaba/loongcollectortheir own version, first seen Oct 8, 2026
- maxyeh0817/Forgetheir own version, first seen Feb 25, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- alibaba/loongcollector★ 2.2ksame name
- DaveSkender/Stock.Indicators★ 1.3ksame name
- maxyeh0817/Forge★ 34same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- review-standards/CLAUDE.mdCLAUDE.md
- frontend-standardsSkill
- go-standardsSkill
- review-standardsSkill
- security-standardsSkill
- verifierSkill
The file
Files
Testing Standards
Overview
Testing standards covering coverage requirements, test synchronization, and patterns.
Modules
| Module | Description |
| Coverage | Coverage requirements and thresholds |
| Test Patterns | Table-driven tests and other patterns |
| Synchronization | Test synchronization with code changes |
Core Principles
| Principle | Canonical Location |
| Unit tests ≥70% | Coverage |
| Test synchronization | Sync |
| Table-driven tests | Patterns |
File Structure
testing-standards/
├── SKILL.md # Main entry
├── coverage.md # Coverage requirements
├── patterns.md # Test patterns
└── sync.md # Test synchronizationDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.