testing-factory_bot

A testing rule that uses FactoryBot, a Rails tool for creating test records from reusable definitions, instead of fixed database fixtures.

In plain words
What is it for?
Use it when setting up Rails test data, defining users or other records, adding traits for variations, or generating unique values.
Why use it?
It makes test data easier to reuse and vary while keeping it aligned with database rules.

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/wintermeyer/cursor-rails-rules/testing-factory_bot
Clone the repo
git clone --depth 1 https://github.com/wintermeyer/cursor-rails-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,382 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.01382
Opus 5 $0.00000 $0.00691
Sonnet 5 $0.00000 $0.00276
Haiku 4.5 $0.00000 $0.00138

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

Security

Grade A, and why

testing-factory_bot 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 2d 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/testing-factory_bot.mdc · 251 lines

How it starts

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

FactoryBot Standards

Use FactoryBot rather than fixtures in Rails tests. Install the factory_bot gem if it is not already included in the Gemfile.

Factory Organization

  1. Directory Structure
test/factories/
├── users.rb
├── posts.rb
├── comments.rb
└── traits/
    ├── addressable.rb
    └── timestampable.rb
  1. Basic Factory Structure
# test/factories/users.rb
FactoryBot.define do
  factory :user do
    first_name { Faker::Name.first_name }
    last_name { Faker::Name.last_name }
    email { Faker::Internet.email }
    password { "password123" }

    trait :admin do
      role { "admin" }
      admin_since { Time.current }
    end

    trait :inactive do
      active { false }
      deactivated_at { Time.current }
    end

    factory :admin_user do
      role { "admin" }
      admin_since { Time.current }
    end
  end
end

Best Practices

  1. Factory Design
  • Keep factories minimal
  • Use traits for variations
  • Use sequences for unique values
  • Follow database constraints
  1. Naming Conventions
  • Use singular form for factory names
  • Use descriptive trait names
  • Prefix dynamic values with with_
  • Use verb past tense for states
  1. Data Generation
  • Use Faker for realistic data
  • Use sequences for unique fields
  • Use associations when needed
  • Keep data consistent
  1. Performance
  • Avoid unnecessary associations
  • Use build instead of create when possible
  • Use traits to minimize database hits
  • Clean up test data properly

Common Patterns

  1. Associations
# test/factories/posts.rb
FactoryBot.define do
  factory :post do
    association :user
    title { Faker::Lorem.sentence }
    content { Faker::Lorem.paragraphs(number: 3).join("\n\n") }

    trait :with_comments do
      after(:create) do |post|
        create_list(:comment, 3, post: post)
      end
    end

    trait :published do
      published_at { Time.current }
      status { "published" }
    end
  end
end

# test/factories/comments.rb
FactoryBot.define do
  factory :comment do
    association :user
    association :post
    content { Faker::Lorem.paragraph }
  end
end

Read the full file on GitHub · 251 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. 2d ago First seen · 251 lines · 0 tokens per session scan A 3751ec4fa815

Subscribe to this mod's changes

testing-factory_bot is a cursor rule published in the GitHub repository wintermeyer/cursor-rails-rules (37 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,382 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.