Testing rules for checking utility functions, calculations, validations, edge cases, and important gameplay behavior. Tests use Arrange, Act, Assert: prepare data, run the code, and check the result.

Use them to decide what needs tests, structure Unreal C++ tests, and name test cases consistently.

They help catch bugs and regressions while avoiding tests for simple accessors, wrappers, and generated code.

testing — Cursor rule by Stramp

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/stramp/lost-mines-phandelver/testing

Clone the repo

git clone --depth 1 https://github.com/Stramp/Lost-Mines-Phandelver

Made for: Cursor.

Per session 1,214 This file is loaded in full into every session.

When invoked 1,214 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5	$0.01214	$0.01214
Opus 5	$0.00607	$0.00607
Sonnet 5	$0.00243	$0.00243
Haiku 4.5	$0.00121	$0.00121

Measured yesterday against content hash 3f0068e9b371, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing 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 yesterday.

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/testing.mdc · 213 lines

How it starts

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

Testing Rules

Testing Principles

What to Test

ALWAYS test:

✅ Helper/utility functions (in Utils/)
✅ Pure functions (no side effects)
✅ Complex calculation logic
✅ Validations and edge cases
✅ Critical gameplay functions

Don't need to test:

❌ Simple Getters/Setters
❌ Simple wrappers of Unreal API
❌ Automatically generated code

Test Structure (AAA Pattern)

Arrange - Prepare data and context Act - Execute the function being tested Assert - Verify the result

TEST(ComponentHelpers, FindCharacterDataComponent_WithValidOwner_ReturnsComponent)
{
    // Arrange
    AActor* TestActor = NewObject<AActor>();
    UCharacterDataComponent* ExpectedComponent = NewObject<UCharacterDataComponent>(TestActor);
    TestActor->AddComponent(ExpectedComponent);

    // Act
    UCharacterDataComponent* Result = ComponentHelpers::FindCharacterDataComponent(TestActor);

    // Assert
    EXPECT_NE(Result, nullptr);
    EXPECT_EQ(Result, ExpectedComponent);
}

Test Naming

Format

TEST(<TestSuite>, <TestName>)

TestSuite

Name of the class/function being tested:

ComponentHelpers - For ComponentHelpers namespace functions
CharacterSheetComponent - For class methods
CharacterDataComponent - For class methods

TestName

Format: <Scenario>_<Condition>_<ExpectedResult>

Examples:

FindCharacterDataComponent_WithValidOwner_ReturnsComponent
FindCharacterDataComponent_WithNullOwner_ReturnsNullptr
FindCharacterDataComponent_WithoutComponent_ReturnsNullptr
CalculateFinalAttributes_WithBaseAttributes_CalculatesCorrectly

Mandatory Test Cases

For Helper Functions

ALWAYS test:

Valid case/happy path

TEST(ComponentHelpers, FindCharacterDataComponent_WithValidOwner_ReturnsComponent)

Nullptr/null input

TEST(ComponentHelpers, FindCharacterDataComponent_WithNullOwner_ReturnsNullptr)

Not found case

TEST(ComponentHelpers, FindCharacterDataComponent_WithoutComponent_ReturnsNullptr)

Read the full file on GitHub · 213 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.

yesterday First seen · 213 lines · 1,214 tokens per session scan A 3f0068e9b371

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 1,214 tokens to every session, about $0.0061 per session on Opus 5. 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-31.

Game development Testing

architecture

Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.

andvolodko/html5-game-editor · 49 tokens

testing