factory_bot
FactoryTrace
factory_bot | FactoryTrace | |
---|---|---|
31 | 5 | |
7,959 | 388 | |
0.3% | - | |
7.1 | 5.6 | |
26 days ago | about 1 year ago | |
Ruby | 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] How We Reduced API Response Rendering Time by 30%
Basic Information about props_template is a library that allows lightweight and fast JSON generation, with syntax similar to Jbuilder. It's developed by Thoughtbot, which is familiar with 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.
FactoryTrace
- If you use FactoryBot then the FactoryTrace gem might be interesting for you. It keeps your old code removed by finding unused factories & traits. There also was a recent release that made it compatible with all FactoryBot features.
- Do you use FactoryBot? Then FactoryTrace gem is right for you. It helps to find unused factories & traits automatically to keep your old code removed. There was a recent release that made it compatible with all FactoryBot features.
- Do you use FactoryBot? Then you should check out FactoryTrace. It finds unused factories & traits automatically for you to keep your old code removed. I just released 1.1.0, which has an important fix.
- Clean FactoryBot with FactoryTrace
-
N+1 problem will never be an issue with N1Loader gem
Don't know Database Consistency or Factory Trace which can help you to improve your code? Check them out too!
What are some alternatives?
Fabrication - This project has moved to GitLab! Please check there for the latest updates.
faker - A library for generating fake data such as names, addresses, and phone numbers.
ffaker - Faker refactored.