similar to: [PATCH] option_groups_from_collection_for_select should produce an HTML-safe string

I posted a quick screencast demonstrating some BDD with RSpec yesterday: http://wincent.com/a/about/wincent/weblog/archives/2007/05/ behaviourdriven.php I''m a C/Objective-C programmer who knows a bit of Ruby, almost nothing about Rails, and in BDD I can really only claim "new but interested" status. It''s not scripted, it''s totally improvised and

Rails documentation gives examples of using option_groups_from_collection_for_select with two tables/objects. How could it be done with one? Example that almost works: I have a form to enter address from both the United States and Canada. It has the following: ====new.html.erb==== <%= select_tag( :state, option_groups_from_collection_for_select( State.countries, :country,

Hello, I am having some difficulties with ActiveRecord. What I want to do is to get a collection of SubjectGroups for using with option_groups_from_collection_for_select My Code: ======================================== class Subject < ActiveRecord::Base has_and_belongs_to_many :users belongs_to :subject_group end class SubjectGroup < ActiveRecord::Base has_many :subjects end

Where should the specs go for code in the "lib" directory of a Rails app? I made a folder, "spec/lib/", for storing such specs, and RSpec automatically picks them up when run using "rake spec". Before I go ahead and patch rspec_on_rails/lib/autotest/ rails_rspec.rb so that autotest can monitor these specs I''d like to ask whether this is the

I''m trying to get really serious about doing true BDD for a new Rails project, and I note that at <http://rspec.rubyforge.org/documentation/ rails/index.html> it says: "we really don?t recommend the use of rails fixtures" On the same page it also says (about Model specs): "these are the only specs that we feel should actually interact with the database"

Given the following ApplicationController specs: describe ApplicationController, "one facet", :shared => true do it ''foo'' ... it ''bar'' ... end describe ApplicationController, "some other facet", :shared => true do it ''abc'' ... it ''xyz'' ... end describe

Autotest is running continuously - even when the files mtimes aren''t changing. I believe this only happens if using a failures file. autotest -v gives me: euclid% autotest -v loading autotest/rails_rspec /opt/local/bin/ruby -S script/spec -O spec/spec.opts spec/ controllers/log_entries_controller_spec.rb spec/views/login/ new_spec.rb spec/controllers/login_controller_spec.rb

The Rails ApplicationController (app/controllers/application.rb) serves as an abstract superclass for all other controllers in a Rails application and is a good place to put methods and filters which you want all of your controllers to use. In my case I''m using it to provide methods such as "current_user" and "logged_in?" etc. By default, RSpec

Hi all, I committed a first cut at blockless Givens/Whens/Thens to RSpec''s trunk: cd /path/to/rspec/project svn up cd rspec bin/spec examples/story/calculator.rb Take a look at examples/story/calculator.rb to see what''s going on. Needs docs!!!! Thoughts welcome. I''ve also got a cut at the plain text parser checked in, but it''s not hooked up to anything

This may have turned up in the RSS feeds of many of you already, but for those who haven''t seen it yet, looks intersting: <http://errtheblog.com/post/7708> > The main problem with fixtures, for me, has always been how unfun > they are. They literally suck the fun out of anything they?re > around. You throw them in your test/ directory, then suddenly > testing

First up, congratulations to the team on RSpec 1.0.0! RSpec is one of the most vibrant and professionally-run projects in the world of Ruby open source. Now that there is a commitment to a stable API I think we''ll see RSpec really take off. Two quick things... In the absence of official Spec::UI docs, can Spec::UI be installed as a Rails plug-in? eg. script/plugin install

Hi Are there any tools around that make rspec''s failure messages easier to read? unit_diff from ZenTest doesn''t seem to work - unless I missed something. A simple but very helpful improvement would be to use more line- breaks, e.g. Current output: expected "this is a very long string blah blah", got "this is a very very long string blah blah" (using

Recently as a result of using Git I''ve noticed a number of inconsistencies in the RSpec codebase with respect to whitespace (mixed line endings, mixed use of spaces and tabs for indentation, and trailing whitespace at the end of lines). I never would have noticed, but Git produces nice colorized diff output which highlights these kinds of inconsistencies. I wanted to ask if the

Hi, in my development environment (Ruby 1.87, Rails 2.3.8) the following code works fine: <%= select "applicant", "member_1", option_groups_from_collection_for_select(@topics, :members, :topic, :id, :name, @applicant.member_1), {:include_blank => true} %> Producing: <optgroup label="Clinical Neuroscience"> <option value="1">Prof

How can I scope the options returned by option_groups_from_collection_for_select? Method calls look like this: option_groups_from_collection_for_select (collection, group_method, group_label_method, option_key_method, option_value_method, selected_key = nil) But say I want to limit the results returned by the option_key and option_value methods to some particular scope? For instance, using the

Has anybody had any luck getting Cucumber, Webrat and Selenium to play nicely together for SSL sites? My test environment: - nginx front-end accepting SSL requests, proxying them to mongrel back-end - mongrel back-end accepting normal HTTP requests - application routes configured with ":protocol => ''https''" so that URLs generated with "_url"

When writing view specs is there any way to test not only for the presence of tags (have_tag) and nested tags (with_tag), but also test that they appear in a given order? For example, consider the following: it ''should display the login names, display names and email address in alternating rows'' do response.should have_tag(''div.odd>div'') do

I think we all know that the readability of steps isn''t great right now, and in fact there''s a very recent thread that discusses just that. It was that recent thread that prompted me to explore this a bit. The basic idea is that you define step matchers, which have a regex, and then you match step names against that regex. Kind of tough for me to explain so I''ll just

# How would you best perform a secondary sort on :buildings below? = ''Building Name'' = select_tag ''building_id'', | option_groups_from_collection_for_select(Site.all(:order => :full_name), | :buildings, :full_name, :id, :full_name, nil) | -- Thanks, Tyler Arrigoni President OneInterface.net Network Engineering, Inc. 7475 North Palm, Suite 105, Fresno,

I''ve submitted a small patch to make Rails behave properly with the Erubis <%== %> construct. For some reason the current behaviour of that tag in Rails 3 is to escape the contents _twice_ which is probably a bug. I offer three suggestions why this is a good idea: - The syntax is cleaner. It can avoid a lot of .html_safe and raw in your views. I especially like the conciseness of