factory_bot

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.

> 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

When releasing a new application (or feature) I've always loaded each table in my development environments database with a few million rows. Tools like Python's Factory Boy [1] or Ruby's Factory Bot [2] help get the data loaded. After the data is loaded up, start navigating through the application and it will become evident where improvements need to be made. Tools like Django Debug Toolbar [3] help expose where the bad ORM calls are or also by tailing Postgres log files. [1] https://github.com/FactoryBoy/factory_boy [2] https://github.com/thoughtbot/factory_bot [3] https://github.com/jazzband/django-debug-toolbar

> Why is it important for the sake of testing to be able to alter the runtime behaviour externally without changing the code? Because that's additional cruft that you don't want when reading your code. Yeah I get it, you can pass dozen of abstract classes to each constructor for each thing you are mocking (or equivalent if it's not a class-based language) that you replace if needed, the only problem with that is that it's inconvenient, prone to mistakes (you can forget some) and makes the code ugly (you don't want to read testing code on the main code). I've done it in multiple static languages and at best it's a workaround that you should not have to deal with. I should add that any additional barrier to writing tests like this one also reduces the likelyhood that your app is well tested since some developers of your team might not bothe

Similar things happen all the time [0] An interesting thinking angle to this often “why was it fine before ?” Was it because nobody knew about that name/word in the first place ? Was there always incoming requests for change but those were just ignored as baseless, and as the social context changed discarding them is not as easy anymore ? Was it because the majority of users weren’t offended, but the user base changed enough that offended people’s voices go louder ? I find a lot of seemingly frivolous or petty word changes have a wider context that are not as simple as it looks on the surface. [0] https://github.com/thoughtbot/factory_bot/issues/1053

Name changes of popular OSS projects feels contentious, but like anything built on language it's inherently political and full of bias. As with anything, it's worth striving to improve things where we can. There are a few great examples including: 1. FactoryGirl -> FactoryBot: https://github.com/thoughtbot/factory_bot/issues/921 2. Whitelist -> Allowlist API in Rails: https://github.com/rails/rails/issues/33677 The irony that rather than engaging in the conversation and attempting to understand where people are coming from, bbatsov wrote a code of conduct then enforced it is not lost on me. > edited for formatting

This is neither good or bad imo. I can't even begin to comprehend why people would think that using a word in a fictional software name given by a developer causes "alienation". It's depressing that people take the time, effort and stress that goes into these rants and succeed. Possibly because those people are the only ones who care about something so.. worthless? useless? I mean, if people get murdered or locked up over this shit I could wrap my head around this edit: It seems a user on Github[0] called 'maxkwallace' addressed the naming issue. This particular user had an encounter with his female colleague which he found to be very awkward: "(...) at one point, I was going through some code with a female engineer, and noticing the name FactoryGirl led to an awkward exchange (...)" Later, he gets asked how the conversation was awkward

https://github.com/thoughtbot/factory_bot/issues/921 - Here is the original issue. And yes, it's about sexism, even though the name was a reference to a factory pattern and a song. https://github.com/thoughtbot/factory_bot/issues/921#issueco... - here is a comment I would like to highlight. >There is real, honest, awful sexism in tech, but this is not it.

Btw, they have counterparts in the Ruby world: https://github.com/stympy/faker (which states to be a port from Perl) and https://github.com/thoughtbot/factory_girl I use them in a Rails db/seed.rb file to create a new dev db every time I need new data to play with, especially after changes to the schema.