cuken 0.1.1 → 0.1.2

data/examples/chef/features/support/env.rb

@@ -0,0 +1,16 @@
+require 'bundler'
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
+
+$LOAD_PATH.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'cuken/ssh'
+require 'cuken/cmd'
+require 'cuken/file'
+require 'cuken/chef'
+
+require 'rspec/expectations'

data/features/chef/cookbooks/cookbook.feature

@@ -0,0 +1,14 @@
+@announce @work_in_cwd @cookbooks @cookbook_validity
+Feature: Cookbook Validity
+  In order to understand cookbooks without evaluating them
+  As an Administrator
+  I want to automatically confirm cookbook existence and validity
+
+  Background:
+    Given a default base chef repository in "ckbk/scratch/myapp"
+
+  Scenario: Clone a cookbook repository
+      And the remote cookbook repository "features/data/repositories/cookbooks/hosts/.git"
+     When I clone the remote cookbook repository branch "master" to "tmp/aruba/ckbk/scratch/myapp/cookbooks/hosts"
+     Then the local cookbook repository exists
+      And the local cookbook "hosts" exists

data/features/chef/cookbooks/metadata.feature

@@ -0,0 +1,40 @@
+@announce @work_in_cwd @cookbooks @cookbook_metadata
+Feature: Cookbook Metadata
+  In order to understand cookbooks without evaluating them
+  As an Administrator
+  I want to automatically generate metadata about cookbooks
+
+  Background:
+    Given a default base chef repository in "ckbk/scratch/myapp"
+      And the local chef repository exists
+      And a file named "ckbk/scratch/myapp/.chef/knife.rb" with:
+      """
+      current_dir = File.dirname(__FILE__)
+      log_level :debug
+      log_location $stdout
+      node_name "bobo"
+      client_key "#{File.dirname(current_dir)}/bobo.pem"
+      chef_server_url "http://localhost:4000"
+      cache_type 'Memory'
+      cache_options( :path => "#{ENV['HOME']}/.chef/checksums" )
+      cookbook_path ["#{current_dir}/../cookbooks","#{current_dir}/../site-cookbooks"]
+
+      """
+      And the remote cookbook repository "features/data/repositories/cookbooks/hosts/.git"
+      And I clone the remote cookbook repository branch "master" to "ckbk/scratch/myapp/cookbooks/hosts"
+      And the local cookbook repository exists
+
+  Scenario: Generate metadata for all cookbooks
+     When I successfully generate all cookbook metadata
+      And the output should contain "DEBUG: Generated "
+      And the output should not contain "DEBUG: No "
+    Then the file "ckbk/scratch/myapp/cookbooks/hosts/metadata.json" exists
+
+  Scenario: Generate metadata for a specific cookbook
+     When we record the a-mtime of "ckbk/scratch/myapp/cookbooks/hosts/metadata.json"
+      And I successfully generate cookbook "hosts" metadata
+      And the output should contain "DEBUG: Generated "
+      And the output should not contain "DEBUG: No "
+    Then the file "ckbk/scratch/myapp/cookbooks/hosts/metadata.json" exists
+      And the mtime of "ckbk/scratch/myapp/cookbooks/hosts/metadata.json" changes
+

data/features/chef/cookbooks/repo.feature

@@ -0,0 +1,13 @@
+@announce @work_in_cwd @cookbooks @chef_repo
+Feature: Base Chef repository for cookbooks
+  In order to have a Chef skeleton to build a custom deployment
+  As an Administrator
+  I want to automatically clone a generic base Chef repository
+
+  Background:
+    Given a directory named "ckbk/scratch"
+
+  Scenario: Clone a Chef skeleton repository
+      And the remote chef repository "features/data/repositories/chef-repo/.git"
+     When I clone the remote chef repository branch "master" to "tmp/aruba/ckbk/scratch/myapp"
+     Then the local chef repository exists

data/features/chef/knife.feature

