agentleFS
Sign inStart free
autonomous-aiautonomous-ai/Physical-AI-Operating-System/.cursor/rules/testing.mdc

Physical-AI-Operating-System / rules

Cursor rule552 starsChanged 8 months agoApache-2.0View on GitHub

Testing conventions

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this testing.mdc into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Test files live next to the code they test: internal/led/engine_test.go

    line 10
  2. Very specific:

    Use standard testing package — no external test frameworks

    line 11
  3. Very specific:

    Test function names: TestMethodName_Scenario (e.g.

    line 26
  4. Very specific:

    Use t.Errorf or t.Fatalf — not panic or log.Fatal in tests

    line 27
  5. Distinctive:

    Test exported behavior, not internal implementation details

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
testing.mdc
---
description: Testing conventions
alwaysApply: true
---

# Testing Rules

## Test Files

- Test files live next to the code they test: `internal/led/engine_test.go`
- Use standard `testing` package — no external test frameworks
- Table-driven tests preferred for multiple cases

## Running Tests

```bash
go test ./...                    # All tests
go test ./internal/led/...       # Single package
go test -run TestFunctionName    # Single test
go test -v ./...                 # Verbose output
go test -race ./...              # Race detector
```

## Conventions

- Test function names: `TestMethodName_Scenario` (e.g. `TestEncodeColors_BufferLength`)
- Use `t.Errorf` or `t.Fatalf` — not `panic` or `log.Fatal` in tests
- Test exported behavior, not internal implementation details
- Mock external dependencies (shell commands, hardware), not internal services

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free