With this latest version of test-unit, context works fine when tests are run with rake test.
However, when executing individual test files with testrb, no output is emitted. Guessing it's an API change on test-unit's part?
Thanks for the awesome gem!

I get the following when running context with ruby 1.9.1p243:

test: scrape_with_eval determines arguments with literal defaults(Boson::ArgumentInspectorTest::TestScrapeWithEval3387818):
NameError: undefined local variable or method `method_name' for #<Boson::ArgumentInspectorTest::TestScrapeWithEval3387818:0x66a61c>

/Users/bozo/.rvm/gems/ruby/1.9.1/gems/jeremymcanally-context-0.5.5/lib/context/lifecycle.rb:63:in `setup'
/Users/bozo/.rvm/gems/ruby/1.9.1/gems/mocha-0.9.8/lib/mocha/integration/mini_test/version_131_and_above.rb:25:in `run'

It seems method_name has disappeared in ruby 1.9.1. I tried changing method_name to name but then I get constant creation errors such as this:

test: scrape_with_eval determines arguments with literal defaults(Boson::ArgumentInspectorTest::TestScrapeWithEval3387776):
NameError: uninitialized constant Boson::ArgumentInspectorTest::TestScrapeWithEval3387776::MethodInspector

/Users/bozo/code/gems/boson/test/argument_inspector_test.rb:34:in `block (2 levels) in <class:ArgumentInspectorTest>'
/Users/bozo/.rvm/gems/ruby/1.9.1/gems/jeremymcanally-context-0.5.5/lib/context/lifecycle.rb:80:in `instance_eval'
/Users/bozo/.rvm/gems/ruby/1.9.1/gems/jeremymcanally-context-0.5.5/lib/context/lifecycle.rb:80:in `block in run_each_callbacks'

Any ideas on how to make context 1.9.1 compatible?

In my testing, my 'after' block is not running after a test failure.

This means that I can't remove some database objects after a test failure.

When I place a top-level before(:all) callback, the callback gets run for every context instead of only being run once. Even if I wrap this callback + all the test cases in a context, I still get the same behavior. This is happening on a mac with 1.8.6 using the system's test-unit or test-unit 1.2.3.