@@ -0,0 +1,140 @@
+#
+# NOTE: This is an example of Cuken usage. Assuming:
+# - A Chef server on localhost:4000 (point to yours)
+# - An admin client named bobo exists on that Chef server
+#
+# If you wish to mock a Chef server, see the Chef project's
+# features setup.
+#
+@announce @knife @steps
+Feature: Reusable Chef Knife steps
+  In order to write Chef features describing post-convergence system integration
+  As a Chef user
+  I want to describe features without having to implement Knife steps
+
+  Background:
+    Given the Chef server URI "http://localhost:4000"
+    And the Chef admin client "bobo"
+    Given a directory named "foo/bar"
+    And a file named "foo/bar/bobo.pem" with:
+    """
+    -----BEGIN RSA PRIVATE KEY-----
+    MIIEowIBAAKCAQEAumj8KuxHMNsIF00uMw2ZYfUj45vQD1OqhgjF2xAAlILMVeMP
+    xt+Xqq5bm2LS2zDbwK0lAWDAJTr/PHRPt9+4rMlYZt9bZWcLy/AeHHc3XePzaPIZ
+    Pctv7ja9Juom55PQRqmqviyw//9Usbnwx/9BAgPaq9lk3Cx0Ce+gRJLHkzXA0/bY
+    m68XTTtSkfdruruy0Y8qDSHEX++08xA0MYTp6EY+BiyECPntv8itp/DoRL+cDgAt
+    zuG0/Gn6EUMH2GGZ2K1bbA0l8xR8Jl+pE+w8teRWnJeuF1VxK6k0jnR8D7TzGJHc
+    xmg0O/UJf7f6CYVA7schABkZfu/LUcGXSImK9wIDAQABAoIBADSdYV+0JTvy9sus
+    6zdZxUtS5/hciFNrKByA6We1kpRYfthXKKLXhXWVlSG8uQtJNR2jQWisKE/Z4STt
+    J3sc2IFcq2kN7jwm47uCYN1kAOqtZozemKVKgKNaK/WJ7cU7gXQQe7MF5ke7h+pK
+    M14f+/dXoycSS1eh7HbJfhEc5Nv1ufpm+0anK+Ek1qKWVFSC5wrtMbnHb3TuIkE4
+    W7cUHWFtnf1p6ZGDROooAOpbPLO7pmbO1idt6lR12/DUP5vgd4WzyRitGt0ra3X9
+    htf12jMAaXVqAe1xKGFLi6p08CMTnv/7p/G+sK/HliBN4dpKMmhmFyDG1kEaXCIp
+    abUd5oECgYEA9WHNfEs24CMfvNxw5Rrz176BwbFHolnjY9XpqoCB5jN+RhXzM2IR
+    8r9jFwTGe7GucLB0DBOWh+8xNyPNtDleYggBWX36f85UFvpkvPwTAjvZHsgdHC4c
+    EjnWyzgz+GL2glKXnJed/eBejVFHnHvVOkWz15X1CZmDEQAeQmU/5tcCgYEAwnnt
+    DaECIYPxWaeBuYqP0AhyuvA/wHqb0HjsrS7spM1mvcyFDtcOMuSKFO4eEJW4Jybk
+    fxaMnJdrL7kPWjT5e8OP0dFsMiNyXD1gWl8/+CysaYsVFNa4QJo/ZZKVSTCGgDk4
+    8aOVyHB0KjLeDcf6aqe9aAr7amDrHoIqPT4wmOECgYA+x1HqLdgRSgsxp3hetSGT
+    ndLWukNofvTVMwJAM/aH7b6tsanyCHItF9gDKJ6bQN8vR4W5HT3S81g1Ejzrkg3a
+    qM+nlLqE/kW3R0KEsz0twiAPZwVDk2xtIU0Z2vw43SDSQM03K/co38FxCE149Jmd
+    +f1D98KkPRkyPUSAmiTaKwKBgHiH7L3nrlRrXCg+ww3lrOA4fDMUN87prqx0Zeuo
+    C47Qpv63RTg/XVN5hYMXWZbZ1DqfxjpmFVvwFMSNI9C6yG1GdVqLO02P3o8Akzkv
+    k4wS1ADN7JDvy15uuyAOy2uDIblSvdI1mt2RpM2KnUlZSgDUWXWkaNIzo0VTUy6F
+    3sTBAoGBAMCgw1dKF48GiKL5HYcwpbQrRneDX/l6w3sqNV8/UrzqJOm+elu/BT8y
+    g1sug7qgWqOJYytk2hgGeiB/IGZNsR9Tw+270xLaQlUoqtraDoh6liAdjA3f4BWu
+    9SJ/Of+9/IQ4lNXG36TAVUHnJ7hu5SGQkL3XUgNeotv1gCcZTvWW
+    -----END RSA PRIVATE KEY-----
+    """
+    And a file named "foo/bar/.chef/knife.rb" with:
+    """
+    current_dir = File.dirname(__FILE__)
+    log_level :debug
+    log_location $stdout
+    node_name "bobo"
+    client_key "#{File.dirname(current_dir)}/bobo.pem"
+    chef_server_url "http://localhost:4000"
+    cache_type 'Memory'
+    cache_options( :path => "#{ENV['HOME']}/.chef/checksums" )
+    cookbook_path ["#{current_dir}/../cookbooks","#{current_dir}/../site-cookbooks"]
+
+    """
+
+  Scenario: Knife steps default knife.rb path
+     Given I cd to "foo/bar"
+      When I successfully run `knife node list`
+      When the output should contain:
+     """
+     DEBUG: Using configuration from /usr/src/cuken/tmp/aruba/foo/bar/.chef/knife.rb
+     DEBUG: Signing the request as bobo
+     DEBUG: Sending HTTP Request via GET to localhost:4000/nodes
+     [
+     """
+
+  Scenario: Knife steps with path to knife.rb created earlier
+     Given the Knife file "foo/bar/.chef/knife.rb"
+      When I successfully run Knife's "node list"
+      When the output should contain:
+     """
+     DEBUG: Using configuration from /usr/src/cuken/tmp/aruba/foo/bar/.chef/knife.rb
+     DEBUG: Signing the request as bobo
+     DEBUG: Sending HTTP Request via GET to localhost:4000/nodes
+     [
+     """
+
+  Scenario: Upload a cookbook with path to knife.rb created earlier
+    Given the Knife file "foo/bar/.chef/knife.rb"
+      And I cd to "./../../"
+      And a cookbook path "features/data/cookbooks_not_uploaded_at_feature_start"
+     When I successfully run Knife's "cookbook upload version_updated"
+     Then the output should contain:
+    """
+    DEBUG: Signing the request as bobo
+    DEBUG: Sending HTTP Request via PUT to localhost:4000/cookbooks/version_updated/2.0.0
+    INFO: Upload complete!
+
+    """
+
+  Scenario: Verify a cookbook with path to knife.rb created earlier
+    Given the Knife file "foo/bar/.chef/knife.rb"
+    And I successfully run Knife's "cookbook show version_updated"
+    And the output should contain:
+    """
+    DEBUG: Signing the request as bobo
+    DEBUG: Sending HTTP Request via GET to localhost:4000/cookbooks/version_updated
+    {
+      "version_updated": [
+        "2.0.0"
+      ]
+    }
+
+    """
+
+  Scenario: Delete a cookbook with path to knife.rb created earlier
+    Given the Knife file "foo/bar/.chef/knife.rb"
+     When I interactively run Knife's "cookbook delete version_updated"
+      And I type "Y"
+      And wait "5" seconds
+     Then the output should contain:
+      """
+      DEBUG: Signing the request as bobo
+      DEBUG: Sending HTTP Request via GET to localhost:4000/cookbooks/version_updated
+      Do you really want to delete version_updated version 2.0.0? (Y/N) DEBUG: Signing the request as bobo
+      DEBUG: Sending HTTP Request via DELETE to localhost:4000/cookbooks/version_updated/2.0.0
+      Deleted cookbook[version_updated version 2.0.0]!
+      """
+
+  Scenario: Auto upload and Delete a cookbook with path to knife.rb created earlier
+    Given the Knife file "foo/bar/.chef/knife.rb"
+      And I cd to "./../../"
+      And a cookbook path "features/data/cookbooks_not_uploaded_at_feature_start"
+     When I successfully run Knife's "cookbook upload version_updated"
+     When I successfully run Knife's "cookbook delete version_updated 2.0.0"
+     Then the output should contain:
+      """
+      DEBUG: Signing the request as bobo
+      DEBUG: Sending HTTP Request via GET to localhost:4000/cookbooks/version_updated
+      Do you really want to delete version_updated version 2.0.0? (Y/N) DEBUG: Signing the request as bobo
+      DEBUG: Sending HTTP Request via DELETE to localhost:4000/cookbooks/version_updated/2.0.0
+      Deleted cookbook[version_updated version 2.0.0]!
+      """

