Skip to content

Instantly share code, notes, and snippets.

@msavy
Forked from jcrossley3/abstract.txt
Created June 20, 2011 18:55
Show Gist options
  • Save msavy/1036288 to your computer and use it in GitHub Desktop.
Save msavy/1036288 to your computer and use it in GitHub Desktop.
The goals of the TorqueBox project are ambitious, and exposing
complex, integrated enterprise Java services to Ruby applications
presents great challenges to the creation of useful yet simple
integration tests.
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 named TorqueSpec. We realize that what
works well for us might also work well for others who deploy their
apps on TorqueBox. In this talk we'll demonstrate exactly 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment