do-test-fixture-data-management

do-test-fixture-data-management is a cursor rule for Cursor from FeatureFactory-io/mimir. It costs 0 tokens per session (663 once invoked), scanned A, original, Apache-2.0.

A testing rule for storing end-to-end test data in JSON fixtures. End-to-end tests check a complete user flow, while fixtures are prepared data loaded before the tests run.

In plain words
What is it for?
Use it to add users, tokens, and application records to an e2e seed file, either by exporting them from Django or writing the JSON directly.
Why use it?
It keeps tests predictable and avoids changing the database while each test is running. It also gives the whole test suite one clear place for its sample data.

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/featurefactory-io/mimir/do-test-fixture-data-management
Clone the repo
git clone --depth 1 https://github.com/FeatureFactory-io/mimir

Made for: Cursor.

Wrote 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.

agentmods badge for do-test-fixture-data-management

README.md
[![agentmods](https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-test-fixture-data-management.svg)](https://agentmods.dev/rules/featurefactory-io/mimir/do-test-fixture-data-management)
Your own site
<a href="https://agentmods.dev/rules/featurefactory-io/mimir/do-test-fixture-data-management"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-test-fixture-data-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 663 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.00663
Opus 5 $0.00000 $0.00331
Sonnet 5 $0.00000 $0.00133
Haiku 4.5 $0.00000 $0.00066

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

Security

Grade A, and why

do-test-fixture-data-management 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 4d 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/do-test-fixture-data-management.mdc · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rule: E2E Test Fixture Data Management

Core Principle

Think of e2e_seed.json like a test-suite-level setUp() method. All test data lives in fixtures. No ORM operations during test execution.

Adding Test Data to e2e_seed.json

1. Review Current Data

# Check what data already exists
cat tests/fixtures/e2e_seed.json | jq '.[].model' | sort | uniq -c

2. Add Authentication Token to Fixtures

// Add to tests/fixtures/e2e_seed.json
[
  // ... existing data ...
  {
    "model": "authtoken.token",
    "pk": 1,
    "fields": {
      "user": 1,
      "created": "2023-01-01T00:00:00.000Z",
      "key": "abcdef1234567890abcdef1234567890abcdef12"
    }
  }
]

3. Option A: Generate from Database

# Create the data you need in Django admin or shell
python manage.py shell
>>> from api.models import Intent
>>> Intent.objects.create(user_id=1, name="Test Intent", startag="TEST", motive="Testing")

# Export to fixture format
python manage.py dumpdata api.Intent --indent 2 >> new_data.json

# Merge into e2e_seed.json (manually or with jq)

4. Option B: Write JSON Directly

// Add to tests/fixtures/e2e_seed.json
[
  // ... existing data ...
  {
    "model": "api.intent",
    "pk": 99,
    "fields": {
      "user": 1,
      "name": "Test Scenario Intent",
      "startag": "TESTSCENARIO",
      "motive": "For testing specific scenario",
      "color": "#ff6b6b",
      "priority": 99,
      "active": true
    }
  }
]

5. Reference Known Data in Tests

# In your test, reference the pre-seeded data
def test_scenario(self, authenticated_page, base_url):
    app_url = base_url or "http://localhost:5173"
    intents_page = IntentsPage(authenticated_page, app_url)
    intents_page.goto()
    
    # Use known data from e2e_seed.json
    # User: denis.petelin (pk=1)
    # Intent: WORK (pk=1), TESTSCENARIO (pk=99)
    # Token: abcdef1234567890abcdef1234567890abcdef12
    
    # Verify authentication worked
    expect(authenticated_page.get_by_text("Add Intent")).to_be_visible()

Read the full file on GitHub · 95 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. 4d ago First seen · 95 lines · 0 tokens per session scan A 1f889b6808e6

Subscribe to this mod's changes

do-test-fixture-data-management is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 663 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.