Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/prassanna-ravishankar/clearml-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/prassanna-ravishankar/clearml-mcp/testing-philosophy)<a href="https://agentmods.dev/rules/prassanna-ravishankar/clearml-mcp/testing-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/testing-philosophy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/prassanna-ravishankar/clearml-mcp/testing-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/testing-philosophy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
testing-philosophy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Testing Philosophy: Behavioral/Black-Box Testing
Core Principle
This project uses behavioral (black-box) testing instead of white-box testing. Tests focus on public API behavior and expected outcomes, not internal implementation details.
Testing Approach
✅ DO: Test Public API Behavior
- Test all public functions and their expected behaviors
- Focus on input/output relationships
- Test error conditions and edge cases
- Verify the complete user-facing contract
- Test with realistic data scenarios
❌ DON'T: Test Internal Implementation
- Avoid testing private methods directly
- Don't test internal data structures
- Don't mock internal implementation details
- Don't test "how" the code works, test "what" it does
Coverage Standards
- Target: 65%+ coverage (pyproject.toml
fail_under = 65) - Current: 69% coverage achieved through comprehensive behavioral tests
- Coverage should come from testing all public API paths, not from testing internals
Test Structure
Tests are organized in tests/test_clearml_mcp.py with:
- Comprehensive mocking of external dependencies (ClearML API)
- Behavioral verification of all public functions
- Edge case and error condition testing
- Real-world usage scenario simulation
Key Testing Files
- Main test suite: tests/test_clearml_mcp.py
- Coverage configuration: pyproject.toml
[tool.coverage.*] - CI testing: .github/workflows/ci.yml
This approach ensures tests remain stable when refactoring internal implementations while maintaining comprehensive verification of the public API contract.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 44 lines · 0 tokens per session scan A 93bf63a172f8
testing-philosophy is a cursor rule published in the GitHub repository prassanna-ravishankar/clearml-mcp (16 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
python-code-validator
Validate generated Python at every step, not once at the end.
testing-conventions
Testing conventions and techniques for Strapi MCP plugin.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.
incremental-validation
Validate frequently and early; find errors when they're small.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.