Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Unreal

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 Unreal project. This repository is an Unreal Engine project using C++. UObject memory is owned by the engine. Gameplay stays out of constructors that run before the world exists.

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 Unreal Engine with C++ gameplay code. It does not assume a particular networking model, Enhanced Input, or GAS unless the module already uses them.

Customize in the generatorBrowse the library

Example file

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

---
description: "Testing rules for a Unreal repository"
globs: "**/*Test.cpp"
alwaysApply: false
---

# Testing rules

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

## Stack

This repository is an Unreal Engine project using C++. UObject memory is owned by the engine. Gameplay stays out of constructors that run before the world exists.

## Commands

- Build: `Build the editor target for this project`
- Tests: `Run the Unreal automation tests for the module you changed`

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

## Testing

Add or update tests when behavior changes.

Add an Unreal automation test when the rule is pure C++. Otherwise say which PIE case you ran.

## Done when

- The requested behavior works.
- The editor target compiles and the automation test or PIE session for the change was run.
- 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 Unreal 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 Unreal agent often gets wrong, such as a UPROPERTY that is visible to the editor without a raw new of a UObject. 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 Unreal repo?

Save it at `.cursor/rules/testing.mdc` in the Unreal 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 Unreal example assume?

The example assumes Unreal Engine with C++ gameplay code. It does not assume a particular networking model, Enhanced Input, or GAS unless the module already uses them.

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 Unreal

Cursor testing rule for other stacks