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/microsoft/data-formulator/backend-test-conventionsgit clone --depth 1 https://github.com/microsoft/data-formulatorWhat 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.01096 |
| Opus 5 | $0.00000 | $0.00548 |
| Sonnet 5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
backend-test-conventions 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Test Conventions
File Location & Naming
- Place tests under
tests/backend/unit/,tests/backend/integration/,tests/backend/contract/, or by domain:tests/backend/routes/,tests/backend/errors/,tests/backend/agents/,tests/backend/data/,tests/backend/security/,tests/backend/auth/,tests/backend/knowledge/. - Name files
test_<feature_or_module>.pywith descriptive snake_case names. - Shared test data goes in
tests/backend/fixtures/.
File Structure
"""One-paragraph summary of what is being tested and why.
Background
----------
Brief context about the feature or bug fix these tests validate.
"""
from __future__ import annotations
import pytest
pytestmark = [pytest.mark.backend]
Conventions
- Always add
pytestmark = [pytest.mark.backend]at module level. - Group related tests in classes prefixed with
Test(e.g.TestStripImageBlocks). - Use
pytest.mark.parametrizefor data-driven tests instead of writing repetitive cases. - Use
pytest.fixture()for shared setup; keep fixtures close to where they are used. - Unit tests must not depend on Flask, network, or external services.
- Mock external calls with
unittest.mock.patch/MagicMock; never make real API calls. - Each test function should verify one behavior and have a clear name:
test_<what>_<condition>.
Running Tests
- When running pytest, use
-q(quiet mode) instead of-v(verbose mode) for cleaner output. - Preferred:
python -m pytest tests/backend/ -q - Avoid:
python -m pytest tests/backend/ -v 2>&1
Error Handling Test Requirements
Application errors return HTTP 200 with status: "error" in the body.
Only auth errors (AUTH_REQUIRED/AUTH_EXPIRED → 401, ACCESS_DENIED → 403) and
uncontrolled transport failures (404/413/500) use non-200.
When adding a new route or modifying error handling, include tests for:
- AppError scenarios — verify HTTP 200 + correct
ErrorCodein body:def test_missing_table_returns_error(): with app.test_client() as client: resp = client.get('/api/tables/nonexistent') assert resp.status_code == 200 # application error → always 200 data = resp.get_json() assert data["status"] == "error" assert data["error"]["code"] == "TABLE_NOT_FOUND"
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.
- 2d ago First seen · 124 lines · 0 tokens per session scan A caab27bf5c0a
backend-test-conventions is a cursor rule published in the GitHub repository microsoft/data-formulator (17,048 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,096 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.