right_develop 1.1.0

data/.rspec

@@ -0,0 +1,4 @@
+--colour
+--format=nested
+--backtrace
+--debugger

data/CHANGELOG.rdoc

@@ -0,0 +1,3 @@
+== 1.0
+
+Initial release calved from RightSupport.

data/Gemfile

@@ -0,0 +1,26 @@
+source "http://rubygems.org"
+
+# Runtime dependencies of RightDevelop
+gem "rake", [">= 0.8.7", "< 0.10"]
+gem "right_support", "~> 2.0"
+gem "builder", "~> 3.0"
+gem "rspec", [">= 1.3", "< 3.0"]
+gem "cucumber", "~> 1.0"
+
+# Gems used during RightDevelop development that should be called out in the gemspec
+group :development do
+  gem "jeweler", "~> 1.8.3"
+  gem "rdoc", ">= 2.4.2"
+  gem "syntax", "~> 1.0.0" #rspec will syntax-highlight code snippets if this gem is available
+  gem "nokogiri", "~> 1.5"
+  gem "flexmock", "~> 0.8.7", :require => nil
+  gem "activesupport"
+  gem "libxml-ruby", "~> 2.4.0"
+end
+
+# Gems that are only used locally by this repo to run tests and should NOT be called out in the gemspec
+group :test do
+  gemspec
+  gem "ruby-debug", ">= 0.10", :platforms => :ruby_18
+  gem "ruby-debug19", ">= 0.11.6", :platforms => :ruby_19
+end

data/Gemfile.lock

