I was having strange issues with an ajax-based cucumber step. It was working perfectly when I ran the test manually, but for some reason Capybara was choking.
If only I could tinker around with the dom as the test was running. Fortunately for me, Mike Gehard at Pivotal Labs and Jari Bakken (a commentor) blogged about gaining access to Firebug while your features are running.
This approach, combined with a “wait” step definition (see here), gave me just the tools I needed to see what was happening while the tests were running. Brilliant!
Unfortunately, I couldn’t get the process to work as Mike outlined it, but by combining it with Jari’s second suggestion, it is working as advertised.