Ruby conf 2016 - Secrets of Testing Rails 5 Apps
Download as PPTX, PDF0 likes359 views
The document discusses testing strategies for Rails 5 applications, differentiating between unit tests, functional tests for controllers, and integration tests. It highlights changes in Rails 5 where controller tests have been most affected and notes the deprecation of functional tests in favor of integration tests that are now faster. Additionally, it mentions using Factory Girl for creating test instances and introduces some testing tools and techniques.
Ruby conf 2016 - Secrets of Testing Rails 5 Apps
- 1. Secrets of Testing Rails 5 Apps
- 2. Rails Tests Unit tests -> For models Functional tests -> For controllers Integration tests -> For scenarios of a particular feature
- 3. Change in rails 5 Unit tests -> No big change Controller tests -> are most affected
- 4. What do we test in a controller test ? Request --------------> Response
- 6. Controller tests actually lie...
- 8. Integration tests Almost same as controller tests Close to the real world But before rails 5 they were really slow
- 9. Integration Controller tests are default in Rails 5
- 10. Functional Controller tests are soft deprecated
- 11. Old functional tests will continue to work for now***
- 12. Might be extracted in separate gem in Rails 5.1
- 13. BLACK BOX
- 14. Sprockets
- 15. Sprockets
- 16. Speeding Up Your Test Suite
- 23. Returns a saved User instance (writes to DB) user = create(:user) # Returns a User instance that's not saved (does not write to DB) user = build(:user) factory :user do association posts end FactoryGirl.build(:user) #this creates posts in the database even though you are only building the parent object(user) Returns an object with all defined attributes stubbed out stub = build_stubbed(:user)
- 26. 20 Tools and Techniques That Make You More Creative
- 44. Thank You
Editor's Notes
- #6: We are hitting the postcontroller create. We are checking if it is redirected to correct path. But we are also checking database value change which is not actually part of the response.
- #7: They dont actually follow the same request / response cycle as it happens when a request hits the application. They bypass typical request/response cycle. It directly hits the particular action and tries to see what happenning inside.They are not really testing the controller in true sense. They are just like unit testing the controller actions.
- #8: We can write functional type controller tests in rails… They dont bypass middleware stack. They go through the way when a request hits rails app.
- #11: Rails by default will not generate the controller test codes. It will generate integrated test codes.
- #12: Rails by default will not generate the controller test codes. It will generate integrated test codes.
- #13: Rails by default will not generate the controller test codes. It will generate integrated test codes.
- #14: Rails is suggesting not to test the internals rather than test the outcome