Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

docs

  • Loading branch information...
commit c4a852d06818c298c5d6f7dd8b3424ab2afbc8a5 1 parent 26271e1
@dchelimsky dchelimsky authored
Showing with 24 additions and 42 deletions.
  1. +1 −1  features/Changelog.md
  2. +23 −41 features/Upgrade.md
View
2  features/Changelog.md
@@ -86,7 +86,7 @@
* debugger statements _just work_ as long as ruby-debug is installed
* otherwise you get warned, but not fired
* Expose example.metadata in around hooks
- * Performance improvments (see [Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown))
+ * Performance improvments (much faster now)
* Bug fixes
* Make sure --fail-fast makes it across drb
View
64 features/Upgrade.md
@@ -1,59 +1,41 @@
-# rspec-core-2.3
+# rspec-core-2.5
+
+## autotest
+
+### 2.5
+
+By default, RSpec adds `bundle exec` to the command generated by Autotest if
+there is a `Gemfile` in the project root directory.
+
+As of rspec-core-2.5, you can pass `--skip-bundler` to the `autotest` command
+and it won't include `bundle exec` even if there is a `Gemfile`.
-## autotest integration
+ autotest -- --skip-bundler
-Add a .rspec file to the project's root directory to tell RSpec to tell
-Autotest to use RSpec's specialized Autotest class.
+### 2.3
+
+As of rspec-core-2.3, RSpec's Autotest extension is loaded when you run the
+`autotest` command if there is a `.rspec` file in the project's root directory.
NOTE that rspec-core-2.0, 2.1, and 2.2 required an autotest/discover.rb file in
the project's root directory. This worked with some, but not all versions of
autotest and/or the autotest command that ships with ZenTest. This new approach
-will work regardless of which version of autotest/ZenTest you are using.
+works regardless of which version of autotest/ZenTest you are using.
+
+# rspec-core-2.3
-## config.expect_with
+## `config.expect_with`
Use this to configure RSpec to use rspec/expectations (default),
-test/unit/assertions, or both:
+stdlib assertions (Test::Unit with Ruby 1.8, MiniTest with Ruby 1.9),
+or both:
RSpec.configure do |config|
config.expect_with :rspec # => rspec/expectations
- config.expect_with :stdlib # => test/unit/assertions
+ config.expect_with :stdlib # => Test::Unit or MinitTest
config.expect_with :rspec, :stdlib # => both
end
-# rspec-core-2.2
-
-## FASTER!
-
-Made several small optimizations that all add up to a considerable improvement
-in performance. Using a simple benchmark:
-
- generate 5000 example groups,
- each with one example,
- each with one passing expectation
-
-Run using ruby-1.9.2 on Mac OS X w/ 3.06 G
-
-* rspec-2.1
- * loaded in 0.85 on avg
- * ran in 2.61 on avg
-* rspec-2.2
- * loaded in 0.73 on avg (~15% improvement)
- * ran in 0.94 on avg (~64% improvement**)
-
-** this does _not_ mean your suite will be 64% faster, but it does mean that
- the overhead incurred by RSpec in your suite should be roughly 64% less.
-
-## Command line
-
-### --debug/-d is now deprecated
-
-This command line option is now has no effect (other than a deprecation
-warning). To use the debugger, just add a `debugger` statement anywhere in your
-code. As long as you have ruby-debug installed, it will just work. If you
-don't, then you'll get a friendly warning telling you what's going on, but
-execution will continue.
-
# rspec-core-2.1
## Command line
Please sign in to comment.
Something went wrong with that request. Please try again.