2004-11-23 20:04:44 -05:00
|
|
|
== Running with Rake
|
|
|
|
|
|
|
|
|
|
The easiest way to run the unit tests is through Rake. The default task runs
|
|
|
|
|
the entire test suite for all classes. For more information, checkout the
|
|
|
|
|
full array of rake tasks with "rake -T"
|
|
|
|
|
|
|
|
|
|
Rake can be found at http://rake.rubyforge.org
|
|
|
|
|
|
|
|
|
|
== Running by hand
|
|
|
|
|
|
|
|
|
|
If you only want to run a single test suite, or don't want to bother with Rake,
|
|
|
|
|
you can do so with something like:
|
|
|
|
|
|
2005-04-10 13:43:12 -04:00
|
|
|
ruby controller/base_tests.rb
|
2004-11-23 20:04:44 -05:00
|
|
|
|
|
|
|
|
== Dependency on ActiveRecord and database setup
|
|
|
|
|
|
|
|
|
|
Test cases in test/controller/active_record_assertions.rb depend on having
|
|
|
|
|
activerecord installed and configured in a particular way. See comment in the
|
|
|
|
|
test file itself for details. If ActiveRecord is not in
|
|
|
|
|
actionpack/../activerecord directory, these tests are skipped. If activerecord
|
|
|
|
|
is installed, but not configured as expected, the tests will fail.
|
|
|
|
|
|
|
|
|
|
Other tests are runnable from a fresh copy of actionpack without any configuration.
|
|
|
|
|
|
