Ruby framework for writing a *True Test*

see blog.codecrate.com/2010/12/anatomy-of-effective-unit-test.html

• One assertion per test. No more…no less

• Clear separation of setup and assertions

• Support for multiple assertions with a single setup for fast test execution

• Integrates with core Ruby Test::Unit library

class BlogTest < Test::Unit::TestCase
  #register reusable fixtures
  register_fixture :a_basic_user do
    User.new
  end
  register_fixture :a_basic_blog do
    Blog.new
  end

  with :a_basic_user, :a_basic_blog do
    setup 'executing @a_basic_user.do_something' do
      @a_basic_user.do_something
    end

    should 'have did_something?' do
      @a_basic_user.did_something?
    end
    should_not 'have did_something_else?' do
      @a_basic_user.did_something_else?
    end
    should 'do some other stuff, but not yet implemented'
  end
end

• Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet

• Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it

• Fork the project

• Start a feature/bugfix branch

• Commit and push until you are happy with your contribution

• Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.

• Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright © 2010 Ryan Sonnek. See LICENSE.txt for further details.