abstract.txt

The goals of the TorqueBox project are ambitious, and when exposing
complex, integrated enterprise Java services to Ruby applications,
making sure everything "just works" can be enormously challenging.

Over time, the TorqueBox integration test suite has evolved from 100%
Java-based container testing, to something of a hybrid, and finally to
a 100% Ruby-based solution we call TorqueSpec. And we believe it can
benefit not just us, but real TorqueBox users, too. In this talk,
we'll attempt to demonstrate how.

TorqueSpec offers end-to-end testing of any Rack-based *OR* Java web
app using RSpec and Capybara (or Webrat, etc). Further, it enables
true "in-container" testing by allowing TorqueBox components to be
injected directly into RSpec examples. This allows you to test, for
example, your Java CDI components using RSpec. Best of all, your tests
will be running on a platform virtually identical to your production
environment: TorqueBox.