Eric went insane on ZenTest the last two weeks and I'm proud to announce that we just released ZenTest 3.2.0! In this release we've added Test::Rails and further enhanced autotest. Test::Rails is a brand-spankin' new way of writing your tests for your rails app. It splits out rails' rather hefty functional tests into separate controller and view tests. Now you can test your controllers without the cost of rendering. It can even audit itself to ensure testing consistency (there is probably a better way of describing this, but it is late).
Install Now, Read Later
sudo gem install ZenTest or visit the rubyforge project.
I'm still going to write up some real stuff on using multiruby and autotest (including my emacs hooks for it), but for now here is the standard marketing blurbies:
ZenTest provides 4 different tools and 1 library: zentest, unit_diff, autotest, multiruby, and Test::Rails.
ZenTest scans your target and unit-test code and writes your missing code based on simple naming rules, enabling XP at a much quicker pace. ZenTest only works with Ruby and Test::Unit.
unit_diff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong.
autotest is a continous testing facility meant to be used during development. As soon as you save a file, autotest will run the corresponding dependent tests.
multiruby runs anything you want on multiple versions of ruby. Great for compatibility checking!
Test::Rails helps you build industrial-strength Rails code.
Specifically I'm trying to figure out a way to stop zentest generating loads of stubs for methods included by 'acts_as...' or mixins, where I trust that this code is already tested.
We have a project on rubyforge: http://rubyforge.org/projects/zentest/