- also removed obsolete experimental cuke feature
for expecting with the assertion framework provided by stdlib
- Closes #242.
"described_class" of the outer group.
- debugger statements work anywhere in the code, even parts that are outside RSpec's control (like before a describe declaration). - deprecated --debug/-d command line option - it doesn't do anything any more - warns if ruby-debug is not installed - only downside is for people who like to leave debugger statements around in their code
- this happens when both rspec-1 and rspec-2 are installed in the same environment, and a "require 'spec'" statement appears somewhere in the code (typically residual from an upgrade from rspec-1 to rspec-2). - Closes #94.
…ling on 1.9.2, but failure was not about spec'd behavior)
* These are built in exclusion filters that can be overriden. * When you configure a filter, it now merges with existing filters rather than completely overriding them. * A spec/group is now filtered if ANY of the filter conditions apply; before it required ALL to apply. * Filter lambdas can now accept a 2nd argument that is the metadata hash--this allows checking to see if the key is even in the hash (necessary for the :if filter).
rspec-core currently only supports using rspec-expectations to set expectations and define matchers, but this opens the door for new expectation frameworks and/or using assertion frameworks like that in test/unit or minitest without having to load rspec's expectation framework. - Closes #118.
- Closes #217.