mutiny 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 5b0cd4975a5e102b5494dea373d982f29a4360b1
+  data.tar.gz: 84b81be52e16ec0438d308f8b41638a664c7d939
+SHA512:
+  metadata.gz: b63df8d72301fbce3ac705294ef4821fc51f076681518b2ba7b4b0936de19a30e5a09c3890464780e6b175c9ad4b9771c4dd74f4afc9a2967a1edcf0a1dff3c3
+  data.tar.gz: 65204290c1816ab66893e05469c9425b4fc8b7d10658dc90c32b0d079e04f3f416339ced292fc18eb855910fdbabb75147cc3c9ff9c1c81502917cd232fcd0d7

data/.gitignore

@@ -0,0 +1,6 @@
+/.bundle
+.DS_Store
+coverage
+.tmp
+.mutants
+pkg

data/.rspec

@@ -0,0 +1,3 @@
+--color
+--format progress
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,18 @@
+AllCops:
+  Include:
+    - Gemfile
+    - Rakefile
+  Exclude:
+    - vendor/*
+
+StringLiterals:
+  Enabled: false
+
+LineLength:
+  Max: 99
+
+Documentation:
+  Enabled: false
+
+Style/TrivialAccessors:
+  ExactNameMatch: true

data/.ruby-version

@@ -0,0 +1 @@
+2.2.2

data/.travis.yml

@@ -0,0 +1,6 @@
+language: ruby
+rvm:
+  - 2.2.2
+addons:
+  code_climate:
+    repo_token: 0297c93e8cb012ae60aa0760b795608f96c681e1493d98153d5cd7bd97e3b650

data/Gemfile

@@ -0,0 +1,5 @@
+ruby "2.2.2"
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in mutiny.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,113 @@
+PATH
+  remote: .
+  specs:
+    mutiny (0.1.0)
+      gli (~> 2.13.0)
+      metamorpher (~> 0.2.2)
+      parser (~> 2.2.2)
+      unparser (~> 0.2.4)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    abstract_type (0.0.7)
+    adamantium (0.2.0)
+      ice_nine (~> 0.11.0)
+      memoizable (~> 0.4.0)
+    aruba (0.6.2)
+      childprocess (>= 0.3.6)
+      cucumber (>= 1.1.1)
+      rspec-expectations (>= 2.7.0)
+    ast (2.0.0)
+    astrolabe (1.3.0)
+      parser (>= 2.2.0.pre.3, < 3.0)
+    attributable (0.1.0)
+    builder (3.2.2)
+    childprocess (0.5.6)
+      ffi (~> 1.0, >= 1.0.11)
+    codeclimate-test-reporter (0.4.7)
+      simplecov (>= 0.7.1, < 1.0.0)
+    concord (0.1.5)
+      adamantium (~> 0.2.0)
+      equalizer (~> 0.0.9)
+    cucumber (2.0.0)
+      builder (>= 2.1.2)
+      cucumber-core (~> 1.1.3)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.12)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.1.2)
+    cucumber-core (1.1.3)
+      gherkin (~> 2.12.0)
+    diff-lcs (1.2.5)
+    docile (1.1.5)
+    equalizer (0.0.11)
+    ffi (1.9.8)
+    gherkin (2.12.2)
+      multi_json (~> 1.3)
+    gli (2.13.1)
+    ice_nine (0.11.1)
+    json (1.8.2)
+    memoizable (0.4.2)
+      thread_safe (~> 0.3, >= 0.3.1)
+    metamorpher (0.2.2)
+      attributable (~> 0.1.0)
+      parser (~> 2.2.2)
+      unparser (~> 0.2.4)
+    multi_json (1.11.0)
+    multi_test (0.1.2)
+    parser (2.2.2.5)
+      ast (>= 1.1, < 3.0)
+    powerpack (0.1.1)
+    procto (0.0.2)
+    rainbow (2.0.0)
+    rake (10.4.2)
+    rspec (3.2.0)
+      rspec-core (~> 3.2.0)
+      rspec-expectations (~> 3.2.0)
+      rspec-mocks (~> 3.2.0)
+    rspec-core (3.2.3)
+      rspec-support (~> 3.2.0)
+    rspec-expectations (3.2.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.2.0)
+    rspec-mocks (3.2.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.2.0)
+    rspec-support (3.2.2)
+    rubocop (0.31.0)
+      astrolabe (~> 1.3)
+      parser (>= 2.2.2.1, < 3.0)
+      powerpack (~> 0.1)
+      rainbow (>= 1.99.1, < 3.0)
+      ruby-progressbar (~> 1.4)
+    ruby-progressbar (1.7.5)
+    simplecov (0.10.0)
+      docile (~> 1.1.0)
+      json (~> 1.8)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.0)
+    thread_safe (0.3.5)
+    unparser (0.2.4)
+      abstract_type (~> 0.0.7)
+      adamantium (~> 0.2.0)
+      concord (~> 0.1.5)
+      diff-lcs (~> 1.2.5)
+      equalizer (~> 0.0.9)
+      parser (~> 2.2.2)
+      procto (~> 0.0.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba (~> 0.6.0)
+  bundler (~> 1.10.2)
+  codeclimate-test-reporter (~> 0.4.6)
+  mutiny!
+  rake (~> 10.4.2)
+  rspec (~> 3.2.0)
+  rubocop (~> 0.31.0)
+
+BUNDLED WITH
+   1.10.2

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2015 Louis Rose
+
+MIT License
+
+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,16 @@
+# Mutiny [![Build Status](https://travis-ci.org/mutiny/mutiny.svg?branch=master)](https://travis-ci.org/mutiny/mutiny) [![Code Climate](https://codeclimate.com/github/mutiny/mutiny/badges/gpa.svg)](https://codeclimate.com/github/mutiny/mutiny) [![Dependency Status](https://gemnasium.com/mutiny/mutiny.svg)](https://gemnasium.com/mutiny/mutiny) [![Test Coverage](https://codeclimate.com/github/mutiny/mutiny/badges/coverage.svg)](https://codeclimate.com/github/mutiny/mutiny)
+
+A tiny mutation testing framework for Ruby. Used for exploring research ideas. For more stable and complete mutation testing in Ruby, use [mutant](https://github.com/mbj/mutant).
+
+Currently supports Ruby versions of these [method level mutation operators](http://cs.gmu.edu/~offutt/mujava/mutopsMethod.pdf).
+
+#### Usage
+* `git clone` this repo
+* `bundle install`
+* `./bin/mutiny ./examples/max.rb ./examples/max_tests.rb` Note that we currently assume that tests.rb is a line-separated set of predicates (expressions that evaluate to either true or false).
+
+## Acknowledgments
+
+Thank-you to the authors of other projects and resources that have inspired mutiny, including:
+
+* Markus Schirp's [mutant](https://github.com/mbj/mutant), which paved the way for modern mutation testing in Ruby. In particular, mutiny's RSpec integration is based on the Markus's stellar work on mutant.

data/RELEASES.md

@@ -0,0 +1,8 @@
+# Release History
+
+## v0.1.0 (5 June 2015)
+Provide support for:
+* Running mutation testing commands via the `mutiny` binary
+* Checking that a program is amenable to mutation testing
+* Generating mutants using traditional method-level operators
+* Integration with RSpec 3

data/Rakefile

@@ -0,0 +1,23 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+task default: ["test:unit", "test:integration", "style:check"]
+
+namespace :test do
+  RSpec::Core::RakeTask.new(:unit) do |task|
+    task.pattern = "./spec/unit{,/*/**}/*_spec.rb"
+  end
+
+  RSpec::Core::RakeTask.new(:integration) do |task|
+    task.pattern = "./spec/integration{,/*/**}/*_spec.rb"
+  end
+end
+
+namespace :style do
+  require "rubocop/rake_task"
+
+  desc "Run RuboCop on the lib directory"
+  RuboCop::RakeTask.new(:check) do |task|
+    task.options = ["--auto-correct"]
+  end
+end

data/TODO.md

@@ -0,0 +1,55 @@
+### TODO
+
+### New implementation
+
+* Reorganise lib, having in mind a "mutiny-core" which is separate to specific integrations (RSpec, etc), specific mutators (Metamorpher-based, etc), specific reporters (command-line, HTML, etc), etc
+
+#### Analysis mode
+* Should calculate mutation score
+  * Need to figure out approach for running tests on a mutant
+
+### Original implementation
+
+* Experimentation to validate approach
+  * Write scripting
+      * Incremental: Should generate mutant delta (new / deleted mutants) between two git commits. Creating new mutants should be possible from existing change detector. Deleting obsoleted mutants will likely require enhancements to the change detector.
+      * Experimental harness: should run non-incremental mode for each commit, and compare to results of incremental mode. Store data for paper and print a summary that shows the number of mutants evaluated by incremental and non-incremental mode.
+
+  * Candidate projects
+      * Thor: https://github.com/erikhuda/thor
+      * Rake (ruled out as it uses minitest rather than RSpec)
+      * Rack (ruled out as it uses Bacon rather than RSpec)
+      * ActiveSupport and other Rails subgems (ruled out as it uses minitest rather than RSpec)
+
+  * Experiments
+      * Compare incremental and non-incremental mutator (seeding of faults) to determine typical magnitude of change over a project. What kind of granularity do we need to make a significant difference (file < method < ast nodes)?
+      * Compare incremental and non-incremental analyser to determine typical impact of change on mutation testing. Analyser will first need to be enhanced with an incremental model that determines which of a set of existing mutants need to be reevaluated.
+
+  * Overall aim: investigate the time savings of using incremental mode over the course of the project's history
+      * Measurements
+          * Could compare time taken for mutation testing each commit.
+          * Alternatively, could compare the number of mutants that need to be re-evaluated. This would allow experimentation to proceed without actually executing any tests; just creating mutants and marking those which need to be re-evaluated. The incremental mode should count any new mutants, mark any mutants from the previous round that need to be re-evaluated, (and mark any mutants from the previous round that need to be deleted?).
+      * Validity of results:
+          * Whatever is measured, I need to compare the _results_ of incremental and non-incremental modes to ensure that incremental mode is correct.
+          * Might need to enhance the change detector to be able to identify dependencies of units. For example, if `max_spec` tests `max` and `max` uses `calculator`, `max_spec` is dependent on calculator. If `calculator` changes, `max_spec` should be detected as impacted.
+
+* Try new approach to specifying mutation operators, particularly if this makes incremental mutation testing easier.
+    * Add a Rewrite class to Ast module which can build and apply rewritings based on syntax in comments
+    * Add notions of MutationOperator that are specified with single rewrite, and with several rewrites.
+
+* More fine-grained change detection. Some ideas:
+  * When an example is removed from a spec, we should be able to quickly recompute the mutation score. To allow this, we would need to store the results of each example for each mutant. We then remove the results for the deleted example, and recalculate the mutation score without running any tests.
+
+  * When a change to a unit is equivalent to swapping the unit for a previously analysed mutant of that unit, we should be able to quickly recompute the mutation score. We simply swap the mutant and unit in the results, and recalculate whether mutants are alive or dead (the new unit might cause different mutants to die). Again, to allow this we would need to store the results of each example for each mutant.
+
+  * When a change to a unit is localised to a single line / method / subset of the file (i.e., a fragment), we only need to recalculate the mutants for that fragment. (However, I suspect we will often need to re-test the mutants and source file to obtain an accurate mutation score: i.e., unlike the points above, this speed up only impacts mutant creation and not mutant analysis) To allow this, the mutation creation component should be able to locate mutation sites in a specific fragment of a file.
+
+* Housekeeping
+
+  * Consider refactoring mutant.rb so that it does not contain a code attribute (perhaps instead it should compute code by passing the file and line number to its operator?)
+
+  * Should the change detector be a separate component, or should it be part of the core?
+
+  * Tests for Session.
+
+* Extend framework to explore Program Analyser and more sophisticated Test Case Provider components (see OmniGraffle diagram)

data/bin/mutiny

@@ -0,0 +1,35 @@
+#!/usr/bin/env ruby
+require "gli"
+require "mutiny"
+
+include GLI::App
+
+program_desc "A tiny mutation testing framework"
+
+flag [:l, :loads], type: Array, default_value: ['lib']
+flag [:r, :requires], type: Array, default_value: [File.basename(Dir.pwd)]
+flag [:p, :patterns], type: Array, default_value: ['*']
+
+pre do |global_options|
+  relevant_options = global_options.select { |k| %i(loads requires patterns).include?(k) }
+  @configuration = Mutiny::Configuration.new(relevant_options)
+end
+
+desc 'Check whether your project can be used with Mutiny'
+long_desc 'Checks that Mutiny can load the modules and classes you specify,
+and execute test cases for each module and class'
+command :check do |c|
+  c.action do
+    Mutiny::Mode::Check.new(@configuration).run
+  end
+end
+
+desc 'Generate a set of mutants for your project'
+long_desc 'Generates a set of mutants for your project and writes them to the .mutant directory'
+command :mutate do |c|
+  c.action do
+    Mutiny::Mode::Mutate.new(@configuration).run
+  end
+end
+
+exit run(ARGV)

data/examples/buggy_calculator/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/examples/buggy_calculator/lib/calculator/max.rb

@@ -0,0 +1,9 @@
+module Calculator
+  class Max
+    def run(left, right)
+      max = left
+      max = right if right < left
+      max
+    end
+  end
+end

data/examples/buggy_calculator/lib/calculator.rb

@@ -0,0 +1,4 @@
+require_relative "calculator/max"
+
+module Calculator
+end

data/examples/buggy_calculator/spec/calculator/max_spec.rb

@@ -0,0 +1,17 @@
+require "calculator/max"
+
+module Calculator
+  describe Max do
+    it "returns correct answer for a tie" do
+      expect(subject.run(4, 4)).to eq(4)
+    end
+
+    it "returns correct answer when first is larger" do
+      expect(subject.run(4, 3)).to eq(4)
+    end
+
+    it "returns correct answer when last is larger" do
+      expect(subject.run(3, 4)).to eq(4)
+    end
+  end
+end

data/examples/buggy_calculator/spec/spec_helper.rb

@@ -0,0 +1,89 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # The settings below are suggested to provide a good initial experience
+  # with RSpec, but feel free to customize to your heart's content.
+  #   # These two settings work together to allow you to limit a spec run
+  #   # to individual examples or groups you care about by tagging them with
+  #   # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  #   # get run.
+  #   config.filter_run :focus
+  #   config.run_all_when_everything_filtered = true
+  #
+  #   # Limits the available syntax to the non-monkey patched syntax that is
+  #   # recommended. For more details, see:
+  #   #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
+  #   #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
+  #   config.disable_monkey_patching!
+  #
+  #   # This setting enables warnings. It's recommended, but in some cases may
+  #   # be too noisy due to issues in dependencies.
+  #   config.warnings = true
+  #
+  #   # Many RSpec users commonly either run the entire suite or an individual
+  #   # file, and it's useful to allow more verbose output when running an
+  #   # individual spec file.
+  #   if config.files_to_run.one?
+  #     # Use the documentation formatter for detailed output,
+  #     # unless a formatter has already been configured
+  #     # (e.g. via a command-line flag).
+  #     config.default_formatter = 'doc'
+  #   end
+  #
+  #   # Print the 10 slowest examples and example groups at the
+  #   # end of the spec run, to help surface which specs are running
+  #   # particularly slow.
+  #   config.profile_examples = 10
+  #
+  #   # Run specs in random order to surface order dependencies. If you find an
+  #   # order dependency and want to debug it, you can fix the order by providing
+  #   # the seed, which is printed after each run.
+  #   #     --seed 1234
+  #   config.order = :random
+  #
+  #   # Seed global randomization in this process using the `--seed` CLI option.
+  #   # Setting this allows you to use `--seed` to deterministically reproduce
+  #   # test failures related to randomization by passing the same `--seed` value
+  #   # as the one that triggered the failure.
+  #   Kernel.srand config.seed
+end

data/examples/calculator/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/examples/calculator/lib/calculator/max.rb

@@ -0,0 +1,9 @@
+module Calculator
+  class Max
+    def run(left, right)
+      max = left
+      max = right if right > left
+      max
+    end
+  end
+end

data/examples/calculator/lib/calculator/min.rb

@@ -0,0 +1,9 @@
+module Calculator
+  class Min
+    def run(left, right)
+      max = left
+      max = right if right < left
+      max
+    end
+  end
+end

data/examples/calculator/lib/calculator.rb

@@ -0,0 +1,5 @@
+require_relative "calculator/max"
+require_relative "calculator/min"
+
+module Calculator
+end

data/examples/calculator/spec/calculator/max_spec.rb

@@ -0,0 +1,17 @@
+require "calculator/max"
+
+module Calculator
+  describe Max do
+    it "returns correct answer for a tie" do
+      expect(subject.run(4, 4)).to eq(4)
+    end
+
+    it "returns correct answer when first is larger" do
+      expect(subject.run(4, 3)).to eq(4)
+    end
+
+    it "returns correct answer when last is larger" do
+      expect(subject.run(3, 4)).to eq(4)
+    end
+  end
+end

data/examples/calculator/spec/calculator/min_spec.rb

@@ -0,0 +1,17 @@
+require "calculator/min"
+
+module Calculator
+  describe Min do
+    it "returns correct answer for a tie" do
+      expect(subject.run(4, 4)).to eq(4)
+    end
+
+    it "returns correct answer when first is smaller" do
+      expect(subject.run(3, 4)).to eq(3)
+    end
+
+    it "returns correct answer when last is smaller" do
+      expect(subject.run(4, 3)).to eq(3)
+    end
+  end
+end

data/examples/calculator/spec/spec_helper.rb

@@ -0,0 +1,89 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # The settings below are suggested to provide a good initial experience
+  # with RSpec, but feel free to customize to your heart's content.
+  #   # These two settings work together to allow you to limit a spec run
+  #   # to individual examples or groups you care about by tagging them with
+  #   # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  #   # get run.
+  #   config.filter_run :focus
+  #   config.run_all_when_everything_filtered = true
+  #
+  #   # Limits the available syntax to the non-monkey patched syntax that is
+  #   # recommended. For more details, see:
+  #   #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
+  #   #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
+  #   config.disable_monkey_patching!
+  #
+  #   # This setting enables warnings. It's recommended, but in some cases may
+  #   # be too noisy due to issues in dependencies.
+  #   config.warnings = true
+  #
+  #   # Many RSpec users commonly either run the entire suite or an individual
+  #   # file, and it's useful to allow more verbose output when running an
+  #   # individual spec file.
+  #   if config.files_to_run.one?
+  #     # Use the documentation formatter for detailed output,
+  #     # unless a formatter has already been configured
+  #     # (e.g. via a command-line flag).
+  #     config.default_formatter = 'doc'
+  #   end
+  #
+  #   # Print the 10 slowest examples and example groups at the
+  #   # end of the spec run, to help surface which specs are running
+  #   # particularly slow.
+  #   config.profile_examples = 10
+  #
+  #   # Run specs in random order to surface order dependencies. If you find an
+  #   # order dependency and want to debug it, you can fix the order by providing
+  #   # the seed, which is printed after each run.
+  #   #     --seed 1234
+  #   config.order = :random
+  #
+  #   # Seed global randomization in this process using the `--seed` CLI option.
+  #   # Setting this allows you to use `--seed` to deterministically reproduce
+  #   # test failures related to randomization by passing the same `--seed` value
+  #   # as the one that triggered the failure.
+  #   Kernel.srand config.seed
+end

data/examples/untested_calculator/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/examples/untested_calculator/lib/calculator/max.rb

@@ -0,0 +1,9 @@
+module Calculator
+  class Max
+    def run(left, right)
+      max = left
+      max = right if right > left
+      max
+    end
+  end
+end

data/examples/untested_calculator/lib/calculator.rb

@@ -0,0 +1,4 @@
+require_relative "calculator/max"
+
+module Calculator
+end