Ruby on Rails latest stable (v6.1.7.7) - 0 notes
  • 1.0.0 (0)
  • 1.1.6 (0)
  • 1.2.6
  • 2.0.3
  • 2.1.0
  • 2.2.1
  • 2.3.8
  • 3.0.0
  • 3.0.9
  • 3.1.0
  • 3.2.1
  • 3.2.8
  • 3.2.13
  • 4.0.2
  • 4.1.8
  • 4.2.1
  • 4.2.7
  • 4.2.9
  • 5.1.7
  • 5.2.3
  • 6.0.0
  • 7.0.0
  • What's this?

Module deprecated or moved

This module is deprecated or moved on the latest stable version. The last existing version (v1.1.6) is shown here.

In addition to these specific assertions, you also have easy access to various collections that the regular test/unit assertions can be used against. These collections are:

  • assigns: Instance variables assigned in the action that are available for the view.
  • session: Objects being saved in the session.
  • flash: The flash objects currently in the session.
  • cookies: Cookies being sent to the user on this request.

These collections can be used just like any other hash:

  assert_not_nil assigns(:person) # makes sure that a @person instance variable was set
  assert_equal "Dave", cookies[:name] # makes sure that a cookie called :name was set as "Dave"
  assert flash.empty? # makes sure that there's nothing in the flash

For historic reasons, the assigns hash uses string-based keys. So assigns[:person] won’t work, but assigns["person"] will. To appease our yearning for symbols, though, an alternative accessor has been deviced using a method call instead of index referencing. So assigns(:person) will work just like assigns["person"], but again, assigns[:person] will not work.

On top of the collections, you have the complete url that a given action redirected to available in redirect_to_url.

For redirects within the same controller, you can even call follow_redirect and the redirect will be followed, triggering another action call which can then be asserted against.

Manipulating the request collections

The collections described above link to the response, so you can test if what the actions were expected to do happened. But sometimes you also want to manipulate these collections in the incoming request. This is really only relevant for sessions and cookies, though. For sessions, you just do:

  @request.session[:key] = "value"

For cookies, you need to manually create the cookie, like this:

  @request.cookies["key"] ="key", "value")

Testing named routes

If you’re using named routes, they can be easily tested using the original named routes methods straight in the test case. Example:

 assert_redirected_to page_url(:title => 'foo')


  • assert_template_equal
Show files where this module is defined (2 files)
Register or log in to add new notes.