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.
npx agentmods add rules/rygwdn/obsidian-mcp-plugin/testing-best-practicesgit clone --depth 1 https://github.com/rygwdn/obsidian-mcp-pluginWrote 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/rygwdn/obsidian-mcp-plugin/testing-best-practices)<a href="https://agentmods.dev/rules/rygwdn/obsidian-mcp-plugin/testing-best-practices"><img src="https://agentmods.dev/badge/rules/rygwdn/obsidian-mcp-plugin/testing-best-practices.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00426 |
| Opus 5 | $0.00000 | $0.00213 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
testing-best-practices 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 5d 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 Best Practices
Unit Tests (test/)
Tests should use real implementations instead of mocks whenever possible. The test/resources.test.ts file serves as a good example of this approach.
Key testing principles:
- Set up test environment with realistic data
- Use MockApp to simulate Obsidian's API
- Avoid vi.mock() for any of the code under test
Run unit tests with: npm run test
E2E Tests (e2e/)
End-to-end tests run against a real Obsidian instance using Playwright in a Docker container.
Structure
e2e/tests/- Playwright test filese2e/helpers/mcp-client.ts- MCP SDK client wrapper for testinge2e/helpers/obsidian.ts- Obsidian launch and management helperse2e/test-vault/- Test vault with sample data
MCP Client
E2E tests use the official MCP SDK (@modelcontextprotocol/sdk) with StreamableHTTPClientTransport:
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { createMcpClient } from "../helpers/mcp-client";
const client = await createMcpClient();
const result = await client.listTools();
await client.close();
Running E2E Tests
E2E tests require Docker/Podman:
# Build the test container
podman build -t obsidian-mcp-e2e -f e2e/Dockerfile .
# Run all e2e tests
podman run --rm --ipc=host -v $(pwd)/e2e/test-results:/app/e2e/test-results obsidian-mcp-e2e
# Run specific test
podman run --rm --ipc=host obsidian-mcp-e2e npm run test:e2e -- --grep "should list"
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.
- 5d ago First seen · 52 lines · 0 tokens per session scan A 8a740a9c04a2
testing-best-practices is a cursor rule published in the GitHub repository rygwdn/obsidian-mcp-plugin (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 426 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-31.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.
do-runner
Use the following runners.