similar to: Announcing Monrel Raw Output

After a long week agonizing over a scheduling library, and then specing it out rather quickly, I''ve got some work I''m pretty happy with. As a contrast to Test::Unit, I like the way RSpec spreads my attention around the codebase while I concentrate on implementing specific behaviours. In Test::Unit, I tend to write tests around the private methods of the object under test. I

Anyone else having an issue with route-generation in specs breaking as of Rails trunk r6062? When I run my specs at r6061, they all pass, and in 6062 I get a trace like this every time my controller generates a route: TypeError in ''Requesting /artists/1 using PUT should redirect to the artist'' can''t convert Fixnum into String (eval):19:in `artist_url''

I spent the last couple of days getting my sea legs with Rails and RSpec. I''d been waiting til things seemed calmer before jumping in, and I''m overall very happy with my experience so far. My only real annoyance so far has been forgetting to call "do_post" or "do_create" from my specify blocks. My mocks don''t get the calls they want, and it usually

The new "pending" example feature reminds me of a feature I''ve been bouncing around in my head, to aid in refactoring. Often, when I''m changing existing behaviour, I know that certain aspects of the old behaviour should change. Imagine changing the "it" method to perhaps "not" or "old" or "removed"... The behaviour would be to

I wrote this abomination just now, and wonder if anyone else has had experience with the pattern behind it. In short, I''m specing an after_create hook on an ActiveRecord model, that calls a bunch of private methods. Instead of stubbing all those private methods (which is verboten anyway, as well as impossible because creating the object which owns those methods is what I''m

Now that I''m developing a big suite of specs, I really want to run Heckle and see how well I''ve done. Using r1359, when I run: spec spec/models/metadata_report_spec.rb --heckle MetadataReport the result is just to run the specs once and then exit, as though I hadn''t mentioned Heckle. I started looking though rspec to figure out why, but it''s late, so I should

RSpecrs, I''ve been running into some trouble lately when passing mock objects into rich views. Either I have to obscure my specs by stubbing every method the view would call on my object, or I have to resort to trickery like stubbing ActionController#render, which is also less than ideal. The solution I''ve some up with is a variant on the :null_object option that can be passed

Greetings, I need some help... please be gentle :-) MY SETUP: Solaris-X86, ruby-1.8.4, Apache-2.2.0, Mongrel-0.3.13.4, MySql-4.1.10a I am using the typical setup with apache proxying request to mongrel with mod_proxy_balancer. Currently, I am only running a single instance of mongrel behind the proxy. I am also using the following gems with this app: capistrano (1.2.0) daemons (1.0.2)

I''m curious, Christian Neukirchen has released test/unit[1] that seems to mirror much of RSpec, but built on Test::Unit, so in some ways less brittle from a Rails-integration perspective, and also allowing you to mix the two together as appropriate. So, has anyone made an informed comparison? I''m new enough that I don''t really know the finer points yet. The syntax is

Hi, I am experiencing an error in the mongrel_rails script on a pc under cygwin/mongrel/rails. My installation details and error are as follows: With some guidance from various blogposts out there, I installed Cygwin on a Windows XP box followed by: Ruby 1.8.4(via cygwin setup), Gems (0.8.1 via ruby install.rb), Mongrel .3.12.4 (via gems), Rake 0.7.1(via gems, GemPlugin (via gems), Rails (via

My problem has been listed here: http://railsforum.com/viewtopic.php?pid=25439#p25439 Don''t think it would be required to completely re-type it here :) Thanks! -- -Daniel Fischer http://danielfischer.com - Geek Blog http://abigfisch.com - Portfolio http://writersbeat.com - Writing Community

Hello, So, I grabbed the mongrel_upload_progress code from subversion because I really need something similar for a project I am working on. Anyway, I installed the gem and can''t figure out a few things. 1) I''m not sure what Upload < GemPlugin::Plugin "/handlers" is for 2) How to call the Progress < GemPlugin::Plugin "/handlers" handler. While I

Hello mongrelians, I''ve had several submissions sent to me regarding the apache documentation on the mongrel site: http://mongrel.rubyforge.org/docs/apache.html I have assembled quite a bit of updates and changes, but if you know of anything that has been useful to you, or that is missing or can be reworded or added (or missing attributes!) please let me know. cheers, -- Charles

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

I thought all you mongrelians might appreciate this: http://xkcd.com/327/ I haven''t laughed out loud at a comic in a while. I realize it''s a working group but I figure many here might get a laugh today out of this one. Steve

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

Hi All I''m having some problems running my view specs when using simply_helpful. I have it semi-working via the following: module SimplyHelpfulHelper def self.included(base) base.send :include, SimplyHelpful::RecordIdentificationHelper base.send :include, SimplyHelpful::RecordTagHelper end end context "The index template" do setup do @shift =

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

Hi, Deploying in production on a server (debian sarge + ruby1.8.4) I got some problems: > mongrel_rails start -q /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.11/bin/mongrel_rails:6: uninitialized constant GemPlugin (NameError) from /usr/bin/mongrel_rails:18 gem_plugin is installed though. Mongrel 0.3.11. Rails 1.1. Any idea? -- Jean-Christophe Michel

Hi folks, I''d like to run the Mongrel prerelease (0.3.13.4 prerelease) and mongrel_cluster 0.2.1 on my shared host (which doesn''t want to install prerelease software for all to use). I can install the gems in my own directory, and run mongrel 0.3.13.4 with --prefix just fine. However, I think due to the GemPlugin structure, even my new mongrel_rails loads up