librarian-puppet 0.9.2 → 0.9.3

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/Rakefile

@@ -0,0 +1,25 @@
+# encoding: utf-8
+require 'rubygems'
+require 'bundler'
+Bundler.setup
+Bundler::GemHelper.install_tasks
+
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new do |t|
+  opts = defined?(JRUBY_VERSION) ? %w{--tags ~@jruby} : []
+  opts += %w{--tags ~@fails-on-travis} if ENV['TRAVIS']
+  t.cucumber_opts = opts 
+end
+
+require 'rspec/core/rake_task'
+desc "Run RSpec"
+RSpec::Core::RakeTask.new do |spec|
+  spec.pattern = 'spec/**/*_spec.rb'
+  spec.rspec_opts = ['--color', '--format nested']
+end
+
+desc "Run tests, both RSpec and Cucumber"
+task :test => [:spec, :cucumber]
+
+task :default => :test

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/aruba.gemspec

@@ -0,0 +1,27 @@
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name        = 'aruba'
+  s.version     = '0.4.11'
+  s.authors     = ["Aslak Hellesøy", "David Chelimsky", "Mike Sassak", "Matt Wynne"]
+  s.description = 'CLI Steps for Cucumber, hand-crafted for you in Aruba'
+  s.summary     = "aruba-#{s.version}"
+  s.email       = 'cukes@googlegroups.com'
+  s.homepage    = 'http://github.com/cucumber/aruba'
+
+  s.add_runtime_dependency 'cucumber', '>= 1.1.1'
+  s.add_runtime_dependency 'childprocess', '>= 0.2.3'
+  s.add_runtime_dependency 'ffi', '>= 1.0.11'
+  s.add_runtime_dependency 'rspec', '>= 2.7.0'
+  s.add_development_dependency 'bcat', '>= 0.6.1'
+  s.add_development_dependency 'rdiscount', '>= 1.6.8'
+  s.add_development_dependency 'rake', '>= 0.9.2'
+
+  s.rubygems_version = ">= 1.6.1"
+  s.files            = `git ls-files`.split("\n")
+  s.test_files       = `git ls-files -- {spec,features}/*`.split("\n")
+  s.executables      = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.rdoc_options     = ["--charset=UTF-8"]
+  s.require_path     = "lib"
+end
+

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/cucumber.yml

@@ -0,0 +1,2 @@
+default: --tags ~@wip
+wip: --wip --tags @wip

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/before_cmd_hooks.feature

@@ -0,0 +1,61 @@
+Feature: before_cmd hooks
+
+  You can configure Aruba to run blocks of code before it runs
+  each command.
+  
+  The command will be passed to the block.
+  
+  Scenario: Run a simple command with a before hook
+    Given a file named "test.rb" with:
+      """
+      $: << '../../lib'
+      require 'aruba/api'
+      
+      Aruba.configure do |config|
+        config.before_cmd do |cmd|
+          puts "about to run `#{cmd}`"
+        end
+      end
+      
+      include Aruba::Api
+      run_simple("echo 'running'")
+      puts all_stdout
+      """
+    When I run `ruby test.rb`
+    Then it should pass with:
+      """
+      about to run `echo 'running'`
+      running
+      """
+  
+  # This should move into a spec
+  Scenario: Use something from the context where the command was run
+    Given a file named "test.rb" with:
+      """
+      $: << '../../lib'
+      require 'aruba/api'
+
+      Aruba.configure do |config|
+        config.before_cmd do |cmd|
+          puts "I can see @your_context=#{@your_context}"
+        end
+      end
+
+      class Test
+        include Aruba::Api
+        
+        def test
+          @your_context = "something"
+          run_simple("echo 'running'")
+          puts all_stdout
+        end
+      end
+      
+      Test.new.test
+      """
+    When I run `ruby test.rb`
+    Then it should pass with:
+      """
+      I can see @your_context=something
+      running
+      """

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/exit_statuses.feature

