{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/ecc4d502278ae77354564beb97bdff10?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ecc4d502278ae77354564beb97bdff10","url":"https://api.github.com/users/knoopx","login":"knoopx","id":100993},"milestone":null,"assignee":null,"labels":[],"updated_at":"2011-11-07T03:33:09Z","closed_at":null,"comments":8,"url":"https://api.github.com/repos/jnicklas/capybara/issues/508","body":"Months ago I started using the new capybara's DSL for acceptance tests, however every time a spec fails I have to reproduce the problem by hand in order to determine what is happening because capybara is unable to catch the exception and the message is printed on response body. So the rspec output/backtrace is pretty useless because it just tells which spec fails instead of the broken app piece. How do you deal with this situation?","html_url":"https://github.com/jnicklas/capybara/issues/508","title":"Acceptance test output/backtrace","number":508,"id":1738915,"created_at":"2011-09-26T12:03:25Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/de396cedd7085b8ac01f8c18a7e24167?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"de396cedd7085b8ac01f8c18a7e24167","url":"https://api.github.com/users/agibralter","login":"agibralter","id":1079},"updated_at":"2011-11-07T03:33:09Z","url":"https://api.github.com/repos/jnicklas/capybara/issues/comments/2649694","body":"That is, if you're using Capybara's `Thin` app server... you could probably do something similar for mongrel.","id":2649694,"created_at":"2011-11-07T03:33:09Z"}}