@jnicklas The real issue with this is that HaveSelector needs to catch the Capybara::ExpectationNotMet exception and then ends up raising an RSpec::Expectations::ExpectationNotMetError exception. This may necessitate waiting for a major version update if there was a guarantee of HaveSelector raising Capybara::ExpecationNotMet on failure. I don't see it documented (or specifically tested) anywhere. What would your thoughts on it be?

I think it should be done in major version.

It wasn't documented but it's a quiet well known (and reliable) fact that those methods raise Capybara::ExpectationNotMet error - http://stackoverflow.com/search?q=%5Bcapybara%5D+ExpectationNotMet

Also as this is backwards incompatible change please take a look on #1246 as it refactors this code too (I know that I should rebase it, maybe fix something, include Composable, etc.)

@abotalov all of the entries I looked at in that search were people trying to figure out why their matcher was failing, none of them seemed to be people rescuing that specific exception. I'm not convinced this needs to go into a major release.

Is there a release cycle for capybara, wondering when this will make it into the gem?

@DaveBlooman There is no fixed release cycle. I'm aiming for the next release in 1-2 weeks

Thanks for update and the PR.