lax

A bright smidgen of a testing framework that is not the boss of you.

  Lax.test { |assert|
    assert.calling(:/).on(1).with(0).raises ZeroDivisionError

    assert.satisfies(->(n) { n == 1 }) { |returns_one|
      returns_one.calling(:+).on(0).with 1

      returns_one.on(1) { |id_on_one|
        id_on_one.calling(:+).with 0
        id_on_one.calling(:*).with 1

        0.upto(10) { |n|
          id_on_one.calling(:**).with n
        }
      }
    }
  }
  Lax.go

yes but why

• Everything about a test is independently scopeable - methods, arguments, receivers, blocks, expectations, hooks, and any metadata you might care to attach. Testing that one method call satisfies three conditions is as natural as testing that one condition is satisfied by three different method calls. Write tests in whatever way makes sense.
• No hardcoded constraints on terminal output, handling of failed tests, w/e - it's all done with user-configurable hooks.
• Support for concurrent testing (via threads - not currently threadsafe in JRuby).
• Code footprint so small, it's hardly there at all (< 200 SLOC).
• Does not pollute your toplevel namespace or infect the entire Ruby object hierarchy with its code.

make it do it

  cd my/project/root
  mkdir -p lax/test
  echo "Lax.test {|that| that.calling(:+).on(1).with(99).returns 100}" > lax/test/test.rb
  echo "require 'lax'; Lax::RakeTask.new(:dir=>'lax')" >> rakefile
  rake lax

license

X11. See LICENSE for details.