similar to: Are you writing "imperative" or "declarative" scenarios in your stories?

Forgive the long post, just looking for input/advice/alternate opinions.. Like many I think that going through the exercise of framing user requests in Cucumber terms(Features, Scenarios..) really helps facilitate necessary conversations and avoid time wasted implementing the wrong thing(e.g. as a requirement/specification tool). However, I''m a bit confused when it comes to

I''m working on writing features for a wizard. The wizard collects information from a number of different forms, and you can navigate through it in a number of ways. Anyhow one of these forms is a customer form collecting name, and email. In the context of the wizard I feel that the following scenarios Scenario: Given I step to customer And I fill in my customer details

I''m spending today writing documentation. I''ll be updating quite a few documents, doing some edits, and adding some user contributed docs. If anyone has documentation suggestions, FAQ questions they''d like included, or things they think are old and stale, then let me know. Swing by the Lingr room: http://www.lingr.com/room/3yXhqKbfPy8 And drop me a line if you want

Hey list, I''m refactoring some much-used functionality into a common_steps step group. Methods like this are in there: steps_for :common do Given "a number of existing $types?" do |type| @initial_item_count = type.singularize.classify.constantize.count end When "the user adds an invalid $type" do |type| post

What''s the status on a rake task for the story runner. If nothing is in progress, where could I start to try and build one? JD

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs: http://www.sonoma-marinfair.org/uglydogvote.shtml I *have* to use one of these for the Mongrel BUGS Mascot. He''ll go on our bug list page and replace the little beetles on the left. Pick the dog you think best represents a lovable but defective pooch and reply to this with your +1. Let the voting begin! -- Zed A. Shaw

I have been using Rspec stories with Webrat feeling very productive and happy. Then I needed to do something with Selenium (Webrat could have done what I needed but it does not yet have the functionality). Selenium-core as part of a rails plugin looked nice but did not seem to fit with rspec stories. So I went the Selenium-rc route. Since Selenium uses a separate instance of rails

I''m proud to announce the official Mongrel certification program: http://mongrel.rubyforge.org/certified.html Move quick, seats are filling fast for the RubyConf courses. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.

Hey Folks, This is a quick release that fixes a major bug. I forgot to require the timeout library properly in mongrel.rb so people using Mongrel outside of Rails would see pauses. 0.3.3 fixes this all up. The 0.3.3 release also has a small change to the examples/simpletest.rb file with some gzip response using Ruby''s zlib support. Curious what people think about this and whether it

Hi All, Alright, this release is getting closer. It''s nearly complete except the docs on my site aren''t written yet. There is however a full README with RDoc documentation and several packages including a gem release. Please check out the latest release at: * Announcement: http://www.zedshaw.com/ * README and RDoc:

Hi, Whenever I restart mongrel on my production server, the first request in my browser always fails, I get this error: Processing Base#index (for 83.xx.xx.xx at 2006-09-03 16:08:47) [GET] Session ID: f1918346d193e19a70c3230286e5ce1a Parameters: {} TypeError (superclass mismatch for class Stats): /app/models/stats.rb:1 stats.rb:1 just contains a normal A/R line: class Stats <

Hey folks, I''m falling behind in my Mongrel duties and seriously need to recruit an enterprising individual to take on the patch queue and help push out a new release with some minor fixes. The goal would be to just get patches that are currently languishing, pull them together, put them in the source, write some tests to try them, and then one slight design change. If this works out

Alright folks, after nearly a month of pounding and beating up the Mongrel 1.0 RC1 release we''re putting out the official 1.0.1 release. Read all about it at the (much funnier) news posting: http://mongrel.rubyforge.org/news.html For those people in a hurry, the gems should hit the mirrors and you can install using your usual commands. Refer the the above page for more help.

Hi, I kept getting a very weird question about Mongrel (http://mongrel.rubyforge.org) and SCGI that I think really needs to be cleared up: ** Mongrel is not SCGI and will never need, use, require, or interact with SCGI (unless someone wants to write the handler for it). ** For some reason people have been under the impression that Mongrel actually uses or interacts with my other project SCGI

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hello All, Yet another release of Mongrel proudly pushed out for everyone to review and comment on. This time though, I''ve done up a little website that''s *way* better than the plan Rdoc that used to stand in for the site like a one-legged leper. * http://mongrel.rubyforge.net/ As you should already know, Mongrel is a fast HTTP server and library for Ruby partially written in

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

Hi Everyone, Just want to get out another ping on the Mongrel pre-release saga. I''ve updated a bunch of the documentation to include documents people have donated and to beef up the FAQ for most of the questions people have asked over the past month. INSTALL gem install mongrel --source=http://mongrel.rubyforge.org/releases/ CHANGES * Fixed memory leak by switching to Sync rather

Hi Folks, I''ve been getting reports of people with serious stability problems in Mongrel. These problems go away instantly when they remove ruby-sendfile. If your mongrel starts up saying that you have "sendfile installed" and that it is using it then **you are wrong**. Remove the gem and don''t use it. I''ll be investigating why it doesn''t really