If the gem installs or your application still runs this does not mean the gem is compatible!
The 'Is it Ruby 1.9' website is full of bad reports of working gems and ruins what could be a good resource. Good on you for having a go but at the very least you should run the unit tests before reporting that something works; otherwise you are only hindering the process.
Sorry to get all Zed Shaw but as someone trying to help authors migrate to 1.9 by submitting patches instead of sitting on my hands it's hard to know what does/doesn't need attention due to the poor quality of reporting.
For example http://isitruby19.com/rspec is reported as working for 1.2.6 but if you check out that tag (1.2.6) as listed by the reporter it fails 1 test[1]. That's much better than 1.2.3 and 1.2.4 according to the previous reporter but it still means that every other gem using Rspec tested against any of these versions either isn't being tested at all or may be failing/passing incorrectly.
Perhaps it's time to stop talking about testing, speaking at conferences, writing frameworks, dsl's, methodologies, etc. require 'test/unit' and actually write/run some tests.
From Perl's CPAN playbook:
- Run gem installs with tests by default.
- Use Test::Unit. A test framework should not be part of a gems dependencies (a whole other rant).
- Get testers and a test matrix set up either as a community or amongst your friends.
- Email authors when the tests fail.
1) OSX - Tag 1.2.6, Ruby 1.9.1p0 - Looks like the author (david?) has a full path in there by mistake?
Spec::Runner::Formatter::HtmlFormatter should produce HTML identical to the one we designed manually with --diff
expected: "/Users/david/projects/ruby/rspec-dev/example_rails_app/vendor/plugins/rspec/examples/failing/mocking_example.rb",
got: "/Users/anonymous_coward/projects/gh/rspec/examples/failing/mocking_example.rb" (using ==)
Cheers.Anonymous Coward - May 29, 2009 16:54
Dear anonymous coward,
I agree that tests should be on by default. I've already submitted this as a feature request, and I plan on putting it into motion for 1.4.0, so long as Eric agrees (which I think he does).
We can't specify the test library. That's up to the gem authors. If they use rspec for their tests for example, then it's up to them to create rspec as a dependency for their library. Rspec will then have to be installed first.
I'm not sold on the test matrix + email concept. One of the downsides is lots of bogus failures from unsupported platforms, or from platforms the author has no way of testing on. I could see it as an independent service, though, but not something baked into Rubygems.
I like the "tests on by default" idea for RubyGems, but it better be reallllllly easy to turn off with a switch or something. I can imagine a ton of gems I use regularly failing some minor test or another. On the plus side, of course, this will help highlight issues and encourage more people to get involved with improving those libraries..PeterCooper - May 30, 2009 16:59
Peter, the -t and --no-test options are already available. In addition, even if a test fails, you're given the choice to force install it.
The issue now, beyond the fact that it's not on by default, is the ordering of some of the events that take place behind the scenes. Or rather, the ordering of the messages that you see on the command line is less than ideal.djberg96 - May 31, 2009 02:38
Very useful information on this site I bet there are continuous
Garlica sarımsak hapı kilo verdiren bitkisel kapsul
Garlica sarımsak hapı zayıflamada en iyi
Garlicasarımsak hapı - September 24, 2009 15:53
RubyFlow is a community driven Ruby links site with 1243 members. Posts are by members of the community — like you! Enjoy the links and leave comments.
How To Post Items
RubyFlow is a great way to promote great Ruby content — even your own! No mandatory signup but only posts by registered members with 1 previously good post make it into the RSS and Twitter feeds.
Comments