testing

Testing rules for this project, covering integration tests, adapter round trips, MCP behavior, error cases, file paths, and generated file contents.

In plain words
What is it for?
Adding or updating Rust tests for adapters, MCP features, error handling, generated files, and changes to output locations.
Why use it?
They make tests check both what files are created and what they contain, reducing the chance that format or path changes silently break users.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/maxgfr/conforme/testing
Clone the repo
git clone --depth 1 https://github.com/maxgfr/conforme

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 107 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00107
Opus 5 $0.00000 $0.00053
Sonnet 5 $0.00000 $0.00021
Haiku 4.5 $0.00000 $0.00011

Measured yesterday against content hash a045e55c7861, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing 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 yesterday.

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.

.cursor/rules/testing.mdc · 13 lines

What it actually says

  • Integration tests use assert_cmd + tempfile crates
  • Each adapter must have round-trip tests in tests/roundtrip.rs
  • MCP format tests belong in src/mcp.rs unit tests
  • Error case tests go in tests/error_cases.rs
  • Always assert on file paths AND content (not just existence)
  • When changing an output path (e.g. MCP location), update ALL tests that reference it
Changes

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.

  1. yesterday First seen · 13 lines · 0 tokens per session scan A a045e55c7861

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository maxgfr/conforme (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 107 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.