- it was more expressive, but caused errors in rspec-rails - will revisit later This reverts commit 9d61d59.
- the rspec command already does this - if you want to use the ruby command, require 'rspec/autorun'
- not in the context of config - aligns with shared_examples_for API - also add `include_context` method to example group - so shared context can be included ... - using include_context - by matching metadata
The current message won't make sense for config options that use symbol metadata so this provides an easy way to define another module with a different warning message for use by configuration.
only executed once per suite.
…prevent SystemStackError on 1.9.
inheriting from Proc. - This allows Procsy to behave correctly in all supported versions of MRI, as well as JRuby-1.5 and JRuby-1.6. - See http://jira.codehaus.org/browse/JRUBY-5261 - See http://jira.codehaus.org/browse/JRUBY-5026 - Thanks to John Firebaugh for the suggestion! - Closes #291 (hopefully forealz)
Previously, they could only be applied to top-level example groups. - Closes #274.
* 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).
- caller is only used to determine file and line number as metadata is initialized. There is no need to store it. - Also, the previous commit reduces the need for analysis of the caller stack. We therefore don't need to sling it around within the rspec codebase. - Running the following 5000 times took 2.77 seconds before these last two commits, 1:58 after: describe "something" do it "does something" do 1.should eq(1) end end Please enter the commit message for your changes. Lines starting
This isn't a good permanent solution, but it's better than the current behavior. Currently, RSpec's error handling raises its own error for an error in after(:all), which gives the user a confusing error message and hides the user's error message.