Using FactoryBot
Engineering
Our engineering is underpinned by principles that celebrate both the integrity of code and the ambition to innovate. This manifesto champions excellence, advocates for the adoption of cutting-edge technologies, and fosters an environment of continuous intellectual growth.
On Code Quality
On Cutting-Edge Technologies
On Starting Projects
On Security
Our Tech Stack
On Design Thinking
On Workstation Setup
On Elixir
On Frontend
On Toolchain
On Rails
Use syntax helpers
Always include the syntax helpers in your tests. This makes build and create available in your test cases.
# rails_helper.rb
config.include FactoryBot::Syntax::Methods
Build, don't create
Prefer build over create, if you can get away with it. This can lead to faster tests. Avoid build_stubbed.
Use sequences
Never hard-code emails and similar fields that must be unique. Use sequence when possible.
factory :user do
sequence(:email) { |i| "user-#{i}@email.com" }
...
end
Write reusable sequences when possible
Place reusable sequences in a separate file.
# spec/factories/factory_sequences.rb
FactoryBot.define do
sequence(:uid) { |i| SecureRandom.uuid }
sequence(:email) { |i| "user-#{i}@email.com" }
end
factory :admin do
uid
email
end
factory :client do
uid
email
end
Traits
Traits can be used to remove duplication, but use them sparingly.
Always update
Make sure that factories are always up to date.
Simple defaults
Always provide the simplest defaults for your factories. Prefer to only add fields that are validated such that records built through the factory will pass validation. Other fields would only serve to make for confusing future tests and make it difficult to test default behavior.
class Profile < ActiveRecord::Base
validates :name, presence: true
validates :gender, inclusion: %w(male female)
end
factory :profile do
name "Jack Sparrow"
gender "male"
occupation "Pirate" # <- Don't
bio "Jack is a pirate lord of the seven seas." # <- Don't
end
Test your factories
Test your factories. This will make it easy to spot any factories that may be out of date.
EXCLUDED = [:factories, :to, :exclude, :if, :any]
FactoryBot.factories.map(&:name).each do |factory_name|
next if EXCLUDED.include?(factory_name)
it "the #{factory_name} factory is valid" do
expect(build factory_name).to be_valid
end
end
Insights, Forward Thinking.
Dive into our latest musings and discoveries. Our blog is a window to the trends shaping the future and reflections on our journey.
Exploring horizons, sharing insights.
Innovation at the Intersection: How Diverse Cultures are Shaping Tech
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
Agile Evolution: Adapting Strategy for Fast-Paced Tech Development
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
Designing for Scalability: Engineering Challenges and Strategies
From building minimum-viable-products to managing existing products, we created product teams and managed them within Mashup Garage. We work with companies of different stages and together we built products and launched them.
Connect.
Mashup Garage, a premier software development team, specialises in crafting exceptional products for startups and enterprises. With expertise in React, Elixir/Phoenix, and Ruby on Rails, we deliver solutions that meet your unique needs. Our mission is to bring value backed by decades of technical expertise and global co-founding experience.
What do you need help with?
Build a project
Build a team
Consult
Speak to someone
Expect a guaranteed response from us in 1-2 business days.
United Kingdom
London
Islington, London
+44 738 777 3405
LDN
Philippines
Manila
3F Topy IV Building, 3 Economia Road, Bagumbayan, Quezon City, 1110
+63 917 3084089
MNL