@@ -0,0 +1,42 @@
+Feature: exit statuses
+
+  In order to specify expected exit statuses
+  As a developer using Cucumber
+  I want to use the "the exit status should be" step
+
+  Scenario: exit status of 0
+    When I run `ruby -h`
+    Then the exit status should be 0
+
+  Scenario: exit status of 0 with `
+    When I run `ruby -h`
+    Then the exit status should be 0
+
+  Scenario: Not explicitly exiting at all
+    When I run `ruby -e '42'`
+    Then the exit status should be 0
+    
+  Scenario: non-zero exit status
+    When I run `ruby -e 'exit 56'`
+    Then the exit status should be 56
+    And the exit status should not be 0
+
+  Scenario: Successfully run something
+    When I successfully run `ruby -e 'exit 0'`
+
+  Scenario: Successfully run something with `
+    When I successfully run `ruby -e 'exit 0'`
+
+  Scenario: Unsuccessfully run something
+    When I do aruba I successfully run `ruby -e 'exit 10'`
+    Then aruba should fail with "Exit status was 10"
+
+  @posix
+  Scenario: Try to run something that doesn't exist
+    When I run `does_not_exist`
+    Then the exit status should be 1
+
+  @posix
+  Scenario: Try to run something that doesn't exist with `
+    When I run `does_not_exist`
+    Then the exit status should be 1

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/file_system_commands.feature

@@ -0,0 +1,157 @@
+Feature: file system commands
+
+  In order to specify commands that load files
+  As a developer using Cucumber
+  I want to create temporary files
+  
+  Scenario: create a dir
+    Given a directory named "foo/bar"
+    When I run `ruby -e "puts test ?d, 'foo'"`
+    Then the stdout should contain "true"
+  
+  Scenario: create a file
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I run `ruby foo/bar/example.rb`
+    Then the output should contain "hello world"
+
+  Scenario: create a fixed sized file
+    Given a 1048576 byte file named "test.txt"
+    Then a 1048576 byte file named "test.txt" should exist
+
+  Scenario: Append to a file
+    \### We like appending to files:
+    1. Disk space is cheap
+    1. It's completely safe
+
+    \### Here is a list:
+    - One
+    - Two
+
+    Given a file named "foo/bar/example.feature" with:
+      """
+      Feature: Example
+        Hello World
+      """
+    And a file named "foo/bar/example.rb" with:
+      """
+      puts "\e[31mhello world\e[0m"
+
+      """
+    When I append to "foo/bar/example.rb" with:
+      """
+      puts "this was appended"
+
+      """
+    When I run `ruby foo/bar/example.rb`
+    Then the stdout should contain "hello world"
+    And the stdout should contain "this was appended"
+
+  Scenario: Append to a new file
+    When I append to "thedir/thefile" with "x"
+    And I append to "thedir/thefile" with "y"
+    Then the file "thedir/thefile" should contain "xy"
+
+  Scenario: clean up files generated in previous scenario
+    When I run `ruby foo/bar/example.rb`
+    Then the exit status should be 1
+    And the output should contain "No such file or directory -- foo/bar/example.rb"
+  
+  Scenario: change to a subdir
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I cd to "foo/bar"
+    And I run `ruby example.rb`
+    Then the output should contain "hello world"
+
+  Scenario: Reset current directory from previous scenario
+    When I run `ruby example.rb`
+    Then the exit status should be 1
+
+  Scenario: Holler if cd to bad dir
+    Given a file named "foo/bar/example.rb" with:
+      """
+      puts "hello world"
+      """
+    When I do aruba I cd to "foo/nonexistant"
+    Then aruba should fail with "tmp/aruba/foo/nonexistant is not a directory"
+
+  Scenario: Check for presence of a subset of files
+    Given an empty file named "lorem/ipsum/dolor"
+    Given an empty file named "lorem/ipsum/sit"
+    Given an empty file named "lorem/ipsum/amet"
+    Then the following files should exist:
+      | lorem/ipsum/dolor |
+      | lorem/ipsum/amet  |
+
+  Scenario: Check for absence of files
+    Then the following files should not exist:
+      | lorem/ipsum/dolor |
+
+  Scenario: Check for presence of a single file
+    Given an empty file named "lorem/ipsum/dolor"
+    Then a file named "lorem/ipsum/dolor" should exist
+
+  Scenario: Check for absence of a single file
+    Then a file named "lorem/ipsum/dolor" should not exist
+
+  Scenario: Check for presence of a subset of directories
+    Given a directory named "foo/bar"
+    Given a directory named "foo/bla"
+    Then the following directories should exist:
+      | foo/bar |
+      | foo/bla |
+
+  Scenario: check for absence of directories
+    Given a directory named "foo/bar"
+    Given a directory named "foo/bla"
+    Then the following step should fail with Spec::Expectations::ExpectationNotMetError:
+    """
+    Then the following directories should not exist:
+      | foo/bar/ |
+      | foo/bla/ |
+    """
+
+  Scenario: Check for presence of a single directory
+    Given a directory named "foo/bar"
+    Then a directory named "foo/bar" should exist
+
+  Scenario: Check for absence of a single directory
+    Given a directory named "foo/bar"
+    Then the following step should fail with Spec::Expectations::ExpectationNotMetError:
+      """
+      Then a directory named "foo/bar" should not exist
+      """
+
+  Scenario: Check file contents
+    Given a file named "foo" with:
+      """
+      hello world
+      """
+    Then the file "foo" should contain "hello world"
+    And the file "foo" should not contain "HELLO WORLD"
+
+  Scenario: Check file contents with regexp
+    Given a file named "foo" with:
+      """
+      hello world
+      """
+    Then the file "foo" should match /hel.o world/
+    And the file "foo" should not match /HELLO WORLD/
+
+  Scenario: Remove file
+    Given a file named "foo" with:
+      """
+      hello world
+      """
+    When I remove the file "foo"
+    Then the file "foo" should not exist
+
+  Scenario: Just a dummy for reporting
+    Given an empty file named "a/b.txt"
+    Given an empty file named "a/b/c.txt"
+    Given an empty file named "a/b/c/d.txt"

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/flushing.feature

