@bmispelon I don't remember trying it, but while reading about it now, I think that the slogan "smart fixtures for better tests" (which it inherited from model-mommy) can make sense.
@webology@josh@benjaoming@bmispelon definitely sold on them, and I typically build fixtures with factories, so I’m super curious to hear more about y’all’s workflows 😊 (happy to be pointed to examples if that’s easier!)
I get the impression there might be something in there for me when I don’t want to/can’t build factories for loads of models for whatever reason 🤞
@ghickman@webology@benjaoming@bmispelon Unfortunately all the interesting examples I have aren't public. I'll see if I can throw something in a gist at some point today.
@ghickman@webology@benjaoming@bmispelon Of course, just one model on it's own isn't super interesting, but if you extrapolate out for a project that has a dozen (or dozens) of Models, those extra files add up. Since I'm already all in on the pytest fixture train, just defining them once there saves that overhead. Plus the flexibility of adding kwargs to the baker.make call anywhere whenever I need it.
@ghickman@webology@benjaoming@bmispelon six of one, half dozen of the other.. Both are great libraries for accomplishing essentially the same thing, I just happen to like the little bit of extra flexibility and less boilerplate that model-bakery gives you.
@ghickman@webology@benjaoming@bmispelon On top of the fact that if you really need or miss the factory pattern, there are Recipes within model-bakery that can do that for you as well
It's something that's been on the back of my mind for a few years now, but your daily blogging in February really motivated me to actually start doing it.
Add comment