backend-test-conventions

Rules for writing backend Python tests with pytest, a tool for running automated tests.

In plain words
What is it for?
Naming and organizing test files, marking backend tests, sharing fixtures, testing repeated inputs, and mocking external calls.
Why use it?
They keep tests in predictable locations and prevent unit tests from depending on web frameworks, networks, or outside services.

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/microsoft/data-formulator/backend-test-conventions
Clone the repo
git clone --depth 1 https://github.com/microsoft/data-formulator

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,096 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.01096
Opus 5 $0.00000 $0.00548
Sonnet 5 $0.00000 $0.00219
Haiku 4.5 $0.00000 $0.00110

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

Security

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.

.cursor/rules/backend-test-conventions.mdc · 124 lines

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>.py with 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.parametrize for 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:

  1. AppError scenarios — verify HTTP 200 + correct ErrorCode in 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"
    

Read the full file on GitHub · 124 lines

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. 2d ago First seen · 124 lines · 0 tokens per session scan A caab27bf5c0a

Subscribe to this mod's changes

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.