Ah, thanks, Luis, I figured it must be something like this. FWIW, my two cents: This change makes perfect sense for most Ruby users, but it will be a minor irritant for me -- I wrote some Ruby code for students to install, and I'd like to minimize the number of things they need to download to set up their environment. In this case I have an easy workaround, though. I have them run a setup script after installing my gem, and I can just modify this script so it does the unit tests.
Thanks again -- I appreciate all you and the others have been doing with gem, the Windows installer, etc. JC On Jun 14, 2011, at 5:41 PM, Luis Lavena wrote: > On Tue, Jun 14, 2011 at 5:25 PM, Conery John <con...@cs.uoregon.edu> wrote: >> Hi -- >> >> I'm trying to use the "gem check" command to run unit tests for an installed >> gem. On one of my systems (OS X, running gem 1.8.5) I noticed that the >> --test option is no longer supported for the check command. Was it removed >> on purpose? Is there another way I can let users run unit tests after they >> have installed a gem? Or is there a better way for users to test their gems? >> > > Testing of RubyGems has been removed (deprecated) and replaced by a > better testing infrastructure in a RubyGems plugin: gem install > rubygems-test: > > https://github.com/rubygems/rubygems-test > > -- > Luis Lavena > AREA 17 > - > Perfection in design is achieved not when there is nothing more to add, > but rather when there is nothing more to take away. > Antoine de Saint-Exupéry > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
