From db045dbbf60b53dbe013ef25554fd013baf88134 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Wed, 24 Nov 2004 01:04:44 +0000 Subject: Initial git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4 5ecf4fe2-1ee6-0310-87b1-e25e094e27de --- actionpack/RUNNING_UNIT_TESTS | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 actionpack/RUNNING_UNIT_TESTS (limited to 'actionpack/RUNNING_UNIT_TESTS') diff --git a/actionpack/RUNNING_UNIT_TESTS b/actionpack/RUNNING_UNIT_TESTS new file mode 100644 index 0000000000..c27ee02d67 --- /dev/null +++ b/actionpack/RUNNING_UNIT_TESTS @@ -0,0 +1,25 @@ +== 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: + + ruby controller/base_test.rb + +== 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. + -- cgit v1.2.3