Service objects in Rails tests - factory_girl replacement
3 likes1,250 views
Service objects provide a way to test Rails applications by encapsulating business logic and hiding implementation details. They represent use cases or scenarios and allow writing tests that are fast, easy to write, and stay in sync with production code by testing below the controller layer. However, extracting existing Rails code into service objects can be challenging.
Service objects in Rails tests - factory_girl replacement
- 1. Service objects as a way of testing Rails apps @andrzejkrzywda @arkency In love/hate relationship with Rails, since 2004
- 3. The things you call from your controllers
- 4. Rails is not your app Your app is below controllers
- 5. Most of the things without HTTP
- 9. Query objects - read the system
- 11. Reads are easy Commands are more difficult
- 12. Rails-way is good for Reads
- 13. Rails-way is not ideal for Commands
- 14. Testing
- 16. Good tests tell a story
- 17. 1. User adds a product to the cart 2. User looks at the cart to see the current total amount 3. User changes the amount 4. User goes to checkout
- 18. How to setup the state?
- 19. factory_girl
- 21. What makes a good unit?
- 22. Unit == a set of service objects
- 24. Wins?
- 26. tests in sync with production code
- 27. Easy to write
- 28. Fast
- 29. Problems?
- 30. Tests are one layer below ! Easy to make mistakes when calling services from controllers
- 31. Not so easy to extract services from an existing, legacy Rails codebase
- 32. Examples
- 34. Thanks!