Gem Developers

How can you, as a gem developer get the most out of Firebrigade?

First off, write tests. If you don't write tests, you can't even be marked as passing on Firebrigade. Also, release gems with passing tests.

Depend on what you need so that your tests will work. For example, if you have an rcov task, but you don't want to mark it as a dependency, wrap it in a rescue block. Tinderbox is friendly enough to add Rake or RSpec as a dependency if you forgot it, but other than that, you're on your own.

Make testing easy by following one of these conventions:

Be sure that the tests run with one of those commands out of the box (without doing anything else beforehand).

Test with the Tinderbox by running your gem in the same sandbox that each Tinderbox will use: 

$ tinderbox_gem_build ZenTest 3.4.3
build succeeded: true
build duration: 0.499964
build log:
### installing ZenTest-3.4.3 + dependencies
### ZenTest-3.4.3
### hoe-1.1.7
### rubyforge-0.4.0
### rake-0.7.1
### testing ZenTest-3.4.3
### rake test
/usr/local/bin/ruby -Ilib:bin:test -e 'require "test/test_autotest.rb"; require "test/test_help.rb"; require "test/test_rails_autotest.rb"; require "test/test_rails_controller_test_case.rb"; require "test/test_rails_helper_test_case.rb"; require "test/test_rails_view_test_case.rb"; require "test/test_ruby_fork.rb"; require "test/test_unit_diff.rb"; require "test/test_zentest.rb"; require "test/test_zentest_assertions.rb"; require "test/unit"' 
(in /Users/drbrain/tinderbox/sandbox/gems/ZenTest-3.4.3)
Loaded suite -e
Started
...................................................................................................................
Finished in 0.16146 seconds.

115 tests, 328 assertions, 0 failures, 0 errors

This way you can check your gem for potential problems before releasing.