[rubygems/rubygems] Fix bundle gem ignoring global gem.test config

* bundle gem previously ignored gem.test when passed empty -t flag,
defaulting to RSpec
* bundle gem will now ask user for test framework when passed empty -t
flag and gem.test is set to false, but will not overwrite gem.test
* thor option parsing for String types falls back to human name for nil,
so setting lazy_default to nil won't work
* https://github.com/erikhuda/thor/blob/c5161501e0cfac7a8c5b838a9c6084c275f03c0d/lib/thor/parser/options.rb#L224

Default to Bundler.settings["gem.test"] for empty --test

Add shared examples for test framework to newgem spec

Add examples for empty --test flag to newgem spec

Simplify conditional for prompting test framework

Follow naming conventions for bundler settings

Add more descriptive test framework help text for bundle gem

Update man pages for bundler

https://github.com/rubygems/rubygems/commit/ab0785a09f

1 files changed, 15 insertions, 15 deletions

diff --git a/man/bundle-lock.1.txt b/man/bundle-lock.1.txt
index c52a3667a0..a24180b71d 100644
--- a/man/bundle-lock.1.txt
+++ b/man/bundle-lock.1.txt
@@ -16,16 +16,16 @@ DESCRIPTION
 OPTIONS
        --update=<*gems>
               Ignores  the  existing  lockfile. Resolve then updates lockfile.
-              Taking a list of gems or updating all gems if no list is given.
+              Taking a list of gems or updating all gems if no list is  given.
 
        --local
               Do not attempt to connect to rubygems.org. Instead, Bundler will
-              use   the   gems  already  present  in  Rubygems'  cache  or  in
-              vendor/cache. Note that if a appropriate  platform-specific  gem
+              use  the  gems  already  present  in  Rubygems'  cache   or   in
+              vendor/cache.  Note  that if a appropriate platform-specific gem
               exists on rubygems.org it will not be found.
 
        --print
-              Prints  the  lockfile  to  STDOUT instead of writing to the file
+              Prints the lockfile to STDOUT instead of  writing  to  the  file
               system.
 
        --lockfile=<path>
@@ -35,7 +35,7 @@ OPTIONS
               Fall back to using the single-file index of all gems.
 
        --add-platform
-              Add a  new  platform  to  the  lockfile,  re-resolving  for  the
+              Add  a  new  platform  to  the  lockfile,  re-resolving  for the
               addition of that platform.
 
        --remove-platform
@@ -51,7 +51,7 @@ OPTIONS
               If updating, prefer updating to next major version (default).
 
        --strict
-              If  updating,  do  not  allow  any gem to be updated past latest
+              If updating, do not allow any gem  to  be  updated  past  latest
               --patch | --minor | --major.
 
        --conservative
@@ -59,28 +59,28 @@ OPTIONS
               do not allow shared dependencies to be updated.
 
 UPDATING ALL GEMS
-       If  you  run  bundle  lock  with  --update option without list of gems,
-       bundler will ignore any  previously  installed  gems  and  resolve  all
-       dependencies  again  based on the latest versions of all gems available
+       If you run bundle lock with  --update  option  without  list  of  gems,
+       bundler  will  ignore  any  previously  installed  gems and resolve all
+       dependencies again based on the latest versions of all  gems  available
        in the sources.
 
 UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the  rest  of the gems that you specified locked to the versions in the
+       the rest of the gems that you specified locked to the versions  in  the
        Gemfile.lock.
 
-       For instance, you  only  want  to  update  nokogiri,  run  bundle  lock
+       For  instance,  you  only  want  to  update  nokogiri,  run bundle lock
        --update nokogiri.
 
        Bundler will update nokogiri and any of its dependencies, but leave the
-       rest of the gems that you specified  locked  to  the  versions  in  the
+       rest  of  the  gems  that  you  specified locked to the versions in the
        Gemfile.lock.
 
 SUPPORTING OTHER PLATFORMS
-       If  you want your bundle to support platforms other than the one you're
+       If you want your bundle to support platforms other than the one  you're
        running locally, you can run bundle lock --add-platform PLATFORM to add
-       PLATFORM  to the lockfile, force bundler to re-resolve and consider the
-       new platform when picking gems, all without needing to have  a  machine
+       PLATFORM to the lockfile, force bundler to re-resolve and consider  the
+       new  platform  when picking gems, all without needing to have a machine
        that matches PLATFORM handy to install those platform-specific gems on.
 
        For a full explanation of gem platforms, see gem help platform.