Testing in Rails 3.x

Test Automation with RoR for dummies
Aug, 2011
Eran Nelinger, SAP Labs
eran.nelinger@sap.com

Why Test Automation
Rails Testing Theory
Deep dive into ‘Test’ directory
Other automation investment tips
8/22/2011

8/22/2011

8/22/2011
Life’s too short for manual testing…

8/22/2011
Rails make it super-easy for us to write tests (Almost everything we need is already in place with scaffolding)
Machine can better remember expected output

Why Test Automation
Deep dive into ‘Test’ directory
8/22/2011

8/22/2011
Rails applications typically interacts heavily with databases
If we would like to write efficient tests, they’ll need to interact with databases

8/22/2011
We would like to be able to run our test in such environment where messing our data does not really make a difference
On the other hand we want to rebuild our data each time before a test run

8/22/2011
The Three Environments approach allows us to set up and interact with test data without any danger of your tests altering data from your production environment

8/22/2011
test/fixtures:
Just a fancy word for ‘sample-data’
Populate our test-schema with content each time before a test runs
Database independent
Supports YAML as well as CSV

8/22/2011

8/22/2011
test/unit:
Unit-tests in rails are model-tests
Logical assertions of our application’s business logic
Should include at list one test method for every method in the model

8/22/2011
test/unit/helpers:
Any method that might be used in more then one test-case

8/22/2011
test/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 files
Switch to RAILS_ENV = “test”
Brings us assertions from test test/unit

8/22/2011
test/functional
ActionController::TestCase
Controller specific tests
was the web request successful?
was the user redirected to the right page?
was the user successfully authenticated?
was the correct object stored in the response template?
was the appropriate message displayed to the user in the view?

8/22/2011
test/integration
ActionController::IntegrationTest
Interaction among number of controllers
Generally used to test important flows
Fixtures -> to be included explicitly

8/22/2011
test/performance
ActionDispatch::PerformanceTest
Runs a code profiler of each test method
Flat and graph_html output is written by defauls

8/22/2011
Before 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

8/22/2011
Assertions are the working bees of testing
Actually performs a check to see if expected==actual

8/22/2011
Rails specific assertions

Why Test Automation
Deep dive into ‘Test’ directory (Model testing)
8/22/2011

8/22/2011

Why Test Automation
Deep dive into ‘Test’ directory (Controller testing)
8/22/2011

8/22/2011

Why Test Automation
Deep dive into ‘Test’ directory (View testing)
8/22/2011

8/22/2011

8/22/2011
http://guides.rubyonrails.org/testing.html
http://guides.rubyonrails.org/
http://ruby-doc.org/stdlib/libdoc/test/unit/rdoc/classes/Test/Unit.html
http://ruby-doc.org/stdlib/libdoc/test/unit/rdoc/classes/Test/Unit/Assertions.html
http://api.rubyonrails.org/classes/ActiveSupport/TestCase.html
http://api.rubyonrails.org/classes/ActionController/TestCase.html
http://rdoc.info/github/rails/rails/master/ActionDispatch/IntegrationTest
http://watir.com/
http://pivotal.github.com/jasmine/
http://railscasts.com/episodes/261-testing-javascript-with-jasmine

8/22/2011

Testing in Rails 3.x

by nelinger on Sep 01, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 4

Statistics

Testing in Rails 3.x — Presentation Transcript