similar to: deprecate integrate_views, WDYT?

describe MyController do integrate_views describe "A common base senario" do it "no longer integrates views" do be_careful end end end integrate_views affects an attribute in the class formed by the describe factory method. The second describe generates its own class, so integrate_views is OFF at that level. I''ve already spent far, far too much

Hi all, There are two tickets in lighthouse that point to problems with the use of context() in RSpec: * conflict with JRuby: http://rspec.lighthouseapp.com/projects/5645/tickets/728 * request context() be deprecated http://rspec.lighthouseapp.com/projects/5645/tickets/713 As there are a lot of people (and libraries) that mix and match describe() and context(), I don''t plan to

I wanted to use "integrate_views" as Ryan explains in his RailsCast #71 (http://railscasts.com/episodes/71) ...but I can''t get it to work: the view code in not executed I looked everywhere but I can''t understand what I am doing wrong. Here is what I did: I created a new application from scratch (Rails 2.0.2), added rspec and rspec_on_rails plugins, and run

Hello, I have a controller action that raises a RecordNotFound exception if you''re not allowed to see something. In my global application controller (application.rb), I catch these and render the 404 template. But when I run cucumber (using webrat), it''s getting the full stacktrace (the step blows up). Any ideas why? I have consider_all_requests_local turned off in my test.rb.

Hi all, Where can we add tickets for Cucumber? While trying to migrate a current project I ran into a snag.. specially that cucumber does not support multi-line steps like the edge rspec story runner (which makes sense since this was such a new feature to the story runner.) Anyways, I don''t have enough time at the moment to dig into it myself so I''d like to at least log it.

Is there a way to always use integrate_views for all controller specs? I hate having to remember to insert that line into each one. Thanks, Joe

Seem to be getting a problem when running a feature with background. Running the whole file works fine however running an individual feature fails. The background steps are Background: Given an admin user Philip exists When I login as Philip Then I should be logged in as Philip running the following scenario on its own causes an error Scenario: Admin should be able to run a feed #

Hey all, Anybody use the --dry-run command line option? I''m planning to deprecate it if nobody has a compelling reason to keep it. Please post your comments in the ticket: https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/781-deprecate-dry-run Thanks, David

Hey all, Does anyone know how to disable the cucumber autotest support on a project? With this commit: http://github.com/aslakhellesoy/cucumber/commit/93470e2580b5e3cfe0c8eb3fce86e21bf8afa219 The cucumber features are worked into the autotest cycle automatically. This is cool, but on some projects I don''t think it fits well with my red->green->refactor cycle. Any ideas on

hiya, i want the selector that would return a <tr> of a table if any td contains some text, so i can use it in click_link_within e.g. When I click the "show" link within the row containing "user at example.com" When /^I click the "(.+)" link within the row containing "(.+)"$/ do | link, text| selector = ?? click_link_within selector, link

Last night it seemed like the mailing list was playing catchup, as I got a flood of emails from the past few days. Has anyone else seen this? -- Zach Dennis http://www.continuousthinking.com http://www.mutuallyhuman.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20081030/f19f3755/attachment.html>

I've having trouble downloading and compiling Xapian 1.0.19 on OSX 10.5.8. Does the below error look at all familiar to anyone? creating bin/quartzcheck g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I./backends/quartz -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Woverloaded-virtual -Wundef -Wshadow

Hi The code I''m working on now is a server daemon that talks to Twitter, an RSS feed, and some web pages. I''ve got mock implementations of Twitter and the web stuff, which I start and stop with daemon_controller[1]. I do all the setup in a Before block, but this makes the feature runs agonisingly slow due to the time waiting for everything to restart. I''m

On Thu, Jul 9, 2009 at 5:40 AM, Daniel Tenner<daniel.rspec at tenner.org> wrote: > Hi all, > Like everyone (?), I use nested contexts to keep my specs well organised and > tidy. > However, I have a problem. I have various sets of specs that needs to > perform very time-expensive operations to set up the fixtures that will be > examined in the tests. Two specific examples:

Hi all, I just submitted a patch to 2-3-stable on lighthouse and wanted to bring it to folks general attention. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/896-be-a-little-more-discerning-about-which-exceptions-to-handle My explanation is a bit long-winded, but here''s the motivation for the patch, as explained in the lighthouse ticket: Perhaps I should open

I am working with the authlogic gem and trying to create a simple login test from cucumber features. The feature statement is: Given the user is not logged in The step definition for this is confounding me. In the application_controller the authlogic tutorial recommends the following: private def require_user unless current_user store_location flash[:notice] =

Hi everyone, I just created my first rails patch. It is a simple textile doc error requiring only a single word to be changed. https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5779 I uploaded a .diff file. Not sure what to do now but lighthouse guide says I should ask on here for someone to take a look. Thank you for your time, fooledbyprimes Peoria, Illinois, USA --

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?

In Rails 3 the only way to get for content captured with the content_for method in a view is to call yield from within a view. However, sometimes is it useful to get to this data from within a helper (for instance to provide a default value). Calling yield from within the helper method won''t work, and accessing the @_content_for variable directly is not encouraged. Proposed solution: add

I am using Cucumber 0.2.3 and am having problems running a single feature. In particular, the cucumber Textmate bundle was not working so I traced it back and discovered that I could not run single files or features from the command line either. My setup has the following line in cucumber.yml default: -r features/support/env.rb -r features/support/plain.rb -r features/steps