similar to: [Cucumber] pretty html output?

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

I finally plunked down for the beta RSpec bundle and I''m working through the initial example. Although I''m a fairly experienced RSpec user, I''m stlll learning new tricks. Anyway, I''m going though the mastermind example, and everything is going well, except that I decided to also try out the Textmate bundle for Cucumber. I decided to use Ben Mabey''s

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

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]

Rodrigo Flores wrote: > Hi > > I''m reading the rspec book and I''m having problems when I require the > file ''spec/stubs/cucumber''. When I go to an IRB prompt and type > require ''spec/stubs/cucumber'' after requiring another libraries [1] I > get the false in ''spec/expectations'' and an error in >

Big news for all Java programmers out there. Now you can use Cucumber with pure Java! That''s right, you don''t have to write a single line of Ruby! (1) All of your step definitions can be written as annotated methods in POJOs (Plain Old Java Objects). To get a taste of what this looks like, check out the simple example in the cucumber_java project on GitHub: * README for

OS=CentOS-5.2 Ruby=1.8.6 Rails=2.2.1_RC Gems all up to date I have been experimenting with autotest and I have a few questions. 1. given export AUTOFEATURES=TRUE if ./test exists (with tests) then these tests are run and the features are not. Is this intended behaviour? 2. given require ''autotest/redgreen'' in .autotest if /test tests are run then all I get colourized is a

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.

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

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

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

when ranning cucumber:install and generate me this files <code> create config/cucumber.yml create script/cucumber chmod script/cucumber create features/step_definitions create features/support create features/support/env.rb exist lib/tasks create lib/tasks/cucumber.rake gsub config/database.yml gsub config/database.yml force config/database.yml </code> im searching for the

Hi! I''m using cucumber + selenium and I love it. However I''m looking to add some methods (example: click_and_wait etc) to the lib. Therefore looked around a bit and I got two questions: Firstly about rspec-ui, I''m a little confused, does rspec-ui overlap with its propose with webrat with cucumber or I''m missing a point? Secondly, are there any plans to

I''m just starting on BDD. I installed the gems for webrats and cucumber. I also ran the following in the Ruby shell: >rake gems:install RAILS_EN=test >script/generate cucumber These commands seemed to create the expected features and lib folders in my project. I''m using the eclipse framework with Aptana and RadRails as my IDE. However, when I run: >cucumber features

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:

I''ve just upgraded RSpec to 1.2 on a Rails 2.2.2 app. rake features fails with the following error: /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/ dependencies.rb:442:in `load_missing_constant'': uninitialized constant Spec::Ruby (NameError) from /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/ active_support/dependencies.rb:77:in

Hello, I have a Rails3beta4 project where I want to use rSpec stubs in a Cucumber feature. Unfortunately it looks like requiring ''spec/stubs/cucumber'' in env.rb does not work anymore: I get a "no such file to load -- spec/stubs/cucumber (LoadError)" error. Is it possible to use rSpec stubs in Cucumber with rSpec2? If not, is there any other viable alternative? Thanks

Hello, Is there any way to test controllers using cucumber. I was doing it with rspec but since cucumber''s description is good how can i proceed testing it with cucumber? For e.g. I have a scenario of user creation like Feature: User Scenarios Scenario: Successfull creation of user Given a new user When the user fill all the mandatory details Then that user should get

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

Can anybody tell me how to pass a variable from the rake command to my steps file using cucumber? I have the following in my Rakefile: ## Rakefile Cucumber::Rake::Task.new do |t| profile = ENV[''PROFILE''] || ''default'' browser_type = ENV[''BROWSER''] || ''*chrome'' t.cucumber_opts = "--profile #{profile}" end I