rspec
diff --git a/‎DEVELOPMENT.md
Lines changed: 16 additions & 5 deletions b/‎DEVELOPMENT.md
Lines changed: 16 additions & 5 deletions
diff --git a/‎rspec-mocks/lib/rspec/mocks/verifying_double.rb
Lines changed: 2 additions & 0 deletions b/‎rspec-mocks/lib/rspec/mocks/verifying_double.rb
Lines changed: 2 additions & 0 deletions
diff --git a/‎script/run_rspec
Lines changed: 17 additions & 2 deletions b/‎script/run_rspec
Lines changed: 17 additions & 2 deletions
@@ -18,9 +18,15 @@ $ bundle install
 
 ## Working on an individual library
 
-For most contributors, setting up the project individually will be simpler.
+Each rspec-* library is a standalone gem, with a standalone build. We recommend you
+treat each as such and run development tools from their individual directories.
+
+For convience though, you can also run `script/run_rspec` from the root directory
+to run all the specs, as well as `bin/rubocop` to check all files for recommendations
+at once.
+
+# Bundler setup
 
-Unless you have a specific reason to use rspec-dev, we recommend using this approach.
 To minimize boot time and to ensure we don't depend upon any extra dependencies
 loaded by Bundler, our CI builds avoid loading Bundler at runtime
 by using Bundler's [`--standalone option`](https://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
@@ -29,14 +35,17 @@ While not strictly necessary (many/most of our contributors do not do this!),
 if you want to exactly reproduce our CI builds you'll want to do the same:
 
 ```
+$ rm Gemfile.lock
 $ bundle install --standalone --path <current_lib>/bundle
 $ bundle binstubs --path <current_lib>/bundle/bin
 ```
 
 The `binstubs` option creates the `bin/rspec` file that, like `bundle exec rspec`, will load
 all the versions specified in `Gemfile.lock` without loading bundler at runtime!
 
-You can also run `bundle install` as normal with the GEMFILE environment variable set to the parent directory.
+Note that as a set of gems we don't check in `Gemfile.lock`, so to replicate a CI build on branch
+changes / after a period of time you will need to delete your local `Gemfile.lock` file to install
+the same gems as CI.
 
 ## Extra Gems
 
@@ -48,10 +57,12 @@ gem declarations. The `Gemfile` evaluates that file if it exists, and it is git-
 
 The [CI build](https://github.com/rspec/rspec/actions)
 runs many verification steps to prevent regressions and
-ensure high-quality code. To run the build locally, for an individual libraryrun:
+ensure high-quality code. To run the build locally, for an individual library run:
 
 ```
-$ script/run_build
+$ ../script/run_rspec
+$ ../script/run_rspec_one_by_one
+$ ../script/run_cucumber
 ```
 
 See [build detail](BUILD_DETAIL.md) for more detail.
 
@@ -36,12 +36,14 @@ def method_missing(message, *args, &block)
 
       # Redefining `__send__` causes ruby to issue a warning.
       old, $VERBOSE = $VERBOSE, nil
+      # rubocop:disable Naming/MethodName
       def __send__(name, *args, &block)
         @__sending_message = name
         super
       ensure
         @__sending_message = nil
       end
+      # rubocop:enable Naming/MethodName
       ruby2_keywords :__send__ if respond_to?(:ruby2_keywords, true)
       $VERBOSE = old
 
 
@@ -13,8 +13,23 @@ function run_specs {
     rspec_bin=script/rspec_with_simplecov
   fi;
 
-  echo "${PWD}/bin/rspec"
-  $rspec_bin spec --backtrace --format progress --profile --format progress
+  if [ $PWD -ef $ROOT_DIR ]; then
+    echo "In root directory... running all specs..."
+
+    for dir in "$ROOT_DIR"/*/ ; do
+      dir=${dir%/}
+
+      if [ -d "$dir/spec" ]; then
+        echo "${PWD}/bin/rspec spec in ${dir}"
+        pushd $dir
+        $rspec_bin spec --backtrace --format progress --profile --format progress
+        popd
+      fi
+    done
+  else
+    echo "${PWD}/bin/rspec spec"
+    $rspec_bin spec --backtrace --format progress --profile --format progress
+  fi;
 }
 
 run_specs