similar to: behavioural testing of puppet manifests with cucumber-puppet

Hi all, Firstly, I''m using 2.6.9 and have updated to the latest cucumber puppet gems (cucumber-puppet 0.3.5) that allow for storeconfigs to be tested - thanks to Nikolay and his post (http://blog.nistu.de/ 2011/09/04/testing-exported-resources-with-cucumber-puppet/). Yay! I have been trying to get some testing of a ''testnode'' which would be a generic node that I can

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

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

Hey everybody I''m sorry, I know that this question seems to arise every few moments, but I think in my case it''s a bit special (but doesn''t everybody?). Well, I''m working with RoR on a private level since v1.0, and my knowledge about both Ruby and Rails are on a basic level (but definitely does exist), but I''m in no means near being an expert yet. In

Railers, I am running an application on Rails 2.3.2. For some reason within our organization, we wish to remain on this version of Rails. For BDD/Testing, we use Cucumber. So I installed Cucumber (0.8.5), Capybara (0.3.9) and Selenium-webdriver (0.0.17). But when I run Cucumber on any feature, I get an error saying *" wrong number of arguments (2 for 1) (ArgumentError)"*, (Check here

I am working on my first Rails BDD project with extensive tests since starting out with Rails a few years ago. Running RSpec or Cucumber is really slow. I''m using Rails 3 and RSpec 2. To run one model spec with only 5 tests takes almost 1 minute! When it finishes it says it took only 0.9 seconds to run the actual test. So obviously it is loading the environment that takes so long. I just

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for

Hello, I was hoping that someone may point me to a github public repo that is a rails 3, outside in designed project with cucumber and Rspec. I read the Rspec book, though found it too brief and just surfing Github I only find gems and rails 2 projects. I guess one thing that I don''t understand fully well is the role of unit testing. The feeling I get is pure BDD doesn''t

Cucumberists (and RSpec Classic users ;): How can we convert a Cucumber feature file into HTML with syntax highlighting? Not the test-runner output; that''s preprocessed so it does not match the input file... Tx! -- Phlip

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

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:

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

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

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 >

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