Things are looking fairly slick thanks to jQuery UI and a lot of AJAX, but it has been a bit of a handful to test. If you have suggestions for doing so, I’d lo

Things are looking fairly slick thanks to jQuery UI and a lot of AJAX, but it has been a bit of a handful to test. If you have suggestions for doing so, I’d love to hear about them in the comments. Mostly I have been doing unit testing for models which are likely to have failures, and then doing manual testing to verify that the UI works how I expect it to. I have suggestions. Use Capybara with Selenium, driven by either Cucumber or Steak (Steak is just rspec + some extra syntactic sugar; I prefer it, myself). You won't be able to test everything, especially complex user interactions. However, you should be able to test about 80-90% of the site functionality, and, importantly, you should be able to test the purchasing functionality (the balls of your app, so to speak) since that should always be simple. One of the decisions we've ended up leaning towards on Woobius is that we think twice about implementing UIs that can't be tested. If it can't be tested as designed, we spend some more time trying to figure out whether it can be redesigned in a way that can be tested but is still clear to the user. It's just one more design constraint, basically - can it be tested. If it really cannot be done in a testable way, at least we provide an alternative method that doesn't use fancy javascript and/or flash. For example, for the flash uploader, we also have a basic uploader. This means everything else can be tested, just not the multiple upload.