data/features/chef/knife_steps.feature

@@ -0,0 +1,19 @@
+@knife @cookbook_upload @knife_cookbook_upload
+Feature: Upload Cookbooks with Knife
+  In order to use cookbooks I have written
+  As a knife user
+  I want to upload my cookbooks
+
+  Scenario: Uploading a new cookbook updates the metadata on the server
+    Given I am an administrator
+     When I upload the 'version' cookbook with knife
+     When I 'GET' to the path '/cookbooks/version_updated'
+     Then the inflated response should equal '{"version_updated"=>{"url"=>"http://127.0.0.1:4000/cookbooks/version_updated", "versions"=>[{"url"=>"http://127.0.0.1:4000/cookbooks/version_updated/2.0.0", "version"=>"2.0.0"}]}}'
+
+  @regression
+  Scenario: Uploading a new version updates the metadata on the server
+    Given I am an administrator
+     When I upload the 'version_updated' cookbook with knife
+     When I 'GET' to the path '/cookbooks/version_updated'
+     Then the inflated response should equal '{"version_updated"=>{"url"=>"http://127.0.0.1:4000/cookbooks/version_updated", "versions"=>[{"url"=>"http://127.0.0.1:4000/cookbooks/version_updated/2.0.0", "version"=>"2.0.0"}]}}'
+

