search for: josephwilk

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

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

Hello, Anyone working in QA Test Automation with RSpec wouldn?t mind posting their testing framework or know where I can go to get more info on testing frameworks either with RSpec or Cucumber? I greatly appreciate. Thank you.

Hi, Is there a hook or a method to execute some code after a whole feature has run or will I need to embed that in a ''Then''? Regards Aidy

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

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

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

Hi, I''m working on update my local Cucumber to the latest version. But it seems the old formatter APIs(step_failed, scenario_executed, etc.) don''t work any more. Are there some documents or even Cucumber source code I can refer to? Thanks in advance, Liu -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Anyone recognise this exception, and know what causes it to happen occasionally? Thanks Ashley Scenario: new story appears on feed # features/descriptions/ story_notification.feature:12 /opt/local/lib/ruby/gems/1.8/gems/cucumber-0.1.10/bin/../lib/cucumber/ broadcaster.rb:15:in `write'': Bad file descriptor (Errno::EBADF) from

I''m working on writing features for a wizard. The wizard collects information from a number of different forms, and you can navigate through it in a number of ways. Anyhow one of these forms is a customer form collecting name, and email. In the context of the wizard I feel that the following scenarios Scenario: Given I step to customer And I fill in my customer details