Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Django

A Cursor `.mdc` rule can attach only when you touch tests. This variant keeps testing policy out of the always-on project rule so day-to-day edits stay quieter. This copy is written for a Django project. This repository is a Django project. Models, views, and templates follow the apps that already exist. Schema changes go through migrations, and you do not skip migrations.

The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.

The example assumes Django with the ORM and migrations. It does not assume Django REST framework. If DRF is installed, use serializers. Otherwise stay with the views and forms the project already uses.

Customize in the generatorBrowse the library

Example file

Balanced strictness, readable style, pragmatic tests. Download name: testing.mdc

---
description: "Testing rules for a Django repository"
globs: "**/test_*.py"
alwaysApply: false
---

# Testing rules

Attach these rules when editing tests in this Django repository.
The always-on project rule still lives in `.cursor/rules/project.mdc`. This file does not repeat it.

## Stack

This repository is a Django project. Models, views, and templates follow the apps that already exist. Schema changes go through migrations, and you do not skip migrations.

## Commands

- Dev server: `python manage.py runserver`
- Migrations: `python manage.py makemigrations && python manage.py migrate`
- Tests: `python manage.py test`
- Check: `python manage.py check`

Use the script the repo already defines when it differs from the command above.

## Testing

Add or update tests when behavior changes.

Use Django's test client or pytest-django, matching the repo. Cover the view status and one model constraint.

## Done when

- The requested behavior works.
- `python manage.py check` is clean and the migration list matches the model change you made.
- The diff stays inside the task.
- You list anything you could not run.

Add it to the project

  1. 01

    Copy a starting file

    Copy the example Cursor testing rule on this page, or open the generator if you want different testing, strictness, or comment rules.

  2. 02

    Save it at .cursor/rules/testing.mdc

    Save it at `.cursor/rules/testing.mdc` in the Django repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

  3. 03

    Start a fresh agent session

    Rules files are read when a session starts. A chat that is already open may still be using the old instructions.

  4. 04

    Give it one small task

    Ask for one change a Django agent often gets wrong, such as a model change that includes the migration, not only the model field. If it ignores the file, confirm the path and start a new session.

Questions about this file

Where do I put Cursor testing rule in a Django repo?

Save it at `.cursor/rules/testing.mdc` in the Django repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

Which tools read this Cursor testing rule?

Cursor loads `.cursor/rules/testing.mdc` when a file matches its globs. It does not replace `project.mdc`. Keep the always-on rule for stack conventions.

What does the Django example assume?

The example assumes Django with the ORM and migrations. It does not assume Django REST framework. If DRF is installed, use serializers. Otherwise stay with the views and forms the project already uses.

Does VibeSpell upload my repository?

No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.

Other files for Django

Cursor testing rule for other stacks