@@ -0,0 +1,24 @@
+Feature: Flushing output
+
+  In order to test processes that output a lot of data
+  As a developer using Aruba
+  I want to make sure that large amounts of output aren't buffered
+
+  Scenario: A little output
+    When I run `ruby -e 'puts :a.to_s * 256'`
+    Then the output should contain "a"
+    And the output should be 256 bytes long
+    And the exit status should be 0
+
+  Scenario: Tons of output
+    When I run `ruby -e 'puts :a.to_s * 65536'`
+    Then the output should contain "a"
+    And the output should be 65536 bytes long
+    And the exit status should be 0
+
+  Scenario: Tons of interactive output
+    When I run `ruby -e 'len = gets.chomp; puts :a.to_s * len.to_i'` interactively
+    And I type "65536"
+    Then the output should contain "a"
+    And the output should be 65536 bytes long
+    # And the exit status should be 0

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/interactive.feature

@@ -0,0 +1,40 @@
+Feature: Interactive process control
+
+  In order to test interactive command line applications
+  As a developer using Cucumber
+  I want to use the interactive session steps
+
+  Scenario: Running ruby interactively
+    Given a file named "echo.rb" with:
+      """
+      while res = gets.chomp
+        break if res == "quit"
+        puts res.reverse
+      end
+      """
+    When I run `ruby echo.rb` interactively
+    And I type "hello, world"
+    And I type "quit"
+    Then it should pass with:
+      """
+      dlrow ,olleh
+      """
+
+  @posix @fails-on-travis
+  Scenario: Running a native binary interactively
+    When I run `bc -q` interactively
+    And I type "4 + 3"
+    And I type "quit"
+    Then the output should contain:
+      """
+      7
+      """
+
+  @posix
+  Scenario: Stop processes before checking for filesystem changes 
+    See: http://github.com/aslakhellesoy/aruba/issues#issue/17 for context
+
+    Given a directory named "rename_me"
+    When I run `mv rename_me renamed` interactively
+    Then a directory named "renamed" should exist
+    And a directory named "rename_me" should not exist

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/no_clobber.feature

