Ruby On Rails State of Practice: Testing

• Share
• 
• | 
• Read later
• My Reading List

Rails developers can draw from a huge pool of libraries to build their applications. Dozens of options are available just for templating: do you use ERB, HAML, SASS, or do you prefer a JavaScript approach with Backbone.js or Knockout.js? The possibilities are endless, so we want to find out what our readers are using, or planning to use in the future.

In a first step (RFP), we asked you for suggestions. We received many answers, and after asking about deployment and management and frontend we now ask about testing. On the x-axis, you can show us what you’re using right now, or what you’ve moved away from and what you plan to adopt next. The y-axis indicates how valuable you think the specific technology or library is.

Here are the options:

• Capybara: acceptance test framework for web applications
• Jasmine: BDD framework for JavaScript
• RSpec: BDD for Ruby
• Shoulda: makes your Ruby tests more readable
• Spork: testing server for your Rails tests
• Minitest: provides a complete suite of testing facilities (TDD, BDD, mocking, and benchmarking)
• Bacon: small RSpec clone
• Riot: fast and contextual unit testing framework