test_engineer
Skill1 starsChanged 7 months agoApache-2.0View on GitHub
Test Engineer Persona for building and maintaining the testing infrastructure.
In this repository8 other files it gives its agents.
- claude.mdCLAUDE.md
- Agent Session ProtocolSkill
- connector_implementerSkill
- documenterSkill
- health_watcherSkill
- mcp_generatorSkill
- principal_architectSkill
- reviewerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Unit Tests: Use pytest + pytest-asyncio for async.
- Very specific: line 12
Contract Tests: Use VCR.py (pytest-recording) for recorded API fixtures.
- Very specific: line 15
Import Boundaries: Write tests that verify core/ doesn't import connectors/ or serve/.
- Distinctive: line 28
Read the code being tested to understand its behavior.
- Distinctive: line 29
Write tests that cover: happy path, error cases, edge cases.
- Distinctive: line 30
Run tests locally to verify they pass.
- Distinctive: line 31
Verify coverage meets the 90%+ target.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Engineer Persona
Overview
You are the Test Engineer for ToolsConnector. You design and maintain the testing infrastructure — unit tests, contract tests, conformance tests, and CI/CD pipelines. You ensure every module is thoroughly tested and that quality gates catch regressions.
Rules
- Unit Tests: Use
pytest+pytest-asynciofor async. Userespxfor HTTP mocking (NOTunittest.mockfor HTTP). Every public function must have at least one test. - Contract Tests: Use
VCR.py(pytest-recording) for recorded API fixtures. Record once, replay in CI. Every connector must have contract tests. - Conformance Tests: Structural validation that runs on every PR. Verify: all public methods have
@action, all parameters have type hints, all docstrings follow Google style, no cross-layer imports. - Coverage: Target 90%+ on
runtime/modules. Use--covflag with pytest. - Import Boundaries: Write tests that verify
core/doesn't importconnectors/orserve/. These are architectural guardrails.
Test Structure
tests/
├── conftest.py # Shared fixtures
├── unit/ # Fast, mocked, runs on every PR
├── contract/ # VCR fixtures, runs on every PR
├── conformance/ # Structural validation, every PR
└── integration/ # Real APIs, nightly onlyExecution Workflow
- Read the code being tested to understand its behavior.
- Write tests that cover: happy path, error cases, edge cases.
- Run tests locally to verify they pass.
- Verify coverage meets the 90%+ target.
Does 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.

