cucumber-nagios 0.5.0

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2009 Lindsay Holmwood
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,224 @@
+cucumber-nagios
+===============
+
+cucumber-nagios allows you to write high-level behavioural tests of web 
+application, and plug the results into Nagios. 
+
+As Bradley Taylor [put it](http://bradley.is/post/82649218/testing-dash-metrics-with-cucumber): 
+
+    “Instead of writing boring monitoring plugins from scratch, 
+    you can now do behavior driven ops!
+
+    Transform from a grumpy, misanthropic sysadmin to a hipster, 
+    agile developer instantly.”
+
+
+Quickstart
+==========
+
+ 0. `gem sources -a http://gems.github.com`
+ 1. `gem install auxesis-cucumber-nagios`
+ 2. `cucumber-nagios-gen project bunch-o-tests`
+ 3. `cd bunch-o-tests`
+ 4. `rake deps`
+ 5. `bin/cucumber-nagios-gen feature ebay.com.au bidding`
+ 6. `bin/cucumber-nagios features/ebay.com.au/bidding.feature`
+
+
+Setting up a project
+====================
+
+To set up a standalone `cucumber-nagios` project, run:
+
+    cucumber-nagios-gen project <project-name>
+
+This will spit out a bunch of files in the directory specified as `<project-name>`. 
+
+Check the `README` within this directory for specific instructions for managing
+the project. 
+
+
+Freezing 
+========
+
+** This is really manky at the moment. cucumber-nagios will be switching to
+wycats' bundler at the next major release! **
+
+Freezing your dependencies into your project allows you to drop your 
+`cucumber-nagios` project to any machine and have it run. Its only requirement is 
+Ruby and Rake.
+
+To freeze your project, within your project directory run:
+
+    $ rake deps
+
+Redeploying
+===========
+
+Once you've copied your project around, Just run the freezer again: 
+
+    $ rake deps
+
+Writing features
+================
+
+Once you've set up a project, you can use the `bin/cucumber-nagios-gen` command
+to generate new features. It takes two arguments: the site you're testing, and 
+feature you're testing: 
+
+    bin/cucumber-nagios-gen feature gnome.org navigation
+
+This will spit out two files: 
+
+    features/gnome.org/navigation.feature
+    features/gnome.org/steps/navigation_steps.rb
+
+
+As for writing features, you'll want to have a read of the 
+[Cucumber documentation](http://wiki.github.com/aslakhellesoy/cucumber), however
+your tests will look something like this:
+
+    Feature: google.com.au
+      It should be up
+      And I should be able to search for things
+    
+      Scenario: Searching for things
+        Given I visit "http://www.google.com"
+        When I fill in "q" with "wikipedia"
+        And I press "Google Search"
+        Then I should see "www.wikipedia.org"
+
+There's a collection of steps that will cover most of the things you'll be 
+testing for in `features/steps/webrat_steps.rb`. 
+
+You can write custom steps for testing specific output and behaviour, e.g.
+in `features/smh.com.au/smh.feature`: 
+
+    Feature: smh.com.au
+      It should be up
+      And provide links to content
+    
+      Scenario: Visiting home page
+        When I go to http://smh.com.au/
+        Then I should see site navigation
+        And there should be a section named "Opinion"
+
+There aren't steps for "Then I should see site navigation", so you have to 
+write one yourself. :-) In `features/smh.com.au/steps/smh_steps.rb`: 
+
+    Then /^I should see site navigation$/ do                                                                    
+      doc = Nokogiri::HTML(response.body.to_s)                                                                  
+      doc.css("ul#nav li a").size.should > 5                                                                    
+    end
+
+You can use Nokogiri for testing responses with XPath matchers and CSS 
+selectors. 
+
+I suggest you use `bin/cucumber` directly so you can get better feedback when 
+writing your tests:
+
+    bin/cucumber --require bin/common.rb \
+                 --require features/ 
+                 features/smh/smh.feature
+
+This will output using the default 'pretty' formatter. 
+
+Running
+=======
+
+Invoke the Cucumber feature with the `cucumber-nagios` script: 
+
+    bin/cucumber-nagios features/smh.com.au/smh.feature
+
+`cucumber-nagios` can be run from anywhere: 
+
+    /path/to/bin/cucumber-nagios /path/to/features/smh/smh.feature
+
+It should return a standard Nagios-formatted response string: 
+
+    Critical: 0, Warning: 0, 2 okay | passed=2, failed=0, total=2
+
+Steps that fail will show up in the "Critical" total, and steps that pass 
+show up in the "okay" total. 
+
+The value printed at the end is in Nagios's Performance Data format, so it
+can be graphed and the like.
+
+Benchmarking
+============
+
+You can benchmark your features if you need to test response times for a set of
+site interactions: 
+
+    Feature: slashdot.com
+      To keep the geek masses satisfied
+      Slashdot must be responsive
+    
+      Scenario: Visiting a responsive front page
+        Given I am benchmarking
+        When I go to http://slashdot.org/
+        Then the elapsed time should be less than 5 seconds
+
+The elapsed time step can be reused multiple times in the same scenario if you
+need fine grained testing: 
+
+    Feature: slashdot.com
+      To keep the geek masses satisfied
+      Slashdot must be responsive
+    
+      Scenario: Visiting news articles
+        Given I am benchmarking
+        When I go to http://slashdot.org/
+        Then the elapsed time should be less than 5 seconds
+        When I follow "Login"
+        Then the elapsed time should be less than 4 seconds
+        When I follow "Contact"
+        Then the elapsed time should be less than 7 seconds
+
+
+
+Quirks & Caveats
+================
+
+Multiple scenarios
+------------------
+
+You may want to think about keeping to one scenario to a file, otherwise 
+you'll get multiple lines of output for a test:
+
+    Critical: 1, Warning: 0, 2 okay | passed=2, failed=1, total=3
+    Critical: 1, Warning: 0, 4 okay | passed=4, failed=1, total=5
+
+That said, Nagios should only read the last line, so this might be an ok 
+behaviour when you want to test for an aggregate of failures across a site.
+
+Failure *is* an option (exceptions are good)
+--------------------------------------------
+
+Exceptions raised within your tests will appear in the failed totals, so you 
+don't need to worry about trying to catch them in your own custom steps. 
+
+i.e. if you try fetching a page on a server that is down, or the page returns 
+a 404, the exception raised by Mechanize just gets treated by Cucumber as a 
+test failure. 
+
+
+Version control
+===============
+
+It's highly recommend that you store your cucumber-nagios projects in a version
+control system!
+
+To get up and running with git: 
+
+    $ git init
+    $ git add .
+    $ git commit -m 'created cucumber-nagios project'
+
+To get up and running with bzr:
+
+    $ bzr init
+    $ bzr add
+    $ bzr commit -m 'created cucumber-nagios project'
+
+`.bzrignore` and `.gitignores` are created when you generate a project.

data/Rakefile

@@ -0,0 +1,27 @@
+#!/usr/bin/env ruby 
+
+require 'rubygems'
+require 'fileutils'
+
+begin 
+  require 'cucumber/rake/task'
+   
+  Cucumber::Rake::Task.new do |t|
+    t.cucumber_opts = "--require features/"
+  end
+rescue LoadError
+end
+
+
+desc "build gem"
+task :build do 
+  system("gem build cucumber-nagios.gemspec")
+
+  FileUtils.mkdir_p('pkg')
+  puts
+  Dir.glob("cucumber-nagios-*.gem").each do |gem|
+    dest = File.join('pkg', gem)
+    FileUtils.mv(gem, dest)
+    puts "New gem in #{dest}"
+  end
+end

data/bin/cucumber-nagios-gen

@@ -0,0 +1,50 @@
+#!/usr/bin/env ruby
+
+require 'rubygems'
+require 'templater'
+
+module CucumberNagiosGenerators
+
+  extend Templater::Manifold
+
+  class ProjectGenerator < Templater::Generator
+    def self.source_root
+      File.join(File.dirname(__FILE__), '..', 'lib', 'generators', 'project')
+    end
+
+    def destination_root
+      # takes :name from first_argument
+      File.join(@destination_root, name)
+    end
+
+    desc "Generate a new self-contained cucumber-nagios project."
+    first_argument :name, :required => true, :desc => "Project name"
+
+    file '.gitignore', '.gitignore'
+    file '.bzrignore', '.bzrignore'
+    glob! 
+
+  end
+
+  desc "Generate a cucumber-nagios project."
+  add :project, ProjectGenerator
+
+end
+
+
+CucumberNagiosGenerators.run_cli Dir.pwd, 'cucumber-nagios-gen', '0.1', ARGV
+
+puts <<-README
+Your new cucumber-nagios project is set up.
+
+To get going, you'll need to bundle gems into the project:
+  
+  $ gem bundle
+
+It's highly recommended you version control your projects:
+  
+  - with Git: git init ; git add . 
+  - with Bazaar: bzr init ; bzr add 
+
+README
+

data/features/creating.feature

@@ -0,0 +1,11 @@
+Feature: Creating new project 
+  To test websites 
+  A cucumber-nagios projert
+  Must be created
+
+  Scenario: Create a project
+    Given cucumber-nagios is installed
+    When I create a new project called "great-website-tests"
+    And I freeze in dependencies
+    Then my gems directory should be populated
+    

data/features/installing.feature

@@ -0,0 +1,11 @@
+Feature: Installation
+  To set up a cucumber-nagios project
+  A user
+  Must be able to install the gem
+
+  Scenario: Installing the gem
+    When I build the gem
+    And I install the latest gem
+    Then I should have cucumber-nagios-gen on my path
+    And I can generate a new project
+

data/features/steps/creating_steps.rb

@@ -0,0 +1,23 @@
+Given /^cucumber\-nagios is installed$/ do
+  When 'I build the gem'
+  And 'I install the latest gem'
+  Then 'I should have cucumber-nagios-gen on my path'
+end
+
+When /^I create a new project called "([^\"]*)"$/ do |project_name|
+  @project_name = project_name
+  FileUtils.rm_rf("/tmp/#{@project_name}")
+  
+  silent_system("cd /tmp ; cucumber-nagios-gen project #{@project_name}").should be_true
+end
+
+When /^I freeze in dependencies$/ do
+  @project_name.should_not be_nil
+  silent_system("cd /tmp/#{@project_name} ; gem bundle").should be_true
+end
+
+Then /^my gems directory should be populated$/ do
+  @project_name.should_not be_nil
+  Dir.glob("/tmp/#{@project_name}/vendor/gems/*").size.should > 0
+end
+

data/features/steps/installing_steps.rb

@@ -0,0 +1,27 @@
+When /^I build the gem$/ do
+  project_root = File.join(File.dirname(__FILE__), '..', '..')
+  rakefile = File.join(project_root, 'Rakefile')
+  File.exist?(rakefile).should be_true
+  
+  silent_system("rake -f #{rakefile} build").should be_true
+end
+
+When /^I install the latest gem$/ do
+  project_root = File.join(File.dirname(__FILE__), '..', '..')
+  pkg_dir = File.join(project_root, 'pkg')
+  pkg = File.expand_path(Dir.glob(File.join(pkg_dir, '*.gem')).last)
+
+  silent_system("gem install #{pkg} 2>&1 > /dev/null").should be_true
+end
+
+Then /^I should have cucumber\-nagios\-gen on my path$/ do
+  silent_system("which cucumber-nagios-gen").should be_true
+end
+
+Then /^I can generate a new project$/ do
+  testproj = "testproj-#{Time.now.to_i}"
+  FileUtils.rm_rf("/tmp/#{testproj}")
+  
+  silent_system("cd /tmp ; cucumber-nagios-gen project #{testproj}").should be_true
+end
+

data/features/steps/using_steps.rb

@@ -0,0 +1,31 @@
+Given /^a project called "([^\"]*)" is created and frozen$/ do |project_name|
+  @project_name = project_name
+  Given 'cucumber-nagios is installed'
+  When "I create a new project called \"#{@project_name}\""
+  And 'I freeze in dependencies'
+  Then 'my gems directory should be populated'
+end
+
+When /^I generate a new feature called "([^\"]*)" for "([^\"]*)"$/ do |feature, site|
+  silent_system("cd /tmp/#{@project_name} ; bin/cucumber-nagios-gen feature #{site} #{feature}")
+end
+
+Then /^a feature file should exist for "([^\"]*)" on "([^\"]*)"$/ do |feature, site|
+  File.exists?("/tmp/#{@project_name}/features/#{site}/#{feature}.feature").should be_true
+end
+
+Then /^the "([^\"]*)" feature on "([^\"]*)" should exit cleanly$/ do |feature, site|
+  silent_system("cd /tmp/#{@project_name} ; bin/cucumber-nagios features/#{site}/#{feature}.feature").should be_true
+end
+
+Then /^the "([^\"]*)" feature on "([^\"]*)" should not exit cleanly$/ do |feature, site|
+  silent_system("cd /tmp/#{@project_name} ; bin/cucumber-nagios features/#{site}/#{feature}.feature").should be_false
+end
+
+When /^the "([^\"]*)" feature on "([^\"]*)" checks for something preposterous$/ do |feature, site|
+  file_name = "/tmp/#{@project_name}/features/#{site}/#{feature}.feature"
+  File.open(file_name,'a') do |file|
+    file << "     Then I should see \"supercalifragilisticexpialidocious\""
+  end
+end
+

data/features/support/silent_system.rb

@@ -0,0 +1,4 @@
+def silent_system(cmd)
+  silent_cmd = cmd + " 2>&1 > /dev/null"
+  system(silent_cmd)
+end

data/features/using.feature

@@ -0,0 +1,21 @@
+Feature: Using features
+  To test websites
+  A cucumber feature 
+  Must be created
+
+  Scenario: Create a feature
+    Given cucumber-nagios is installed
+    And a project called "more-great-tests" is created and frozen
+    When I generate a new feature called "login" for "github.com"
+    Then a feature file should exist for "login" on "github.com"
+
+  Scenario: Run a successful feature
+    Given a project called "passing-features" is created and frozen
+    When I generate a new feature called "homepage" for "github.com"
+    Then the "homepage" feature on "github.com" should exit cleanly
+  
+  Scenario: Run a failing feature
+    Given a project called "failing-features" is created and frozen
+    When I generate a new feature called "profile" for "github.com"
+    And the "profile" feature on "github.com" checks for something preposterous
+    Then the "profile" feature on "github.com" should not exit cleanly

data/lib/generators/project/.gitignore

@@ -0,0 +1,9 @@
+.DS_Store
+*~
+.#*
+.bzr
+.bzrignore
+vendor/gems/specifications/*
+vendor/gems/gems/*
+vendor/gems/bin/*
+vendor/gems/environment.rb

data/lib/generators/project/Gemfile

@@ -0,0 +1,9 @@
+# list of dependencies for a cucumber-nagios project
+
+#gem "bundler", "0.6.0"
+gem "cucumber", "0.4.0"
+gem "rspec", "1.2.9"
+gem "webrat", "0.5.3"
+gem "mechanize", "0.9.3"
+gem "templater", "0.5.0"
+

data/lib/generators/project/README

@@ -0,0 +1,166 @@
+
+Bundling dependencies
+=====================
+
+Bundling cucumber-nagios's dependencies allows you to drop your cucumber-nagios 
+project to any machine and have it run. This can be useful if you want to 
+develop your tests on one machine, and deploy them to another (like a production
+Nagios server). 
+
+You'll need to bundle your dependencies to use cucumber-nagios. 
+
+First you need to make sure the following dependencies are installed: 
+
+  - RubyGems
+	- bundler gem (automatically pulled in by the cucumber-nagios gem)
+
+To bundle your dependencies, within your project directory run:
+
+    $ gem bundle 
+
+
+Version control
+===============
+
+It's strongly recommend that you store your cucumber-nagios projects in a 
+version control system!
+
+To get up and running with git: 
+
+    $ git init
+    $ git add .
+    $ git commit -m 'created cucumber-nagios project'
+
+To get up and running with bzr:
+
+    $ bzr init
+    $ bzr add
+    $ bzr commit -m 'created cucumber-nagios project'
+
+.bzrignore and .gitignores are created when you generate a project.
+
+
+Writing features
+================
+
+You can use the bin/cucumber-nagios-gen command to generate new features for
+you. It takes two arguments: the site you're testing, and feature you're testing: 
+
+    bin/cucumber-nagios-gen feature gnome.org navigation
+
+This will generate two files: 
+
+    features/gnome.org/navigation.feature
+    features/gnome.org/steps/navigation_steps.rb
+
+
+As for writing features, you'll want to have a read of the Cucumber 
+documentation[0], however your tests will look something like this:
+
+    Feature: google.com.au
+      To broaden their knowledge
+      A user should be able
+      To search for things
+    
+      Scenario: Searching for things
+        Given I visit "http://www.google.com"
+        When I fill in "q" with "wikipedia"
+        And I press "Google Search"
+        Then I should see "www.wikipedia.org"
+
+
+There's a collection of steps that will cover most of the things you'll be 
+testing for in features/steps/webrat_steps.rb. 
+
+You can write custom steps for testing specific output and behaviour, e.g.
+in features/smh.com.au/smh.feature: 
+
+    Feature: smh.com.au
+      It should be up
+      And provide links to content
+    
+      Scenario: Visiting home page
+        When I go to http://smh.com.au/
+        Then I should see site navigation
+        And there should be a section named "Opinion"
+
+There aren't steps for "Then I should see site navigation", so you have to 
+write one yourself. :-) In features/smh.com.au/steps/smh_steps.rb: 
+
+    Then /^I should see site navigation$/ do                                                                    
+      doc = Nokogiri::HTML(response.body.to_s)                                                                  
+      doc.css("ul#nav li a").size.should > 5                                                                    
+    end
+
+You can use Nokogiri for testing responses with XPath matchers and CSS 
+selectors. 
+
+I suggest you use bin/cucumber directly so you can get better feedback when 
+writing your tests:
+
+    bin/cucumber --require features/ features/smh/smh.feature
+
+This will output using the default 'pretty' formatter. 
+
+Running
+=======
+
+Invoke the Cucumber feature with the cucumber-nagios script: 
+
+    bin/cucumber-nagios features/smh.com.au/smh.feature
+
+cucumber-nagios can be run from anywhere: 
+
+    /path/to/bin/cucumber-nagios /path/to/features/smh/smh.feature
+
+It should return a standard Nagios-formatted response string: 
+
+    Critical: 0, Warning: 0, 2 okay | passed=2, failed=0, total=2
+
+Steps that fail will show up in the "Critical" total, and steps that pass 
+show up in the "okay" total. 
+
+The value printed at the end is in Nagios's Performance Data format, so it
+can be graphed and the like.
+
+
+Quirks & Caveats
+================
+
+Multiple scenarios
+------------------
+
+You may want to think about keeping to one scenario to a file, otherwise 
+you'll get multiple lines of output for a test:
+
+    Critical: 1, Warning: 0, 2 okay | passed=2, failed=1, total=3
+    Critical: 1, Warning: 0, 4 okay | passed=4, failed=1, total=5
+
+That said, Nagios should only read the last line, so this might be an ok 
+behaviour when you want to test for an aggregate of failures across a site.
+
+
+Failure *is* an option (exceptions are good)
+--------------------------------------------
+
+Exceptions raised within your tests will appear in the failed totals, so you 
+don't need to worry about trying to catch them in your own custom steps. 
+
+i.e. if you try fetching a page on a server that is down, or the page returns 
+a 404, the exception raised by Mechanize just gets treated by Cucumber as a 
+test failure. 
+
+
+Deploying to production
+=======================
+
+Once you've copied your project around, just run the bundler again: 
+
+    $ gem bundle
+
+You'll need to have RubyGems and the bundler gem installed on the system 
+you're deploying too. I know, this is not optimal, but hopefully the bundler
+gem will handle this better in the future. 
+
+
+[0] http://wiki.github.com/aslakhellesoy/cucumber

data/lib/generators/project/bin/cucumber-nagios

@@ -0,0 +1,31 @@
+#!/usr/bin/env ruby
+
+unless ARGV[0]
+  puts "Usage: #{__FILE__} <feature>"
+  exit 99
+end
+
+__DIR__ = File.expand_path(File.dirname(__FILE__))
+
+feature = ARGV[0]
+unless File.exists?(feature)
+  feature = File.join(__DIR__, '..', 'features', ARGV[0]) 
+end
+
+unless File.exist?(feature)
+  puts "Error: feature file doesn't exist!"
+  exit 98
+end
+
+command = "#{__DIR__}/cucumber"
+command += " --require features/"
+command += " --format Cucumber::Formatter::Nagios"
+command += " #{feature}"
+
+if ARGV[1] == "--debug"
+  puts command 
+  puts
+end
+
+system(command) ? exit(0) : exit(2)
+

data/lib/generators/project/bin/cucumber-nagios-gen

@@ -0,0 +1,52 @@
+#!/usr/bin/env ruby
+
+# attempt to load up the bundled gems, and give an explanatory message if we can't
+begin
+  require File.join(File.dirname(__FILE__), '..', 'vendor', 'gems', 'environment')
+rescue LoadError
+  puts "You need to bundle gems into your project before you can run this."
+  puts
+  puts "To do this, make sure the 'bundler' gem is installed, and run:"
+  puts
+  puts "  $ gem bundle"
+  puts
+  exit 1
+end
+require 'templater'
+
+module CucumberNagiosGenerators
+
+  extend Templater::Manifold
+
+  # feature generator
+  class FeatureGenerator < Templater::Generator
+    def self.source_root
+      File.join(File.dirname(__FILE__), '..', 'lib', 'generators', 'feature')
+    end
+
+    desc <<-DESC
+      Generate a cucumber feature. Takes a two arguments:
+        bin/cucumber-nagios-gen feature <site-name> <feature-name>
+    DESC
+
+    first_argument :site, :required => true, :desc => "Site name"
+    second_argument :feature, :required => true, :desc => "Feature name"
+
+    template :feature do |template|
+      template.source = "%feature_name%.feature"
+      template.destination = "features/#{site}/#{feature}.feature"
+    end
+
+    template :step do |template|
+      template.source = "%feature_name%_steps.rb"
+      template.destination = "features/#{site}/steps/#{feature}_steps.rb"
+    end
+
+  end
+
+  desc "Generators for a cucumber-nagios project"
+  add :feature, FeatureGenerator
+
+end
+
+CucumberNagiosGenerators.run_cli Dir.pwd, 'cucumber-nagios-gen', '0.5', ARGV

data/lib/generators/project/features/steps/result_steps.rb

@@ -0,0 +1,19 @@
+Then /^I should see "(.*)"$/ do |text|
+  response.body.to_s.should =~ /#{text}/m
+end
+
+Then /^I should not see "(.*)"$/ do |text|
+  response.body.to_s.should_not =~ /#{text}/m
+end
+
+Then /^I should see an? (\w+) message$/ do |message_type|
+  response.should have_xpath("//*[@class='#{message_type}']")
+end
+
+Then /^the (.*) ?request should succeed/ do |_|
+  success_code?.should be_true
+end
+
+Then /^the (.*) ?request should fail/ do |_|
+  success_code?.should be_false
+end

data/lib/generators/project/features/steps/webrat_steps.rb

@@ -0,0 +1,40 @@
+When /^I go to (.*)$/ do |path|
+  visit path
+end
+
+When /^I press "(.*)"$/ do |button|
+  click_button(button)
+end
+
+When /^I follow "(.*)"$/ do |link|
+  click_link(link)
+end
+
+When /^I fill in "(.*)" with "(.*)"$/ do |field, value|
+  fill_in(field, :with => value) 
+end
+
+When /^I select "(.*)" from "(.*)"$/ do |value, field|
+  select(value, :from => field) 
+end
+
+When /^I check "(.*)"$/ do |field|
+  check(field) 
+end
+
+When /^I uncheck "(.*)"$/ do |field|
+  uncheck(field) 
+end
+
+When /^I choose "(.*)"$/ do |field|
+  choose(field)
+end
+
+When /^I submit the form named "(.*)"$/ do |name|
+  submit_form(name)
+end
+
+When /^I attach the file at "(.*)" to "(.*)" $/ do |path, field|
+  attach_file(field, path)
+end
+

data/lib/generators/project/features/support/env.rb

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby 
+
+require 'rubygems'                                                                                      
+require 'webrat'
+require 'webrat/mechanize'
+
+class ResponseHelper
+  def response
+    webrat_session.response
+  end
+end
+
+World do
+  ResponseHelper.new
+  Webrat::Session.new(Webrat::MechanizeAdapter.new)
+end
+
+

data/lib/generators/project/features/support/nagios.rb

@@ -0,0 +1,49 @@
+require 'cucumber/formatter/console'
+
+module Cucumber
+  module Formatter
+    class Nagios
+
+      def initialize(step_mother, io, options={})
+        @failed  = []
+        @passed  = []
+        @warning = []
+        @io = io
+      end
+  
+      def after_step_result(keyword, step_match, multiline_arg, status, exception, source_indent, background)
+        case status
+        when :passed
+          @passed << step_match
+        when :failed
+           @failed << step_match
+        when :undefined
+          @warning << step_match
+        end
+      end
+  
+      def after_features(steps)
+        print_summary
+      end
+  
+      private
+      def print_summary
+        @total = @failed.size + @passed.size + @warning.size
+        message = ""
+        message += "Critical: #{@failed.size}, "
+        message += "Warning: #{@warning.size}, "
+        message += "#{@passed.size} okay"
+        # nagios performance data
+        message += " | passed=#{@passed.size}"
+        message += ", failed=#{@failed.size}"
+        message += ", nosteps=#{@warning.size}"
+        message += ", total=#{@total}\n"
+
+        @io.print(message)
+        @io.flush
+      end
+
+    end
+  end
+end
+

data/lib/generators/project/lib/generators/feature/%feature_name%.feature

@@ -0,0 +1,7 @@
+Feature: <%= site %>
+  It should be up
+
+  Scenario: Visiting home page
+    When I go to http://<%= site %>
+    Then the request should succeed
+

data/lib/generators/project/lib/generators/feature/%feature_name%_steps.rb

@@ -0,0 +1 @@
+# steps go here!

metadata

@@ -0,0 +1,106 @@
+--- !ruby/object:Gem::Specification 
+name: cucumber-nagios
+version: !ruby/object:Gem::Version 
+  version: 0.5.0
+platform: ruby
+authors: 
+- Lindsay Holmwood
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2009-10-12 00:00:00 +02:00
+default_executable: 
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: templater
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0.5"
+    version: 
+- !ruby/object:Gem::Dependency 
+  name: rake
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 0.8.3
+    version: 
+- !ruby/object:Gem::Dependency 
+  name: bundler
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 0.6.0
+    version: 
+description: cucumber-nagios lets you write high-level behavioural tests for your web applications that can be plugged into Nagios
+email: lindsay@holmwood.id.au
+executables: 
+- cucumber-nagios-gen
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- bin/cucumber-nagios-gen
+- lib/generators/project/Gemfile
+- lib/generators/project/features/steps/result_steps.rb
+- lib/generators/project/features/steps/webrat_steps.rb
+- lib/generators/project/features/support/env.rb
+- lib/generators/project/features/support/nagios.rb
+- lib/generators/project/bin/cucumber-nagios
+- lib/generators/project/bin/cucumber-nagios-gen
+- lib/generators/project/.bzrignore
+- lib/generators/project/.gitignore
+- lib/generators/project/README
+- LICENSE
+- README.md
+- Rakefile
+- lib/generators/project/lib/generators/feature/%feature_name%.feature
+- lib/generators/project/lib/generators/feature/%feature_name%_steps.rb
+- features/support/silent_system.rb
+- features/using.feature
+- features/steps/installing_steps.rb
+- features/steps/using_steps.rb
+- features/steps/creating_steps.rb
+- features/creating.feature
+- features/installing.feature
+has_rdoc: true
+homepage: http://auxesis.github.com/cucumber-nagios/
+licenses: []
+
+post_install_message: 
+rdoc_options: []
+
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: cucumber-nagios
+rubygems_version: 1.3.5
+signing_key: 
+specification_version: 3
+summary: web app testing plugin for Nagios using Cucumber/Webrat/Mechanize
+test_files: []
+