similar to: Getting the file a scenario is defined in (Cucumber)

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

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

I have a bunch of fixtures designed to populate the database for my Cucumber integration tests. But at this stage I want my database to be empty when using Rspec. So, I moved the fixtures from `/spec/fixtures` to `features/support/fixtures`, and updated `features/support/env.rb` to read: Fixtures.reset_cache fixtures_folder = File.join(RAILS_ROOT, ''features'',

Hi all. If I run rake features or cucumber features/* I get one failing FIT scenario in one of my features. If I then run that feature that contains the FIT table with the failing scenario manually, it passes. I run it again with rake features or cucumber features/* it fails, run individually, it passes. Obviously some state is carrying over between the features. Any idea where i would start

I''m having problems knowing what a scenario outline I''ve created is doing. In particular I have no idea about what steps are being matched when the outline is run so when I break something I can''t find out what is wrong. Is there any progress on getting better output for scenario outlines. TIA Andrew -------------- next part -------------- An HTML attachment was

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]

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 #

I''m trying to set up cucumber so we can try it in some Ruby automation scripts I''m working on. These will be straight Ruby, for use in BBEdit and TextMate (on the Mac). NOT Rails. The big early-stage stumbling block I''m having is setting up the initial Rakefile and directory structure. I think I''m rtfm''ing, but clearly I''m missing

Hi, I''m trying to start using cucumber. I''ve done login, logout scenarious, but stumbled in CAPTCHA validation on user registration page. As I get I should stub CAPTCHA validation method. I guess I should implement stubbing Given step or include stubbing code in Before filter? I use validates_captcha gem, thus instance method to stub is module ValidatesCaptcha module

I''m trying to find an effective way to validate the following: I have 3 form fields, a select menu a checkbox and a textfield. They can all be left blank on submission, but if you select two or more it should prompt an error. If the user chooses to, only one field should be allowed to be submitted. I tried the following but it seems to be breaking my cucumber scenario. Only the first

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

I''m just curious about this, since my solution involved stubbing a call to GeoIp. Is there a good rule of thumb for when you make exceptions to the ''no stubbing'' philosophy of Cucumber? My step was: "Given I am accessing the site from Japan," but I can think of other situations - mostly when interacting with web services, that I''d probably

Hi there ! I was wondering if the way I test the validation of my forms is right or not. So here''s a little example : Imagine you have a form with some validations designed to create some object. You want to test it using Scenario Outline and Examples. So you fill in the fields using <value>, and press the create button. Then you "should see" (using webrat) the

Assuming you have a multi-step wizard like thing, with lots of different states and paths through it. What approach would your use to write a feature for it? What I want to do is do the separate states and then reuse these things in more complex scenarios that cover paths. For example Scenario: State A Given I''m ... And I''m ... When I ... Then I should see And I at

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

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, 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

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.

Hi! And now for the second part of the subject of my previous mails :) $ cat cucumber.yml default: . autotest: -v . autotest-all: -v -f progress . $ cucumber -i . -f progress PP Pending Scenarios: 1) enlightenment (meditation) $ AUTOFEATURE=true autospec # bug! prompt returns immediately, ZenTest gem not a dependency? a warning that autotest was not found would be nice. $ sudo gem

Where and how do you put custom logger statements in cucumber? I understood (more or less) how to do this in rspec in the spec_helper file but I do not know where to start with cucumber. I want to add a simple identifying text line in the log file to assist in picking through the output. Something akin to: Running Scenario: X Feature I should have this logged .... Feature This should