factory_bot
django-debug-toolbar
Our great sponsors
factory_bot | django-debug-toolbar | |
---|---|---|
30 | 19 | |
7,875 | 7,903 | |
0.2% | 0.9% | |
7.8 | 8.4 | |
11 days ago | 2 days ago | |
Ruby | Python | |
MIT License | BSD 3-clause "New" or "Revised" 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
-
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.
django-debug-toolbar
-
Setting up Django in a Better Way in 5 Minutes and Understanding How It Works
The reason behind this splitting is that we can safely use packages and related settings only where we need. For example, this starter kit has the package django-debug-toolbar. This is only intended for your development environment and not for your production. This can be very risky if used in production because if your Django project encounters errors, all the debug info will be shown to the user which is a severe security risk. Similarly, for tracking errors in production, we're using Sentry which is not needed in our local environment since we already have django-debug-toolbar. For keeping these settings file separate so that they don't conflict with each other, the settings file is split for serving different environments.
-
Difficulty with foreignkey connecting to main object
django-debug-toolbar: https://github.com/jazzband/django-debug-toolbar
-
The Django ecosystem is not so good
https://github.com/jazzband/django-debug-toolbar/issues?q=is%3Aopen+is%3Aissue+label%3ABug
- Slow performance on AJAX queries in Django 4
-
is it alright to use raw sql and not the ORM if my queries are slow?
https://github.com/jazzband/django-debug-toolbar Allows you to check which sql queries are being run on your app. See if they are optimized first.
-
How to improve django template performance?
Perhaps try the django-debug-toolbar. It might be able to tell you what is causing the slow load time.
-
How do I determine where to cache?
I would start with https://github.com/jazzband/django-debug-toolbar and figure out what causes the slowness.
-
Improve your Django query with bulk_create 👋
-> The debugging above from django-debug-toolbar
-
Django Debug Toolbar
Documentation, including installation and configuration instructions, is available at https://django-debug-toolbar.readthedocs.io/.
- Five Easy to Miss PostgreSQL Query Performance Bottlenecks
What are some alternatives?
Fabrication - This project has moved to GitLab! Please check there for the latest updates.
django-silk - Silky smooth profiling for Django
faker - A library for generating fake data such as names, addresses, and phone numbers.
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
ffaker - Faker refactored.
ipdb - Integration of IPython pdb
Machinist - Fixtures aren't fun. Machinist is.
pudb - Full-screen console debugger for Python
Forgery - Easy and customizable generation of forged data.
django-devserver - A drop-in replacement for Django's runserver.
Fake Person - Create some fake personalities
wdb - An improbable web debugger through WebSockets