I'll be giving my talk "Hurting Code for Fun and Profit" as well as hosting RejectConf at GoRuCo this weekend. I hope to see you there!
Recently in Rails Category
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.
Changes:
3.9.2 / 2008-03-20
4 minor enhancements:
- Added compatibility with miniunit differences.
- Added emailnotify, jabbernotify, and rcov autotest plugins.
- Updated rakefile to include examples automatically in exampledotautotest.
- multiruby now outputs each command so you can grab it easily.
5 bug fixes:
- Ensure tests are run after reset.
- Fixed all test/rails tests to run in any combo.
- Fixed up growl.rb a bit... still buggy (growlnotify, not growl.rb).
- Fixes for -f (fast start) and last_mtime in general.
- Fixes for 1.9 and rubinius
- http://rubyforge.org/projects/zentest/
- ryand-ruby@zenspider.com
One Line Multi-Stage Deployment for Vlad:
Kernel.load "config/deploy_#{ENV['to']}.rb" if ENV['to']
Making this elegant line possible:
% rake vlad:deploy to=qa
Coming Soon™ to a Vlad near you!
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.
Changes:
3.9.1 / 2008-01-31
1 bug fix:
- OMG I'm so dumb... fixed memory leak.
- http://rubyforge.org/projects/zentest/
- ryand-ruby@zenspider.com
Something I should have emphasized more in my release notes:
- Added ability to set test execution order, defaults to :random. EVIL!
What does this mean?
It means that if you ignored my post titled "rake passes but autotest fails?", then autotest is gonna get its revenge when you update. No. Really. It is gonna f' your tests up real good. Why? Because it is Good Testing Practice™ for all your tests to be completely standalone. If I could run your individual tests randomly I'd do that as well(*).
I've had a number of filed bugs and hallway conversations where someone states "blah blah ... but when I run it under autotest, it fails" and somehow they've convinced themselves that it is autotest's fault. "HAH!", I say! Not bloody likely. If your tests aren't written in such a way that each and every individual test can be run in isolation or in any combination and order, then you didn't write tests, you wrote bugs. I really can't emphasize that enough so autotest plans to help you exorcize yourself of these bugs.
Really, you should just take the hit right now and deal with it. But what if your PHB is breathing down your neck? You can tell autotest to run your tests in "Ye Olde Fashioned Sorted Mode" with the following (be sure to copy and paste and fill it out:
Autotest.add_hook :initialize do |at|
at.order = :alpha # I am a bad person. [your name], [today's date]
end
and then make yourself a promise that in 1 month's time autotest will be able to run your tests in any order. Now write it down, and sign it, in blood.
*) I did mention that I wrote miniunit, right? *smile*
**) They probably aren't. PHB's usually won't let you use autotest in the first place. Or write tests for that matter. So if you've gotten this far, you're probably in good shape.
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.
Changes:
3.9.0 / 2008-01-30
15 minor enhancements:
- Added Wilson's patch to allow unit_diff to work with mspec. Adding rspec next.
- Minor overhaul for autotest:
- Added -f flag to start up without testing.
- Added -q flag to autotest to make it extra quiet. Patch by Aaron Patterson.
- Added ability to set test execution order, defaults to :random. EVIL!
- Added completedre and failedresults_re to help subclasses like rspec.
- Added deprecation warnings for hooks. Deprecated :run.
- Added find_directories accessor, defaults to ['.']
- Added sleep accessor, defaults to 1 second.
- Changed findfiles to order files in the same order as finddirectories.
- Changed how autodiscover works with $:, added lib to the front.
- Cleaned out nearly every @ and use accessor methods instead. You should too.
- Made test_mappings ordered.
- Removed @files, adding @findorder and @knownfiles.
- Renamed testsforfile to testfilesfor.
- testfilesfor now only returns known files.
- http://rubyforge.org/projects/zentest/
- ryand-ruby@zenspider.com
Eric and I are last-minute tripping up to RubyCamp... Hopefully we'll see you there.
new rails bug: incorrect pluralization of "penis".
be sure to add your comments/vote. :)
Vlad the Deployer is pragmatic application deployment automation, without mercy. Much like Capistrano, but with 1/10th the complexity. Vlad integrates seamlessly with Rake, and uses familiar and standard tools like ssh and rsync.
Impale your application on the heartless spike of the Deployer.
FEATURES/PROBLEMS:
- Full deployment automation stack.
- Turnkey deployment for mongrel+apache+svn.
- Supports single server deployment with just 3 variables defined.
- Built on rake. Easy. Engine is small.
- Very few dependencies. All simple.
- Uses ssh with your ssh settings already in place.
- Uses rsync for efficient transfers.
- Run remote commands on one or more servers.
- Mix and match local and remote tasks.
- Compatible with all of your tab completion shell script rake-tastic goodness.
- Ships with tests that actually pass in 0.028 seconds!
- Does NOT support Windows right now (we think). Coming soon in 1.2.
Changes:
1.1.1 / 2008-01-14
5 major enhancements:
- Support for Rake 0.8. Should still work for Rake 0.7.
- Added git support (contributed by Garry Dolley).
- Reviewed for accuracy by Evan Phoenix.
- Added lighttpd.rb
- Added automatic client setup for perforce.
- Added mercurial SCM support patch. Closes ticket 13475.
6 minor enhancements:
- Added #put method that wraps up Tempfile/rsync pattern.
- Added automatic p4 client setup for perforce.
- Added vladdemo.sh
- Moved everything over to put.
- Moved generic app setup to core from mongrel.
- Parameterized 'head' into 'revision' variable (with head as default).
1 bug fix
- Fixed cleanup to actually properly clean up.
- http://rubyforge.org/projects/hitsquad/
David Chelimsky has a great writeup in his blog about the latest changes to ZenTest and how they affect you and your .autotest file.
One additional thing:
% ln -s ~/Work/git/rubinius ~/.multiruby/install
% multiruby -e 'p 1 + 2'
... blah blah ...
Passed: 1.8.6-p111, 1.8.4, 1.8.5, rubinius, 1.9.0-0, 1.8.2
Failed:
