This first batch of tips fiddles with unit test logging by tweaking the test/unit/test_helper.rb file. By default, when you run rake test:units from the top level directory of your Rails application, all logging output goes into log/test.log. If that’s not good enough, if you want a different name or location for your test output, the change is easy. Add this to the end of test_helper.rb:

TESTLOG = File.expandpath(”#{RAILSROOT}/log/flamey-test.log”) ActiveRecord::Base.logger = Logger.new(TESTLOG)

If you’re writing a standalone ActiveRecord application outside of a Rails environment, you’ll have to explicitly create and assign a logger yourself. The easiest solution is to pass Logger.new a simple file name.

ActiveRecord::Base.logger = Logger.new(”test.log”)

Unfortunately this will drop the log file into whichever relative directory you run the tests from. What you probably want is to anchor it to the test_helper.rb file (which you’ll also have to create yourself in a standalone application).

TESTLOG = File.expand_path(File.dirname(FILE) + “/test.log”) ActiveRecord::Base.logger = Logger.new(TESTLOG)

A slightly better place is in a log directory, sibling to the test directory:

TESTLOG = File.expand_path(File.dirname(FILE) + “/../log/test.log”) ActiveRecord::Base.logger = Logger.new(TESTLOG)

More tips on the flip side…

Another handy hoop trick is to provide a command-line switch for STDOUT logging. To send output to a file, invoke your tests as normal; to send output to the console, set LOG_STDOUT in your environment to anything, e.g. LOG_STDOUT=yes ruby test/my_test.rb.

TESTLOG = File.expandpath(File.dirname(FILE) + “/test.log”) ActiveRecord::Base.logger = ENV["LOGSTDOUT"] ? Logger.new(STDOUT) : Logger.new(TESTLOG)

Of course, there’s always the lower level logging properties. To turn off the special color markup (who on earth made that the default?!?):

ActiveRecord::Base.colorize_logging = false

To filter the logging output by severity level:

ActiveRecord::Base.logger.level = Logger::INFO

And finally, this line tags the log file (or console output) with a friendly banner whenever the test_helper.rb file is loaded, which amounts to every time you run the tests:

ActiveRecord::Base.logger.info( “#{”=”25} RUNNING UNIT TESTS #{”=”25}\n\t\t\t#{Time.now.to_s}\n#{”=”*70}”)

It looks like this:

========================= RUNNING UNIT TESTS =========================

Mon Feb 12 10:39:50 CST 2007

Have fun, and stay tuned for the next Hoop o’ fire.

According to one elated nginx user:

The only solution I know of that’s extremely high performance that offers all of the features that you want is Nginx… I currently have Nginx doing reverse proxy of over tens of millions of HTTP requests per day (thats a few hundred per second) on a single server. At peak load it uses about 15MB RAM and 10% CPU on my particular configuration (FreeBSD 6).

Under the same kind of load, Apache falls over (after using 1000 or so processes and god knows how much RAM), Pound falls over (too many threads, and using 400MB+ of RAM for all the thread stacks), and Lighty leaks more than 20MB per hour (and uses more CPU, but not significantly more).

It does seem like a lean, powerful solution for sites that control their entire technology stack; of course, it doesn’t help those of us on shared hosting providers like Dreamhost who must wait for the admins to carefully and excruciatingly evaluate each new service they roll out.

A quick Googlry turns up quite a few articles on nginx:

• “Nginx, my new favorite front end for mongrel cluster” by Ezra Zygmuntowicz

• “High-Performance Ruby On Rails Setups Test: mongrel vs lighttpd vs nginx” and many other nginx articles by Alexey N. Kovyrin

• “(Rails Deployment – Apache – Lighttpd) + Nginx & Mongrel Cluster” by LabRat

• “Time For A Grown-Up Server: Rails, Mongrel, Apache, Capistrano and You” by Coda Hale

• “nginx: the front end solution for rails deployment?” by Dominic Damian

If you’re able, I’d highly recommend checking it out. On the other hand, if you’re one of the poor, lonely stack-impaired minions like myself, maybe you can wring a few drops of vicariousness from the gushy victory stories above.

This works nicely for the plugin’s lib directory, but what about its test directory? Unfortunately, by default plugin tests are pretty bland. They use the plain unit test suite supplied by Ruby, and not any of the extended Rails test framework. This will leave our plugin’s test classes with no access to fixtures, database.yml configuration, or any of those nice class auto-loading features.

Fear not! It’s easy to wire the full Rails model testing framework into any plugin. Details below….

(continued)

To get us started, let’s generate stubs for our imaginary SkinnyFeet plugin:

script/generate plugin skinnyfeet create vendor/plugins/skinnyfeet/lib create vendor/plugins/skinnyfeet/tasks create vendor/plugins/skinnyfeet/test create vendor/plugins/skinnyfeet/README create vendor/plugins/skinnyfeet/Rakefile create vendor/plugins/skinnyfeet/init.rb create vendor/plugins/skinnyfeet/install.rb create vendor/plugins/skinnyfeet/uninstall.rb create vendor/plugins/skinnyfeet/lib/skinnyfeet.rb create vendor/plugins/skinnyfeet/tasks/skinnyfeettasks.rake create vendor/plugins/skinnyfeet/test/skinnyfeet_test.rb

The generated test stub is boring as rocks, and completely devoid of Rails-ness:

vendor/plugins/skinnyfeet/test/skinnyfeet_test.rb

require ‘test/unit’

class SkinnyFeetTest < Test::Unit::TestCase

Replace this with your real tests.

def testthisplugin flunk end end

In a test file generated by Rails for a model class, the ${RAILS_ROOT}/test/test_helper.rb file pulls in the Rails environment. In theory, we could reference that application helper file from the plugin, but that’s a bit ugly and dangerous. Our fancy plugin might someday reside in random applications. We have no idea what dastardly hacks they’ve done to their own test_helper.rb file. We certainly don’t want the application test suite to break our plugin test suite.

Let’s be safe and create our own test helper class inside the plugin. The minimum we need is the first three lines of the default generated test_helper.rb file. Note that we have to extend the path to environment.rb by three levels since we’re nested deep in the vendor directory.

vendor/plugins/skinnyfeet/test/testhelper.rb

ENV["RAILSENV"] = “test” require File.expandpath(File.join(File.dirname(FILE), ‘../../../../config/environment’)) require ‘test_help’

Then in each database-hammering plugin test file, replace the require 'test/unit' statement at the top with:

vendor/plugins/skinnyfeet/test/whichevertest.rb

require File.dirname(FILE) + ‘/test_helper’

With this simple change, our plugin gains access to everything we’ve been missing: the application’s database.yml file, the fixtures directory, and the auto-loading feature. We can now start using classes we’ve implemented in our plugin lib directory without bothering with require statements (as long as we follow the proper Rails file-naming conventions).

Also, the fixtures directive should work to load data fixtures into the database for testing — except it’ll grab those fixture files from the default application directory at ${RAILS_ROOT}/test/fixtures/. Instead, we want to create our own fixtures directory inside our plugin, at vendor/plugin/skinny_feet/test/fixtures. To override the default fixture directory (and control other fixture settings), add this to the bottom of the plugin’s test_helper.rb file:

vendor/plugins/skinnyfeet/test/testhelper.rb

class Test::Unit::TestCase self.usetransactionalfixtures = true self.useinstantiatedfixtures = false self.fixturepath = File.expandpath(File.dirname(FILE) + “/fixtures”) end

The disadvantage to loading up Rails for each test suite is that it introduces a significant performance hit. You won’t want to do this for tests that don’t interact with the database.