assert_nothing_raised and assert_nothing_thrown are the two most useless assertions on the planet. If they have spec equivalents, add those to the list as well.

I had a student litter those everywhere and I told him not to use it. He said he was just trying to be "explicit". You're writing a test already, you're already being explicit. By virtue of running code in the first place you're asserting that it doesn't throw anything unexpected.

Why does anyone use it? Is it just to up the assertion count?

I think I'm going to deprecate them from the assertion library unless someone can show me a compelling reason not to.

Do you like that better than must vs wont? I think I do, but it might be too visually similar. I'm not sure. Check it:

(6 * 7).must_equal 42
(6 * 9).wont_equal 42

vs.

(6 * 7).will_equal 42
(6 * 9).wont_equal 42

I think it looks OK so far.

Also, I added a simple little mapping system to make morphing the assertions into specifications more readable:

Object.infect(:must, :wont,
              /(throw)s/              => '\1',
              /must_(.*_of|nil|same)/ => 'must_be_\1',
              /must_not_(nil|same)/   => 'must_not_be_\1',
              /wont_(nil|same)/       => 'wont_be_\1',
              /must_in_delta/         => 'must_be_close_to',
              /must_no_match/         => 'must_not_match',
              /must_operator/         => 'must_be',
/^(wont|must(_(block|raises|nothing_(raised|thrown)))?)$/ => :skip)

For a while Eric and I have added a method to our assertion suite:

def deny exp
  assert ! exp
end

It is a really handy way to describe things. I dislike the look and sound of assert ! blah so we go with deny... but one thing bugs me:

def test\_something
  assert 42 == 6 * 7
  deny 42 == 6 * 9    # does not line up
end

Yeah yeah... I'm OCD or something. I would much rather read:

def test\_something\_better
  assert 42 == 6 * 7
  refute 42 == 6 * 9
end

I was digging through Apple's wonderful dictionary and thesaurus and came up with another possibility: debunk... how much better or worse is this?

def test\_something\_better
  assert 42 == 6 * 7
  debunk 42 == 6 * 9
end

Hell... let's get rid of assert and go with prove and rebut! I've just saved you all an extra key per test! OH! show! Now that's a lot more assertive (pun intended) than assert is. That means I could come back full circle to deny.

That reminds me... I've LONG wanted a list of same-length opposite verbs and adjectives. Google turns up nothing... I'm wondering if I can't somehow generate it with GED's linguistics library.

lib/mini/test.rb
lib/mini/spec.rb
lib/mini/mock.rb

All this fun in less than a thousand lines, tests included!

So obviously it needs a new name. I was thinking of calling it "Mini de Sade" for fun, but it really doesn't convey what it does (other than hurt other code--tee hee!). I also searched through the dictionary looking for other possibilities:

% egrep -i "m.*(t.*s|s.*t)|t.*(m.*s|s.*m)|s.*(m.*t|t.*m)" /usr/share/dict/words | ruby -e 'p STDIN.read.split(/\n/).sort_by { |s| s.length }.first(11)'
["must", "mist", "mast", "stem", "smit", "stum", "smut", "most", "myst", "stim", "stam"]

And I gotta say, I kinda like MuST. I used that as inspiration already. I've also decided that "should" is too wishy-washy and switched to "must" in mini/spec.rb. (Don't worry, I made it easy to add your shoulds if you so desire).

(ooh. smut == specs, mocks, and unit tests)

Any naming suggestions?

Eventually I'll get the dashboard and other styling thingies set up.

updated: Apparently it also changed the UUIDs in the feed... Sorry

just look at that url for a second... (if it doesn't go off screen, that is)

the domain... sure. whatever.
viewvc. yeah. k.
webservices/xmlrpc/trunk/server/src/main/java -- damn... we haven't even hit code yet!
org/apache/xmlrpc/server -- WE STILL haven't hit code yet!?!

and then... the kicker:

wtf? ... wow. check it:

public interface RequestProcessorFactoryFactory { ... }

this thing declares an interface for a factory that produces other factories that produce things that process requests. processing requests... request processing. factory of factory of... I feel like the lawyer in Idiocracy. duuuh... errr. ummm.

How many freakin' levels of indirection does this world need? It's not even a class.

kill. me. now.

(Via Labnotes » Rounded Corners - 196.)

Test::Unit (Classic) - Nathaniel Talbott's originial test-unit, externalized from the ruby project as a gem (for tool developers).

Changes:

1.2.3 / 2008-02-25

• 1 major enhancement

  • Birthday (as a gem)!

• http://rubyforge.org/projects/test-unit/

(no silly... look in the blog, not the RSS feed!)

Using the package_inline tool Inline allows you to package up your inlined object code for distribution to systems without a compiler.

Changes:

3.6.7 / 2008-03-20

• 3 minor enhancements:

  • Added ability to work entirely without .ruby_inline dir. Thanks Kevin Clark!
  • Updated history, readme, and rakefile for new hoe abilities.
  • Cleaned up some really ugly schlock. Man, compiling sucks!

• 2 bug fixes:

  • Fixes for 1.9.
  • Add -I for platform-specific header dir (for ruby/config.h).

• http://rubyforge.org/projects/rubyinline/

• http://rubyinline.rubyforge.org/RubyInline/
• http://www.zenspider.com/ZSS/Products/RubyInline/
• ryand-ruby@zenspider.com

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://www.zenspider.com/ZSS/Products/ZenTest/

• http://rubyforge.org/projects/zentest/
• ryand-ruby@zenspider.com

tell application "OmniFocus"
  tell first document
    repeat with aContext in contexts
      set toDelete to {}
      set seen to {}
      repeat with aTask in tasks of aContext
        if seen contains name of aTask then
          set end of toDelete to id of aTask
        else
          set end of seen to name of aTask
        end if
      end repeat

      repeat with aTask in toDelete
        try
          delete (task id aTask)
        end try
      end repeat
      count of toDelete
    end repeat
  end tell
end tell

• Run 'rubyforge help' for complete usage.
• Setup: For first time users AND upgrades to 0.4.0:
  • rubyforge setup (deletes your username and password, so run sparingly!)
  • edit ~/.rubyforge/user-config.yml
  • rubyforge config
• For all rubyforge upgrades, run 'rubyforge config' to ensure you have latest.
• Don't forget to login! logging in will store a cookie in your .rubyforge directory which expires after a time. always run the login command before any operation that requires authentication, such as uploading a package.

Changes:

0.4.5 / 2008-03-11:

• Update for Ruby 1.9.0.
• Updated History, Rakefile, and Readme for new hoe abilities.

• Added config backup/restore rake tasks (for testing).

• http://codeforpeople.rubyforge.org/rubyforge/

• http://rubyforge.org/projects/codeforpeople/

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!

Generated 2008-03-04 22:49