Note that capybara/rspec's matchers already use the negated assertion in readme

I love the idea of this gem and was eager to see if I could speed up my test suite by eliminating waiting for the timeouts, but I was disappointed when none of my tests failed due to waiting for the timeout.

It turns out the matchers Capybara defines already use the negated version of each assertion (for example: https://github.com/jnicklas/capybara/blob/4161bbc560631e61e611d59bf797eeb59a6b1021/lib/capybara/rspec/matchers.rb#L71), so you're already guarded against accidentally waiting the full timeout.

I'm not thrilled with the copy I added, but figured its a start to alerting others that Capybara may already be handling this for you when used with RSpec.