similar to: rspec-rails gem double quoting (My)SQL?

On Wed, Oct 14, 2009 at 5:49 PM, Scott Taylor <scott at railsnewbie.com> wrote: > > On Oct 14, 2009, at 3:36 PM, Joaquin Rivera Padron wrote: > > hello there, > how do you tipically spec private methods? The thing is ? have something > like this: > > def some_method > ?? complex_method + other_complex_methods > end > > private > def complex_method...

Inspired by Nick Evans'' RSpec progress bar[1], I had a little crack at implementing the progress bar for cucumber, ''cause I want to know how long a break I can take while the features are running :) It''s in my fork, in the coverage_formatter branch: http://github.com/mattwynne/cucumber/tree/master It will dump failing feature, scenario, step and the exception as

Hi, I am trying to learn Cucumber. I have followed the tutorial on "http://www.ultrasaurus.com/sarahblog/2008/12/rails-2-day-3-behavior-driven-development/" Everything is working fine but my problem is it is not inserting any record in either development or test database. Can anyone tell me IS it the behaviour of the Cucumber or Am I missing something? Thanks, Tushar -- Posted via

I love the way I can throw a call to pending() in the top of an unfinished RSpec example and stop it from failing the build. Is there a similar way to do such a thing with good ole'' cucumber? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former,

Since upgrading to Cucumber 0.1.99.19 I''ve noticed that the backtraces appearing in the console output are of the form: Page load was not successful (Code: 500): Followed by the dump of the rails error page. That page looks fine in a browser, and it''s helpful enough to see it when save_and_open_page does its thing, but I''m pretty used to reading plain old

Hi all, In GOOS[1] they use an assertion called assertEventually which samples the system for a success state until a certain timeout has elapsed. This allows you to synchronise the tests with asynchronous code. Do we have an equivalent of that in the Ruby / RSpec world already? I know capybara has wait_until { } but that''s fairly rudimentary - the failure message isn''t very

Hi there I have a weird situation. I have inherited a project in Rails 1.2.3 that has been upgraded to Rails 2.3.14 (and is running). I have installed Cucumber and Rspec to start to write features/tests for the new code that needs to be written. In my Gemfile, these Gems are loaded: group :test do gem ''rspec-rails'', ''~> 1.3.4'', :require =>

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] =

Hey guys, I''d never used RSpec Stories before, so I decided to follow the apparent direction of the wind and just jump right into cucumber. I''m dabbling with/using Cucumber and really like it. Good job, aslak! Where i''m struggling right now is using either fixtures or a model factory methodology like the FixtureReplacement. In both cases, I''m not

In a Cucumber step definition, I''m trying to login, but I keep getting this error: You must activate the Authlogic::Session::Base.controller with a controller object before creating objects (Authlogic::Session::Activation::NotActivatedError) My code: Given /^I am the logged in (.+) "(.+)"$/ do |role, login| user = User.create!( :login => login, :password =>

Hey all, As some of you may know I created the Cucumber TextMate bundle: http://github.com/bmabey/cucumber-tmbundle/tree/master What most of you probably don''t know is that I stopped using TextMate (in favor of Vim) several months ago. Since then the Cucumber bundle has been somewhat neglected by me and I''ve mostly pulled in patches and regenerated the syntax for new

What''s the best way to handle a requirement that shows up as a sub-requirement requirement in other features? For example let''s say users can enter dates in various forms throughout my application. There is one set of global rules specifying the formats in which dates may be entered, and how they are interpreted. I put that in one feature. In various other features, like

On 16 Apr 2009, at 11:22, Joaquin Rivera Padron wrote: > at the moment I do it this way, hiding the complexity out of the > steps: > > Then /^I should see the people search form$/ do > people_search_form_exists > end > > Then /^I should not see the people search form$/ do > people_search_form_exists "not" > end > > and then the method: > >

I think it is a common test case you would meet. For example, you want to test a user registry scenario. You write: Scenario: User Registry When I dosth Then I dosth ... And now business has some changes. Register should have to activate his account by a secret code sent by mobile phone. So you need to write the other scenario: Scenario: User Registry and Account Activation By Mobile

Is it possible to create a stub that returns hash values. For example I would like to convert this: @siteItem = stub(''plmSiteItem'', :one => "uno") To something like this: @siteItem = stub(''plmSiteItem'', {''one'' => ''uno'', ''two'' => ''dos''} ) So that I can do this:

Hey list, Anyone have experience with acts_as_xapian and Cucumber? I''m struggling with updating xapian''s index, to actually "find" fluff that has been indexed.. In a scenario, I''m adding a bunch of articles, and in the actual search step, I run: When "I search for \"$query\"" do |query| %x[rake RAILS_ENV=test xapian:update_index]

Hi, I was writing an integration test for my user signup form (with capybara), and found that my test was failing due to a validation error: "email is already taken". I''m a bit confused because I thought when I run "rspec spec/some_spec.rb", the test database would be wiped clear? Is that not the case? Patrick J. Collins http://collinatorstudios.com

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

Hi, I''m struggling with something that seems to be simple, and I''ve not had any joy following the RSpec books suggestions (p. 187). I''d like to test that a method raises and error when a file is not found. I''ve tried adding this in my example just before I call my method, but it never seems to get invoked. Pathname.stub(:exist?).and_return(false) The whole

Hi All, I want to know the EOL date for the below gems for ROR. Can anyone help me how to find the EOL dates - authlogic - will paginate - oauth-plugin 0.3.14 - statistics 0.1.1 - YUI - cucumber 0.6.4 - cucumber-rails 0.3.0 - rspec 1.3.0 - rspec-rails 1.3.2 - webrat 0.7.0 - factory-girl 1.2.4 - database_cleaner 0.5.0 - SSL requirement - calender_select