thoughtbot/factory_bot_rails

Factory Bot ♥ Rails

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on May 24th, 2010
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 376
Total Stargazers: 3,139 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.4 days
Mean response time: 82.2 days
90th percentile: 319.8 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 589 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (10)
  • feature (2)
  • good first issue (1)
  • open summit (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Factory Bot Rails is a Rails plugin that integrates Factory Bot, a fixtures replacement library for creating test data.

The problem it solves is the tedium of writing and maintaining test fixtures. Factory Bot Rails provides a Rails-specific integration layer that allows developers to define factories—reusable blueprints for creating model instances—directly within their Rails test suite. Rather than managing static fixture files, developers write factory definitions that can generate objects with various attributes and associations on demand, making tests more readable and maintainable.

Developers adopting this tool should understand that it works best in Rails projects where test data generation is a significant concern. It suits projects of any size but particularly benefits teams writing comprehensive test suites with complex model relationships. The tool integrates seamlessly with Rails conventions, automatically loading factory definitions from standard directories and working with Rails' testing infrastructure. It is most valuable when tests require flexible, dynamic object creation rather than static predefined data.

The project maintains steady engagement with its codebase, addressing issues and pull requests regularly. Development activity shows consistent responsiveness to community contributions and bug reports. The maintainers prioritize keeping the tool compatible with current Rails versions and Ruby standards. The project receives ongoing refinement rather than major architectural changes, reflecting a mature tool that has settled into a stable, well-defined purpose.