data/features/command_steps.feature

@@ -0,0 +1,68 @@
+@step_features
+Feature: Listing file steps
+  In order to test a running system
+  As an administrator
+  I want to know what command steps are available
+
+  Background:
+    Given that "cuken/cmd" has been required
+
+  Scenario: Command execution
+    Then these steps are defined for "cuken/cucumber/cmd.rb":
+      | step                                                   |
+      |I run `([^`]*)`                                         |
+      |I run `([^`]*)` interactively                           |
+      |I successfully run `([^`]*)`                            |
+      |I type "([^"]*)"                                        |
+
+  Scenario: Command exit status
+    Then these steps are defined for "cuken/cucumber/cmd.rb":
+      | step                                                   |
+      |the exit status should be (\d+)                         |
+      |the exit status should not be (\d+)                     |
+#    Pending:
+#    https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/707-element-size-differs-2-should-be-1-indexerror
+#      |it should (pass|fail) with:                             |
+#      |it should (pass|fail) with exactly:                     |
+#      |it should (pass|fail) with regexp?:                     |
+
+  Scenario: Command output (stdout+stderr)
+    Then these steps are defined for "cuken/cucumber/cmd.rb":
+      | step                                                   |
+      |the output from "(.*)" contains exactly:                |
+      |the output from "([^"]*)" does not contain exactly:     |
+      |the output from "([^"]*)" contains:                     |
+      |the output from "([^"]*)" does not contain:             |
+      |the output from "([^"]*)" should contain "([^"]*)"      |
+      |the output from "([^"]*)" should not contain "([^"]*)"  |
+      |the output should contain "([^"]*)"                     |
+      |the output should contain:                              |
+      |the output should contain exactly "([^"]*)"             |
+      |the output should contain exactly:                      |
+      |the output should match \/([^\/]*)\/                    |
+      |the output should match:                                |
+      |the output should not contain "([^"]*)"                 |
+      |the output should not contain:                          |
+
+  Scenario: Command stderr
+    Then these steps are defined for "cuken/cucumber/cmd.rb":
+      | step                                                   |
+      |the stderr from "([^"]*)" should contain "([^"]*)"      |
+      |the stderr from "([^"]*)" should not contain "([^"]*)"  |
+      |the stderr should contain "([^"]*)"                     |
+      |the stderr should contain:                              |
+      |the stderr should contain exactly:                      |
+      |the stderr should not contain "([^"]*)"                 |
+      |the stderr should not contain:                          |
+
+  Scenario: Command stdout
+    Then these steps are defined for "cuken/cucumber/cmd.rb":
+      | step                                                   |
+      |the stdout from "([^"]*)" should contain "([^"]*)"      |
+      |the stdout from "([^"]*)" should not contain "([^"]*)"  |
+      |the stdout should contain "([^"]*)"                     |
+      |the stdout should contain:                              |
+      |the stdout should contain exactly:                      |
+      |the stdout should not contain "([^"]*)"                 |
+      |the stdout should not contain:                          |
+

data/features/commands.feature

@@ -10,15 +10,15 @@ Feature: Executing commands
     Given that "cuken/cmd" has been required
 
   Scenario: Check Stdout
-    When I run "echo 'i like cheese'"
+    When I run `echo 'i like cheese'`
     Then the stdout from "echo 'i like cheese'" should contain "i like cheese"
 
   Scenario: Check Stderr
-    When I run "some_error"
+    When I run `some_error`
     Then the stderr from "some_error" should contain "No such file or directory - some_error"
 
   Scenario: Check Stdout for multiple lines
-    When I run "echo 'one\none\none\n'"
+    When I run `echo 'one\none\none\n'`
     Then the output should contain:
     """
     one
@@ -27,10 +27,10 @@ Feature: Executing commands
     """
 
   Scenario: Check exit code
-    When I run "true"
+    When I run `true`
     Then the exit status should be 0
 
   Scenario: Check exit code
-    When I run "false"
+    When I run `false`
     Then the exit status should be 1
 

data/features/common_steps.feature

@@ -0,0 +1,13 @@
+@step_features
+Feature: Listing common steps
+  In order to test a running system
+  As an administrator
+  I want to know what common steps are available
+
+  Background:
+    Given that "cuken/common" has been required
+
+  Scenario: Common execution
+    Then these steps are defined for "cuken/cucumber/common.rb":
+      | step                                                   |
+      |wait "([^"]*)" seconds                                  |

data/features/data/Rakefile

@@ -0,0 +1,38 @@
+#
+# Rakefile for Chef Server Repository
+#
+# Author:: Adam Jacob (<adam@opscode.com>)
+# Copyright:: Copyright (c) 2008 Opscode, Inc.
+# License:: Apache License, Version 2.0
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#     http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+$: << File.join(File.dirname(__FILE__), "..", "..", "chef", "lib")
+
+require 'rubygems'
+require 'chef'
+require 'chef/json_compat'
+
+# Make sure you have loaded constants first
+require File.join(File.dirname(__FILE__), 'config', 'rake')
+
+# And choosen a VCS
+if File.directory?(File.join(TOPDIR, ".svn"))
+  $vcs = :svn
+elsif File.directory?(File.join(TOPDIR, ".git"))
+  $vcs = :git
+end
+
+load 'chef/tasks/chef_repo.rake'
+

data/features/data/apt/chef-integration-test-1.0/debian/changelog

@@ -0,0 +1,5 @@
+chef-integration-test (1.0-1) unstable; urgency=low
+
+  * Initial release (Closes: #CHEF-1718)
+
+ -- Joshua Timberman <joshua@opscode.com>  Thu, 30 Sep 2010 09:53:45 -0600

data/features/data/apt/chef-integration-test-1.0/debian/compat

@@ -0,0 +1 @@
+7

data/features/data/apt/chef-integration-test-1.0/debian/control

@@ -0,0 +1,13 @@
+Source: chef-integration-test
+Section: ruby
+Priority: extra
+Maintainer: Joshua Timberman <Joshua Timberman <joshua@opscode.com>>
+Build-Depends: debhelper (>= 7.0.50~)
+Standards-Version: 3.8.4
+Homepage: http://tickets.opscode.com
+
+Package: chef-integration-test
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: Chef integration tests for APT in Cucumber
+ This package is used for cucumber integration testing in Chef.

data/features/data/apt/chef-integration-test-1.0/debian/copyright

@@ -0,0 +1,34 @@
+This work was packaged by:
+
+    Joshua Timberman <Joshua Timberman <joshua@opscode.com>> on Thu, 30 Sep 2010 09:53:45 -0600
+
+Upstream Author(s):
+
+    Opscode, Inc.
+
+Copyright:
+
+    Copyright (C) 2010 Opscode, Inc
+
+License:
+
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+
+The Debian packaging is:
+
+    Copyright (C) 2010 Opscode, Inc (<legal@opscode.com>)
+
+
+and is licensed under the Apache 2.0 license.
+
+See "/usr/share/common-licenses/Apache-2.0"