Permalink
Browse files

words

  • Loading branch information...
dchelimsky committed Jun 5, 2010
1 parent 3642323 commit 1c03b2a4f4dc6bc2b3d5ebfb0394a2fb3a9e6901
Showing with 34 additions and 37 deletions.
  1. +0 −12 README.markdown
  2. +0 −15 TODO.markdown
  3. +31 −7 Upgrade.markdown
  4. +3 −3 rspec-core.gemspec
View
@@ -63,18 +63,6 @@ Use the documentation formatter to see the resulting spec:
Finished in 0.000379 seconds
1 example, 0 failures
-## Configuration
-
-You can define runtime configuration options in four places. They
-are loaded and processed in this order:
-
-* ~/.rspec
-* .rspec
-* RSpec.configure
-* command line
-
-Run `rspec --help` to see supported configuration options.
-
#### Also see
* [http://github.com/rspec/rspec](http://github.com/rspec/rspec)
View
@@ -1,15 +0,0 @@
-### RSpec Core
-
-* support the following concepts from rspec-1.2.x
- * run options
- * from command line
- * in rake task definitions
- * formatters
-* For self testing
-** shared example groups should not be merged into the real 'world'
-* make sure all behaviour refs are now examplegroup
-
-### Maxwell
-
-* need to figure out how maxwell will allow us to mix all the rails testing
- facilities with rspec when working with rails.
View
@@ -1,11 +1,29 @@
# Upgrade to rspec-core-2.0
-## What's changed
+## What's changed since rspec-1
-### RSpec namespace
+### rspec command
-The root namespace is now `RSpec` instead of `Spec`, and the root directory
-under `lib` is `rspec` instead of `spec`.
+The command to run specs is now `rspec` instead of `spec`.
+
+ rspec ./spec
+
+### autotest
+
+RSpec-2 works with autotest as follows:
+
+ # in ./autotest/discover.rb
+ Autotest.add_discovery { "rspec2" }
+
+ # command line
+ $ autotest
+
+The `autospec` command is a thing of the past.
+
+### RSpec
+
+The root namespace (top level module ) is now `RSpec` instead of `Spec`, and
+the root directory under `lib` within all of the `rspec` gems is `rspec` instead of `spec`.
### Configuration
@@ -15,11 +33,15 @@ Typically in `spec/spec_helper.rb`, configuration is now done like this:
# ....
end
-### rspec commmand
+### .rspec
-The command to run specs is now `rspec` instead of `spec`.
+Command line options can be persisted in a `.rspec` file in a project. You
+can also store a `.rspec` file in your home directory (`~/.rspec`) with global
+options. Precedence is:
- rspec ./spec
+ command line
+ ./.rspec
+ ~/.rspec
## What's new
@@ -35,6 +57,8 @@ like the file and line number on which it was declared, the arguments passed to
argument passed to `describe` or `it`, allowing us to pre and post-process
each example in a variety of ways.
+### Filtering
+
The most obvious use is for filtering the run. For example:
# in spec/spec_helper.rb
View
@@ -9,7 +9,7 @@ Gem::Specification.new do |s|
s.required_rubygems_version = Gem::Requirement.new("> 1.3.1") if s.respond_to? :required_rubygems_version=
s.authors = ["Chad Humphries", "David Chelimsky"]
- s.date = %q{2010-06-02}
+ s.date = %q{2010-06-04}
s.description = %q{RSpec runner and example group classes}
s.email = %q{dchelimsky@gmail.com;chad.humphries@gmail.com}
s.executables = ["rspec", "spec"]
@@ -142,7 +142,7 @@ Gem::Specification.new do |s|
s.rdoc_options = ["--charset=UTF-8"]
s.require_paths = ["lib"]
s.rubyforge_project = %q{rspec}
- s.rubygems_version = %q{1.3.6}
+ s.rubygems_version = %q{1.3.7}
s.summary = %q{rspec-core-2.0.0.beta.10}
s.test_files = [
"spec/autotest/failed_results_re_spec.rb",
@@ -182,7 +182,7 @@ Gem::Specification.new do |s|
current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
s.specification_version = 3
- if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then
+ if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
s.add_development_dependency(%q<rspec-expectations>, [">= 2.0.0.beta.10"])
s.add_development_dependency(%q<rspec-mocks>, [">= 2.0.0.beta.10"])
s.add_development_dependency(%q<cucumber>, [">= 0.5.3"])

0 comments on commit 1c03b2a

Please sign in to comment.