@@ -0,0 +1,92 @@
+PATH
+  remote: .
+  specs:
+    right_develop (1.1.0)
+      builder (~> 3.0)
+      cucumber (~> 1.0)
+      rake (>= 0.8.7, < 0.10)
+      right_support (~> 2.0)
+      rspec (>= 1.3, < 3.0)
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    activesupport (3.2.11)
+      i18n (~> 0.6)
+      multi_json (~> 1.0)
+    archive-tar-minitar (0.5.2)
+    builder (3.1.4)
+    columnize (0.3.6)
+    cucumber (1.2.1)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.11.0)
+      json (>= 1.4.6)
+    diff-lcs (1.1.3)
+    flexmock (0.8.11)
+    gherkin (2.11.6)
+      json (>= 1.7.6)
+    git (1.2.5)
+    i18n (0.6.1)
+    jeweler (1.8.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+      rdoc
+    json (1.7.6)
+    libxml-ruby (2.4.0)
+    linecache (0.46)
+      rbx-require-relative (> 0.0.4)
+    linecache19 (0.5.12)
+      ruby_core_source (>= 0.1.4)
+    multi_json (1.5.0)
+    nokogiri (1.5.6)
+    rake (0.9.6)
+    rbx-require-relative (0.0.9)
+    rdoc (3.12.1)
+      json (~> 1.4)
+    right_support (2.6.17)
+    rspec (2.12.0)
+      rspec-core (~> 2.12.0)
+      rspec-expectations (~> 2.12.0)
+      rspec-mocks (~> 2.12.0)
+    rspec-core (2.12.2)
+    rspec-expectations (2.12.1)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.12.2)
+    ruby-debug (0.10.4)
+      columnize (>= 0.1)
+      ruby-debug-base (~> 0.10.4.0)
+    ruby-debug-base (0.10.4)
+      linecache (>= 0.3)
+    ruby-debug-base19 (0.11.25)
+      columnize (>= 0.3.1)
+      linecache19 (>= 0.5.11)
+      ruby_core_source (>= 0.1.4)
+    ruby-debug19 (0.11.6)
+      columnize (>= 0.3.1)
+      linecache19 (>= 0.5.11)
+      ruby-debug-base19 (>= 0.11.19)
+    ruby_core_source (0.1.5)
+      archive-tar-minitar (>= 0.5.2)
+    syntax (1.0.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activesupport
+  builder (~> 3.0)
+  cucumber (~> 1.0)
+  flexmock (~> 0.8.7)
+  jeweler (~> 1.8.3)
+  libxml-ruby (~> 2.4.0)
+  nokogiri (~> 1.5)
+  rake (>= 0.8.7, < 0.10)
+  rdoc (>= 2.4.2)
+  right_develop!
+  right_support (~> 2.0)
+  rspec (>= 1.3, < 3.0)
+  ruby-debug (>= 0.10)
+  ruby-debug19 (>= 0.11.6)
+  syntax (~> 1.0.0)

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2013- RightScale, Inc.
+
+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.rdoc

@@ -0,0 +1,50 @@
+RightDevelop is a library of reusable, unit- and functional-tested Ruby code that RightScale has found broadly useful.
+
+== What Does It Do?
+
+=== Continuous Integration
+
+Jenkins groks JUnit XML test results very well, and has lots of hidden features associated with them. Tests are tests,
+so we've written an RSpec formatter that Jenkins will feel right at home with!
+
+To use our CI harness, just add the following to your Rakefile (or into lib/tasks/ci.rake):
+
+  require 'right_develop'
+  RightDevelop::CI::RakeTask.new
+
+==== Customizing your CI Harness
+
+You can override various aspects of the CI harness' behavior by passing a block to the constructor which
+tweaks various instance variables of the resulting Rake task:
+
+  RightDevelop::CI::RakeTask.new do |task|
+    task.ci_namespace = :my_happy_ci
+    task.rspec_pattern = "spec/important/**/*_spec.rb" # only run the important specs for CI
+    task.output_path   = "ci_results"                  # use ci_results as the base dir for all output files
+    task.rspec_output  = "happy_specs.xml"             # write to ci_results/rspec/happy_specs.xml
+  end
+
+==== Keeping the CI Harness Out of Production
+
+We recommend that you don't install RightDevelop -- or other test-only gems such as rspec -- when you deploy
+your code to production. This improves the startup time and performance of your app, and prevents instability
+due to potential bugs in test code.
+
+To prevent RightDevelop from shipping to production, simply put it in the "development" group of your Gemfile:
+
+  group :development do
+    gem 'right_develop'
+  end
+
+And ensure that you deploy your code using Bundler's --without flag:
+
+  bundle install --deployment --without development
+
+And finally, modify your Rakefile so you can tolerate the absence of the RightDevelop rake classes. For this,
+you can use RightSupport's Kernel#require_succeeds? extension to conditionally instantiate the Rake tasks:
+
+  require 'right_support'
+
+  if require_succeeds?('right_develop')
+    RightDevelop::CI::RakeTask.new
+  end

data/Rakefile

@@ -0,0 +1,67 @@
+# -*-ruby-*-
+require 'rubygems'
+require 'bundler/setup'
+
+require 'rake'
+require 'rdoc/task'
+require 'rubygems/package_task'
+
+require 'rake/clean'
+require 'rspec/core/rake_task'
+require 'cucumber/rake/task'
+
+# We use RightDevelop's CI harness in its own Rakefile. Hooray dogfood!
+require 'right_develop'
+
+# But, we have a very special need, because OUR Cucumbers need to run with a pristine
+# environment that isn't polluted by RVM or RubyGems or anyone else, in order to validate
+# that RightDevelop's CI harness doesn't break your app if those gems are unavailable.
+# Thus when our own Rake task runs spec or cucumber as a subprocess, we need to give it
+# a pristine non-bundled environment, so it can use Bundler.with_clean_env to launch
+# subprocesses.
+require File.expand_path('../features/support/file_utils_bundler_mixin', __FILE__)
+
+desc "Run unit tests"
+task :default => :spec
+
+desc "Run unit tests"
+RSpec::Core::RakeTask.new do |t|
+  t.pattern = Dir['**/*_spec.rb']
+end
+
+desc "Run functional tests"
+Cucumber::Rake::Task.new do |t|
+  t.cucumber_opts = %w{--color --format pretty}
+end
+
+desc 'Generate documentation for the right_develop gem.'
+Rake::RDocTask.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'doc'
+  rdoc.title    = 'RightDevelop'
+  rdoc.options << '--line-numbers' << '--inline-source'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+  rdoc.rdoc_files.exclude('features/**/*')
+  rdoc.rdoc_files.exclude('spec/**/*')
+end
+
+require 'jeweler'
+Jeweler::Tasks.new do |gem|
+  # gem is a Gem::Specification; see http://docs.rubygems.org/read/chapter/20 for more options
+  gem.name = "right_develop"
+  gem.homepage = "https://github.com/rightscale/right_develop"
+  gem.license = "MIT"
+  gem.summary = %Q{Reusable dev & test code.}
+  gem.description = %Q{A toolkit of development tools created by RightScale.}
+  gem.email = "support@rightscale.com"
+  gem.authors = ["Tony Spataro"]
+  gem.rubygems_version = "1.3.7"
+end
+
+# This is a closed-source gem; omit gemcutter tasks so people don't accidentally
+# push this gem to the public!
+#Jeweler::RubygemsDotOrgTasks.new
+
+CLEAN.include('pkg')
+
+RightDevelop::CI::RakeTask.new

data/VERSION

@@ -0,0 +1 @@
+1.1.0

data/features/cucumber.feature

@@ -0,0 +1,27 @@
+Feature: Cucumber 1.x support
+  In order to facilitate TDD and enhance code quality
+  RightDevelop should provide CI tasks with Cucumber with JUnit XML output
+  So any Ruby project can have a beautiful, info-rich Jenkins project
+
+  Background:
+    Given a Ruby application
+    And a Gemfile
+    And a gem dependency on 'rake ~> 0.9'
+    And a gem dependency on 'cucumber ~> 1.0'
+    And the Rakefile contains a RightDevelop::CI::RakeTask
+
+  Scenario: passing Cucumber features
+    Given a trivial Cucumber feature
+    When I install the bundle
+    And I rake 'ci:cucumber'
+    Then the command should succeed
+    And the output should contain '** Execute ci:cucumber'
+    And the directory 'measurement/cucumber' should contain files
+
+  Scenario: failing Cucumber features
+    Given a trivial failing Cucumber feature
+    When I install the bundle
+    And I rake 'ci:cucumber'
+    Then the command should fail
+    And the output should contain '** Execute ci:cucumber'
+    And the directory 'measurement/cucumber' should contain files

data/features/rake_integration.feature

@@ -0,0 +1,27 @@
+Feature: basic Rake integration
+  In order to promote predictable, reliable Continuous Integration
+  RightDevelop should expose a "ci:" Rake namespace
+
+  Background:
+    Given a Ruby application
+    And a Gemfile
+    And a gem dependency on 'rake ~> 0.9'
+
+  Scenario: list Rake tasks
+    Given the Rakefile contains a RightDevelop::CI::RakeTask
+    When I install the bundle
+    And I rake '-T'
+    And the output should contain 'ci:cucumber'
+    And the output should contain 'ci:spec'
+
+  Scenario: override namespace
+    Given the Rakefile contains:
+    """
+    RightDevelop::CI::RakeTask.new do |task|
+      task.ci_namespace = :funkalicious
+    end
+    """
+    When I install the bundle
+    And I rake '-T'
+    Then the output should contain 'funkalicious:cucumber'
+    Then the output should contain 'funkalicious:spec'

data/features/rspec1.feature

@@ -0,0 +1,67 @@
+Feature: RSpec 1.x support
+  In order to facilitate TDD and enhance code quality
+  RightDevelop should provide a Rake CI harness with JUnit XML output
+  So any Ruby project can have a beautiful, info-rich Jenkins project
+
+  Background:
+    Given a Ruby application
+    And a Gemfile
+    And a gem dependency on 'rake ~> 0.9'
+    And a gem dependency on 'rspec ~> 1.0'
+    And the Rakefile contains a RightDevelop::CI::RakeTask
+
+  Scenario: passing examples
+    Given a trivial RSpec spec
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+    And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
+    And the file 'measurement/rspec/rspec.xml' should mention 0 failing test cases
+
+  Scenario: failing examples
+    Given a trivial failing RSpec spec
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should fail
+    And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
+    And the file 'measurement/rspec/rspec.xml' should mention 1 failing test case
+
+  Scenario: override input file pattern
+    Given an RSpec spec named 'passing_spec.rb' with content:
+    """
+    describe String do
+      it 'is cool' do
+        'cool'.should == 'cool'
+      end
+    end
+    """
+    And an RSpec spec named 'failing_spec.rb' with content:
+    """
+    describe String do
+      it 'is uncool' do
+        'cool'.should == 'uncool'
+      end
+    end
+    """
+    And the Rakefile contains:
+    """
+    RightDevelop::CI::RakeTask.new do |task|
+      task.rspec_pattern = 'spec/passing_spec.rb'
+    end
+    """
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+
+  Scenario: override output file location
+    Given a trivial RSpec spec
+    And the Rakefile contains:
+    """
+    RightDevelop::CI::RakeTask.new do |task|
+      task.rspec_output = 'awesome.xml'
+    end
+    """
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+    And the file 'measurement/rspec/awesome.xml' should exist

data/features/rspec2.feature

@@ -0,0 +1,67 @@
+Feature: RSpec 2.x support
+  In order to facilitate TDD and enhance code quality
+  RightDevelop should provide a Rake CI harness with JUnit XML output
+  So any Ruby project can have a beautiful, info-rich Jenkins project
+
+  Background:
+    Given a Ruby application
+    And a Gemfile
+    And a gem dependency on 'rake ~> 0.9'
+    And a gem dependency on 'rspec ~> 2.0'
+    And the Rakefile contains a RightDevelop::CI::RakeTask
+
+  Scenario: passing examples
+    And a trivial RSpec spec
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+    And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
+    And the file 'measurement/rspec/rspec.xml' should mention 0 failing test cases
+
+  Scenario: failing examples
+    And a trivial failing RSpec spec
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should fail
+    And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
+    And the file 'measurement/rspec/rspec.xml' should mention 1 failing test case
+
+  Scenario: override input file pattern
+    Given an RSpec spec named 'passing_spec.rb' with content:
+    """
+    describe String do
+      it 'is cool' do
+        'cool'.should == 'cool'
+      end
+    end
+    """
+    And an RSpec spec named 'failing_spec.rb' with content:
+    """
+    describe String do
+      it 'is uncool' do
+        'cool'.should == 'uncool'
+      end
+    end
+    """
+    And the Rakefile contains:
+    """
+    RightDevelop::CI::RakeTask.new do |task|
+      task.rspec_pattern = 'spec/passing_spec.rb'
+    end
+    """
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+
+  Scenario: override output file location
+    Given a trivial RSpec spec
+    And the Rakefile contains:
+    """
+    RightDevelop::CI::RakeTask.new do |task|
+      task.rspec_output = 'awesome.xml'
+    end
+    """
+    When I install the bundle
+    And I rake 'ci:spec'
+    Then the command should succeed
+    And the file 'measurement/rspec/awesome.xml' should exist