-
Scout Monitoring
Rennaisance engineers rejoice! 1 gem 5 min to app monitoring. 5-minute onboarding. No sales team. Devs in the support channels. No DevOps team required. Get the free app insights every engineer deserves with Scout Monitoring.
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.
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.
Related posts
-
Show HN: Factory-JS – TypeScript dummy object generator for testing
-
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