factory_bot_rails
factory_bot
Our great sponsors
factory_bot_rails | factory_bot | |
---|---|---|
8 | 30 | |
3,036 | 7,875 | |
0.6% | 0.2% | |
7.1 | 7.8 | |
about 1 month ago | 12 days ago | |
Gherkin | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
factory_bot_rails
-
Test Driving a Rails API - Part Two
While we’re at it, let's add a couple of other gems we’ll need for our test environment: factory_bot_rails is a fixtures replacement and generates test model instances. faker is handy for generating fake strings of data to be used in tests. Add those gems to the development and test group of your Gemfile:
-
How to Use Shoulda Matchers with RSpec for Ruby on Rails
Factory Bot Rails
-
How to Setup RSpec on a Rails Project
rspec-rails factory_bot_rails faker
-
factory_bot_rails_seeder: a gem to mass generate factories for your models
Hey all, just published a simple gem to mass generate FactoryBot factories for existing projects. Someone had this issue on GitHub (https://github.com/thoughtbot/factory_bot_rails/issues/404). I failed to build it in a nice way within the main gem, but wanted to get a solution out there for people who might be in need. I had to get some legacy codebases up to speed in the past, and this would have been useful. Cheers! https://github.com/FanaHOVA/factory_bot_rails_seeder
-
ActiveStorage, Ruby on Rails 7, GraphQL and RSpec
I use FactoryBot for creating the factory, for stubbing the factory. My factory is containing an image that has to be uploaded and attached as doc every time a factory created:
-
It really be like that though
Here is some real Gherkin from the Factory Bot Rails gem source code on GitHub:
- Como configurar ambiente de testes em Ruby on Rails com RSpec
-
10 Signs of a good Ruby on Rails Developer
If your are using gems like faker , factory_bot_rails and database_cleaner to create and clean test records then creating unnecessary records can cost you time and speed.
factory_bot
-
Show HN: Factory-JS – TypeScript dummy object generator for testing
I made Factory-js inspired by factory-bot (https://github.com/thoughtbot/factory_bot), supports Prisma and Drizzle ORM and more. TypeScript is now widely used in both backend and frontend, but there is no de facto standard factory library. I'm developing a web application using Prisma, trpc, and nextjs, but I was struggling with how to write more beautiful and readable back-end tests. That's why I made factory-js.
-
Metaprogramming in Ruby: Advanced Level
factory_bot: A fixtures replacement
-
Seeding the DB: Best approach?
Not sure if you want the execution speed to be faster, or the development speed. If it's development, you can use FactoryBot in a script to generate data easily once you have your factories set up.
-
How could I prevent resetting the database during the test?
For instance, thoughtbot/factory_bot.
-
You can’t bribe, threaten, or feed people to get them back in the office
> if you're a bunch of tool makers and you all know your audience of tool users then there's no benefit at all to have someone offended by the word "tool" in your workforce.
It kinda reminds me of the factorygirl -> factorybot [0] story. It was a cute enough name for a technical tool that plays nice among bros, and down the line you end up renaming your package and deal with the drama.
On brand image, I get your point. I think the corporations doing it best tend to juggle with multiple brands and segment their market accordingly. Then yes, an homogeneous, single focus brand will be more valuable, as it also help to push people outside of the target to your other brands.
[0] https://github.com/thoughtbot/factory_bot/wiki
-
rspec testing on Windows.
Not sure I follow why this question is related to an OS like Windows, but when it comes to RSpec testing with different users, I would use Factory Bot and define a User Factory and add Traits such as Admin & Non Admin and use them in specs with their pre-defined attributes to what they can access based on your User Model and call them within the specs.
-
How to optimize factory creation.
The factory-bot gem is used in almost in all of our spec files and it make our set up much more easier than when we use fixtures. Here is the tradeoff, the easier the gem is to use, the more likely you’ll end up with some pain to control its usage. And when the times come to tackle slow tests, the best bet you can take is to start digging into you factories because it’s likely they are the primary reason why your test suite is slowing down
-
Efate Test Generator Series: Extending the library
Efate is actually the second test fixture library I've written and there were several lessons I learned after using the first iteration for several years myself. The first version was influenced a great deal by factor_girl (called factory_bot now), with a heavy dependency on strings to define and create the fixtures. It also wasn't very modular. You couldn't just import a specific fixture, you had to bring in the whole library. And it wasn't very extensible, if you needed to define custom behavior for how a field should be created, it wasn't very pretty.
-
Get help from thoughtbot for free (mentoring / office hours)
I work at thoughtbot, you might know us for our open source work like administrate, factory_bot or shoulda-matchers.
-
Gnarly Learnings From June 2022
As we continue to level-up our skillsets as developers in Rails, the utility of POROs (Plain Old Ruby Objects) becomes more apparent and appealing. Sometimes, the business object(s) you create do not require persistent storage to a database and are, therefore, outside of the scope of an ORM (Object Relational Mapper) like ActiveRecord. But how do we maintain simplicity in our test suite and continue to leverage helpful testing libraries like FactoryBot without one? This instructional article explores how to implement factories for POROs including common pitfalls, building nested resources, and factory linting.
What are some alternatives?
faker - A library for generating fake data such as names, addresses, and phone numbers. [Moved to: https://github.com/faker-ruby/faker]
Fabrication - This project has moved to GitLab! Please check there for the latest updates.
Whenever - Cron jobs in Ruby
faker - A library for generating fake data such as names, addresses, and phone numbers.
rspec-rails - RSpec for Rails 6+
ffaker - Faker refactored.
SimpleCov - Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites
Machinist - Fixtures aren't fun. Machinist is.
gf-core - Grammatical Framework core: compiler, shell & runtimes
Forgery - Easy and customizable generation of forged data.
rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
Fake Person - Create some fake personalities