@@ -0,0 +1,25 @@
+Feature: No clobber
+
+  By default Aruba removes its scratch directory before
+  every scenario. This isn't always the right thing
+  to do, especially when the path to the default directory
+  has been changed. Use @no-clobber to stop Aruba from
+  cleaning up after itself.
+
+  Scenario: Change the filesystem
+    Given a directory named "foo/bar"
+    And a file named "foo/bar/baz.txt" with:
+      """
+      I don't want to die!
+      """
+
+  @no-clobber
+  Scenario: Verify nothing was clobbered
+    Then a file named "foo/bar/baz.txt" should exist
+    And the file "foo/bar/baz.txt" should contain exactly:
+      """
+      I don't want to die!
+      """
+
+  Scenario: Cleanup and verify the previous scenario
+    Then a file named "foo/bar/baz.txt" should not exist

data/vendor/gems/ruby/1.8/gems/aruba-0.4.11/features/output.feature

@@ -0,0 +1,248 @@
+Feature: Output
+
+  In order to specify expected output
+  As a developer using Cucumber
+  I want to use the "the output should contain" step
+
+  @posix
+  Scenario: Run unknown command
+    When I run `neverever gonna work`
+    Then the output should contain:
+      """
+      No such file or directory - neverever
+      """
+
+  @posix
+  Scenario: Detect subset of one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should contain "hello world"
+
+  @posix
+  Scenario: Detect subset of one-line output
+    When I run `echo 'hello world'`
+    Then the output should contain "hello world"
+
+  Scenario: Detect absence of one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should not contain "good-bye"
+
+  Scenario: Detect subset of multiline output
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the output should contain:
+      """
+      hello
+      """
+
+  Scenario: Detect subset of multiline output
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the output should not contain:
+      """
+      good-bye
+      """
+
+  @posix
+  Scenario: Detect exact one-line output
+    When I run `ruby -e 'puts \"hello world\"'`
+    Then the output should contain exactly:
+      """
+      hello world
+      
+      """
+
+  @ansi
+  @posix
+  Scenario: Detect exact one-line output with ANSI output
+    When I run `ruby -e 'puts \"\e[36mhello world\e[0m\"'`
+    Then the output should contain exactly:
+      """
+      \e[36mhello world\e[0m
+
+      """
+
+  @posix
+  Scenario: Detect exact one-line output with ANSI output stripped by default
+    When I run `ruby -e 'puts \"\e[36mhello world\e[0m\"'`
+    Then the output should contain exactly:
+      """
+      hello world
+
+      """
+  @posix
+  Scenario: Detect exact multiline output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then the output should contain exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce
+  Scenario: Detect subset of one-line output with regex
+    When I run `ruby --version`
+    Then the output should contain "ruby"
+    And the output should match /ruby ([\d]+\.[\d]+\.[\d]+)(\w*\d*)? \(.*$/
+
+  @announce
+  @posix
+  Scenario: Detect subset of multiline output with regex
+    When I run `ruby -e 'puts "hello\nworld\nextra line1\nextra line2\nimportant line"'`
+    Then the output should match:
+      """
+      he..o
+      wor.d
+      .*
+      important line
+      """
+
+  @announce
+  @posix
+  Scenario: Match passing exit status and partial output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then it should pass with:
+      """
+      hello
+      """
+
+  @posix
+  Scenario: Match passing exit status and exact output
+    When I run `ruby -e 'puts "hello\nworld"'`
+    Then it should pass with exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce-stdout
+  Scenario: Match failing exit status and partial output
+    When I run `ruby -e 'puts \"hello\\nworld\";exit 99'`
+    Then it should fail with:
+      """
+      hello
+      """
+
+  @posix
+  Scenario: Match failing exit status and exact output
+    When I run `ruby -e 'puts "hello\nworld";exit 99'`
+    Then it should fail with exactly:
+      """
+      hello
+      world
+
+      """
+
+  @announce-stdout
+  @posix
+  Scenario: Match failing exit status and output with regex
+    When I run `ruby -e 'puts \"hello\\nworld\";exit 99'`
+    Then it should fail with regex:
+      """
+      hello\s*world
+      """
+
+  @announce-cmd
+  @posix
+  Scenario: Match output in stdout
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the stdout should contain "hello"
+    Then the stderr should not contain "hello"
+
+  @announce
+  Scenario: Match output on several lines
+    When I run `ruby -e 'puts %{GET /}'`
+    Then the stdout should contain:
+      """
+      GET /
+      """
+
+  @posix
+  Scenario: Match output on several lines using quotes
+    When I run `ruby -e 'puts %{GET "/"}'`
+    Then the stdout should contain:
+      """
+      GET "/"
+      """
+
+  @posix
+  Scenario: Match output in stdout
+    When I run `ruby -e 'puts \"hello\\nworld\"'`
+    Then the stdout should contain "hello"
+    Then the stderr should not contain "hello"
+
+
+  @posix
+  Scenario: Detect output from all processes
+    When I run `ruby -e 'puts \"hello world!\"'`
+    And I run `ruby -e 'puts gets.chomp.reverse'` interactively
+    And I type "hello"
+    Then the output should contain exactly:
+      """
+      hello world!
+      olleh
+
+      """
+
+  @posix
+  Scenario: Detect stdout from all processes
+    When I run `ruby -e 'puts \"hello world!\"'`
+    And I run `ruby -e 'puts gets.chomp.reverse'` interactively
+    And I type "hello"
+    Then the stdout should contain:
+      """
+      hello world!
+      olleh
+      """
+    And the stderr should not contain:
+      """
+      hello world!
+      olleh
+      """
+
+  @posix
+  Scenario: Detect stderr from all processes
+    When I run `ruby -e 'STDERR.puts \"hello world!\"'`
+    And I run `ruby -e 'STDERR.puts gets.chomp.reverse'` interactively
+    And I type "hello"
+    Then the stderr should contain:
+      """
+      hello world!
+      olleh
+      """
+    And the stdout should not contain:
+      """
+      hello world!
+      olleh
+      """
+
+  Scenario: Detect output from named source
+    When I run `ruby -e 'puts :simple'`
+    And I run `ruby -e 'puts gets.chomp'` interactively
+    And I type "interactive"
+    Then the output from "ruby -e 'puts :simple'" should contain "simple"
+    And the output from "ruby -e 'puts gets.chomp'" should not contain "simple"
+
+  Scenario: Detect stdout from named source
+    When I run `ruby -e 'puts :hello'`
+    And I run `ruby -e 'puts :goodbye'`
+    Then the stdout from "ruby -e 'puts :hello'" should contain "hello"
+    And the stderr from "ruby -e 'puts :hello'" should not contain "hello"
+    And the stdout from "ruby -e 'puts :goodbye'" should not contain "hello"
+
+  Scenario: Detect stderr from named source
+    When I run `ruby -e 'STDERR.puts :hello'`
+    And I run `ruby -e 'puts :goodbye'`
+    Then the stderr from "ruby -e 'STDERR.puts :hello'" should contain "hello"
+    And the stdout from "ruby -e 'STDERR.puts :hello'" should not contain "hello"
+    And the stderr from "ruby -e 'puts :goodbye'" should not contain "hello"
+
+  @wip
+  Scenario: Detect output from named source with custom name
+
+  Scenario: Detect second output from named source with custom name
+    When I set env variable "ARUBA_TEST_VAR" to "first"
+    And I run `ruby -e 'puts ENV[%q(ARUBA_TEST_VAR)]'`
+    Then the output from "ruby -e 'puts ENV[%q(ARUBA_TEST_VAR)]'" should contain "first"
+    When I set env variable "ARUBA_TEST_VAR" to "second"
+    And I run `ruby -e 'puts ENV[%q(ARUBA_TEST_VAR)]'`
+    Then the output from "ruby -e 'puts ENV[%q(ARUBA_TEST_VAR)]'" should contain "second"