Testing in Rails 3.x
- 1. Test Automation with RoR for dummiesAug, 2011Eran Nelinger, SAP [email protected]
- 2. Why Test AutomationRails Testing TheoryDeep dive into ‘Test’ directoryOther automation investment tips8/22/2011
- 3. Why Test AutomationRails Testing TheoryDeep dive into ‘Test’ directoryOther automation investment tips8/22/2011
- 4. 8/22/2011
- 5. 8/22/2011
- 6. 8/22/2011Life’s too short for manual testing…
- 7. 8/22/2011Rails make it super-easy for us to write tests (Almost everything we need is already in place with scaffolding)
- 8. Machine can better remember expected outputWhy Test AutomationRails Testing TheoryDeep dive into ‘Test’ directoryOther automation investment tips8/22/2011
- 9. 8/22/2011Rails applications typically interacts heavily with databases
- 10. If we would like to write efficient tests, they’ll need to interact with databases8/22/2011We would like to be able to run our test in such environment where messing our data does not really make a difference
- 11. On the other hand we want to rebuild our data each time before a test run8/22/2011The Three Environments approach allows us to set up and interact with test data without any danger of your tests altering data from your production environment8/22/2011test/fixtures:Just a fancy word for ‘sample-data’Populate our test-schema with content each time before a test runsDatabase independent Supports YAML as well as CSV
- 12. 8/22/2011
- 13. 8/22/2011
- 14. 8/22/2011test/unit:Unit-tests in rails are model-testsLogical assertions of our application’s business logicShould include at list one test method for every method in the model
- 15. 8/22/2011test/unit/helpers:Any method that might be used in more then one test-case
- 16. 8/22/2011test/unit/test_helper.rb:Define ActiveSupport::TestCase class which is the base class for each test (not only unit)Requires by each of the test filesSwitch to RAILS_ENV = “test”Brings us assertions from test test/unit
- 17. 8/22/2011test/functionalActionController::TestCaseController specific testswas the web request successful?
- 18. was the user redirected to the right page?
- 19. was the user successfully authenticated?
- 20. was the correct object stored in the response template?
- 21. was the appropriate message displayed to the user in the view?8/22/2011test/integrationActionController::IntegrationTestInteraction among number of controllersGenerally used to test important flowsFixtures -> to be included explicitly
- 22. 8/22/2011test/performanceActionDispatch::PerformanceTestRuns a code profiler of each test methodFlat and graph_html output is written by defauls
- 23. 8/22/2011Before running the tests:$ rake db:migrate runs any pending migrations on the development environment and updatesdb/schema.rb$ rake db:test:load recreates the test database from the current db/schema.rb
- 24. 8/22/2011Assertions are the working bees of testing
- 25. Actually performs a check to see if expected==actual8/22/2011Assertions are the working bees of testing
- 26. Actually performs a check to see if expected==actual8/22/2011Rails specific assertionsWhy Test AutomationRails Testing TheoryDeep dive into ‘Test’ directory (Model testing)Other automation investment tips8/22/2011
- 27. 8/22/2011
- 28. 8/22/2011
- 29. 8/22/2011
- 30. 8/22/2011
- 31. 8/22/2011
- 32. 8/22/2011
- 33. 8/22/2011
- 34. 8/22/2011
- 35. 8/22/2011
- 36. 8/22/2011
- 37. 8/22/2011
- 38. 8/22/2011
- 39. 8/22/2011
- 40. Why Test AutomationRails Testing TheoryDeep dive into ‘Test’ directory (Controller testing)Other automation investment tips8/22/2011
- 41. 8/22/2011
- 42. 8/22/2011
- 43. 8/22/2011
- 44. 8/22/2011
- 45. 8/22/2011
- 46. Why Test AutomationRails Testing TheoryDeep dive into ‘Test’ directory (View testing)Other automation investment tips8/22/2011
- 47. 8/22/2011
- 48. 8/22/2011
- 49. 8/22/2011
- 50. 8/22/2011
- 51. 8/22/2011
- 52. 8/22/2011
- 53. 8/22/2011
- 54. 8/22/2011
- 55. 8/22/2011
- 57. 8/22/2011