Use 'empty?' instead of 'any?' and 'none?' to match 'nil' and 'false'
…d 'false' as argument values
…of-matcher Fix generated docstring for BeAnInstanceOf when Class#inspect changed
rspec/rspec-core@96e3d13 rspec/rspec-core@582a0a8 Revert "Allow rbx builds to fail." This reverts commit 2f1595f.
Identify ruby code for syntax highlighting
We're getting weird sudden regressions on rbx, and given the frequency of RBX updates (and recent experience with failing rbx bulids in VCR and other rspec repos), I think it's due to a bug in rbx.
Include backtrace in errors reported by `raise_error` matcher.
It's hard to troubleshoot unexpected errors when the backtrace is silenced, as it was previously. Closes #59.
* rbx confusingly raises a NoMethodError in the error case described in `access_running_example.feature`. MRI and JRuby raise NameError. Because matching exactly isn't super-important, let's just match less stringently on the error message.
* Hopefully prevents relishapp from considering the _ as italics
…pec::Core * It is possible for RSpec::Core to be defined, but not be fully loaded enough for RSpec.configuration to be accessible because rspec-core.gemspec requires 'lib/rspec/core/version' which defines RSpec::Core::Version but nothing else.
We've been getting a strange failure on rbx-19 that I can't reproduce locally: https://travis-ci.org/#!/rspec/rspec-expectations/jobs/2583529