similar to: Reflections on and questions about the describe/it syntax

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

Hi there, I''ve installed rspec, rails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails

Hi there, I''ve installed rspec, rails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails

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

First of all hi, I''m new to the list, and rather new to rspec as will probably show in myquestion. I have tried installing rspec and rspec_on_rails as plugs both using "script/install" and "piston import" commands using the "current release install instructions" here [1]. However, there doesn''t seem to be any mention of the rspec_resource

I''m just getting started with rspec, I''m running on edge for both. In a fresh project, I freeze edge, install the edge rspec plugin. I generate a simple rspec_model and run the spec. It passes. When I run rake spec:doc, I get the following output: - NO NAME (Because of --dry-run) where the specification should be. In fact if I just make a pending spec, it does the same.

I want to find out what are the associations with another active record class. So If my class is as below: Class Component < ActiveRecord::Base has_many :branches end class Branch < ActiveRecord::Base belongs_to :component end and then I do Component.reflections[:branches].active_record I would expect that to be Branch but it is in fact Component. The inspection of

https://bugs.freedesktop.org/show_bug.cgi?id=96443 Bug ID: 96443 Summary: Missrendering of Reflections in Talos Principle Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

I have the latest version of rspec and rails-rspec installed. I''m using the debian versions of ruby and rails. On a new project after a generate an "rspec_model" and then try to run "rake spec", I get the following error: dan at dan-server:~/projects/cw/registration$ rake spec (in /home/dan/projects/cw/registration)

[This is a follow up on gcc3 vs. gcc4 discussion. Background: R benchmark tests ( http://www.sciviews.org/benchmark/index.html ) show a dramatic difference in "Escoufier's method on a 37x37 matrix (mixed)" test when comparing binaries for PowerPC compiled with gcc3 vs gcc4.] On Oct 16, 2006, at 11:29 AM, Ren? J.V. Bertin wrote: > Anyway, it has nothing to do with the G4

Hi there, I''m having trouble with `rake spec:models`. It''s failing on: - 1 old rspec/rails project - all new rspec/rails projects But, it *is* working fine on my other (older) rspec/rails projects. All projects are on rspec & rails 1.0.8, Rails 1.2.3, os X ppc Here''s a fresh rspec/rails project with failing rake task $ rails test_app -d postgresql $ cd

I came across a quite interesting post from Ross Ihaka, thought would be good to share it and get the opinion of folks around here. I am not sure where to post this for the R community but since it has to do with development I thought or R-devel Ross Ihaka Newsgroups: comp.lang.lisp From: Ross Ihaka <ih... at stat.auckland.ac.nz> Date: Wed, 23 Jan 2008 10:35:26 +1300 Local: Tues, Jan 22

Hello everyone, I''m new in contributing and i saw in the contributing-guides, that i have to write an email at this list. I hope, that''s the right place for this. If it''s not, i''M really sorry.. ;) Could someone please give me feedback about this lighthouse-ticket?

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

Hello ups-dev Arnaud asked me to add a function upsdrv_print_ups_list the drivers upsdrv_print_ups_list : why This function would print the vendorId and the productId of the UPS supported by the driver (for USB driver at least). It could then be parsed by a tool (that I'll have to make too), whose the goal would be to automagically generate 4 sort of file : - fdi file for HAL - udev rules

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"

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

Can somebody please review my ticket: https://rails.lighthouseapp.com/projects/8994/tickets/4879 It''s a trivial bugfix ("option_groups_from_collection_for_select should produce an HTML-safe string") before RC, I think. Cheers, Wincent -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group,

Xapians! If tomorrow Xapian search engine would achieved the same performance and result in searches as Google we would not be able to beat Google, because we would create only a copy of the searches that already exists from Google search engine. However there is a way to beat anyone, and there is a way to beat Google successfully as well just do not give up. Some see it as implementing Ajax, or