Passing the --profile flag to RSpec produces some additional output, namely the running times of the ten slowest examples in your specs.

On any page accessed with SSL, all Ajax requests must use SSL, or they will fail. To make this happen, all you need to do is include the names of the actions that service the requests in your ssl_required statement.

What if my controller decides to take the Thing.create! and rescue route? What if my model has a special initializer method, like Thing.build_with_foo? My spec for behavior should not fail if I change the implementation.

Pure-Ruby alternative to Cucumber.

Write declarative tests using nested contexts without performance penalties. Contest is less than 100 lines of code and gets the job done.

Amidst my 400 unread Boing Boing links are probably ten or fifteen that are probably real gems. But I’ll never know and Boing Boing sure as hell isn’t going to help me out.

What Is Bloat?

I brought up the question whether tests should call the translation API when checking for the presence of a string.

The same problem happened with address, which was specified to mean only the contact information for the author of a page. It was quite explicitly specified to not accept mailing addresses. Of course, tons of people did just that, because they had an address and there was an address element, so of course they went together!

Recently I've been made aware of people inside US Government organizations using my Ruby on Rails Security presentation as an excuse to limit Ruby on Rails adoption and projects inside those organizations.

Another ActiveModel alternative.

Celerity is a JRuby wrapper around HtmlUnit – a headless Java browser with JavaScript support. It provides a simple API for programmatic navigation through web applications. Celerity aims at being API compatible with Watir.

You want to try out all of the different ruby interpreters and versions including different patchlevels, but you don't want to break what's working for you now. No time to waste?

Understand API usage.

It's important, however, that his wonderful code live on, and we need your help to do so. We've mirrored what repos we could find and contacted github tech support, who have promised assistance. Whymirror will do what it can to ease the transition but CANNOT be a long-term solution

Rio is a facade for most of the standard ruby classes that deal with I/O; providing a simple, intuitive, succinct interface to the functionality provided by IO, File, Dir, Pathname, FileUtils, Tempfile, StringIO, OpenURI and others. Rio also provides an application level interface which allows many common I/O idioms to be expressed succinctly.

View testing that doesn't suck.

A/Bingo is a Ruby on Rails A/B testing framework written as a plugin.