mrspec 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 6cbbcda0055d2073b1bc987184afd21145c4a527
+  data.tar.gz: 6131f41d4ffd68a89a00b1ba92f70f1e6b87bccb
+SHA512:
+  metadata.gz: 4f1e700ae9c81848aede3a469920d55685152b22e2d68bc65b9c65592a97f99c229af26c3d1adaa5035e7577cc8073696d0997fe42bca983f271c3d2b49ea283
+  data.tar.gz: b9cd655c7c06136b3abd010c66a4b70e2525a21f458971e2d5b6b6c2f3a9938ef39b02892b185217809d733edbd90ec762eb2f00b1d13dcc2c9e0dd56fa56253

data/.gitignore

@@ -0,0 +1,3 @@
+proving_grounds
+*.gem
+Gemfile.lock

data/.travis.yml

@@ -0,0 +1,7 @@
+language: ruby
+script:   cucumber
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - 2.1.2
+  - 2.2.2

data/Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gemspec

data/Readme.md

@@ -0,0 +1,256 @@
+[![Build Status](https://secure.travis-ci.org/JoshCheek/mrspec.png?branch=master)](http://travis-ci.org/JoshCheek/mrspec)
+
+mrspec
+======
+
+Minitest and RSpec, sitting in a tree...
+
+Runs Minitest tests using RSpec's runner.
+Also runs RSpec's tests, so if you want to use them side-by-side,
+this will do it.
+
+
+Examples
+--------
+
+
+### Run specs and tests in tandem
+
+It matches `test/*_test.rb`, `test/test_*.rb`, `spec/*_spec.rb`.
+The RSpec group description is the class name without `Test` prefix/suffix.
+The example name is the method name without the `test_` prefix,
+and with underscores switched to spaces.
+It finds test classes and test methods by asking Minitest what it is tracking.
+
+```ruby
+# file: spec/a_spec.rb
+  RSpec.describe 'An RSpec test' do
+    it('does rspec things') { }
+  end
+
+# file: test/b_test.rb
+  class AMinitestTest < Minitest::Test
+    def test_it_does_minitesty_things
+    end
+  end
+
+# file: test/test_c.rb
+  class TestSomethingElse < Minitest::Test
+    def some_helper_method # won't show up
+    end
+
+    def test_this_also_does_minitesty_things
+    end
+  end
+
+  # Added because Minitest::Runnable knows about it
+  class AnotherTestWithNeitherThePrefixNorTheSuffix < Minitest::Test
+    # This causes Minitest to consider it a test, so we consider it one
+    def self.runnables
+      ['is_this_a_test_yes_it_is']
+    end
+
+    def is_this_a_test_yes_it_is
+    end
+  end
+
+  # Ignored b/c Minitest::Runnable doesn't know about it
+  class NotATest
+    def test_whatevz
+    end
+  end
+
+# file: test/d_spec.rb
+  require 'minitest/spec'
+  describe 'I am a minitest spec' do
+    it 'does minitesty things' do
+      assert_includes self.class.ancestors, Minitest::Spec
+    end
+  end
+```
+
+![file patterns](https://s3.amazonaws.com/josh.cheek/mrspec/file-patterns.png)
+
+
+### Failures, Errors, Skips
+
+It understands Minitest skips and errors/failures.
+
+```ruby
+# file: various_errors.rb
+class VariousErrors < Minitest::Test
+  def test_this_passes()              assert true                    end
+  def test_they_arent_equal()         assert_equal 1, 2              end
+  def test_is_not_included()          assert_includes %w[a b c], 'd' end
+  def test_skipped_because…_reasons() skip                           end
+end
+```
+
+I used `--format progress` here, because there's enough errors that my default documentation
+formatter makes it spammy >.<
+
+![various errors](https://s3.amazonaws.com/josh.cheek/mrspec/various-errors2.png)
+
+
+### Fail Fast and filtering
+
+The `--fail-fast` flag is a favourite of mine. It continues running tests until it sees a failure, then it stops.
+
+We can also use tags to filter which tests to run.
+Mrspec adds RSpec metadata to Minitest classes and tests,
+the metadata behaves as a tag.
+
+The best thing about tags is they're easy to add,
+and they continue to apply to the same test, when it moves around
+(line numbers change), They stay correct even if I rename it!
+I won't have to tweak my command-line invocation until I've got the test passing!
+
+
+```ruby
+# file: test.rb
+
+# Here, we tag the `NoFailures` class with `them_passing_tests`
+# And the `TwoFailures` class with `them_failing_tests`
+class NoFailures < Minitest::Test
+  classmeta them_passing_tests: true
+
+  def test_1() end
+  def test_2() end
+end
+
+class TwoFailures < Minitest::Test
+  classmeta them_failing_tests: true
+
+  # I like short tagnames, b/c usually my use is transient.
+  # I just keep them around until they're fixed.
+  meta f1: true
+  def test_3
+    raise 'first failure'
+  end
+
+  meta f2: true
+  def test_4
+    raise 'second failure'
+  end
+end
+```
+
+![Examples of Tagging](https://s3.amazonaws.com/josh.cheek/mrspec/tagging.png)
+
+
+
+Why?
+----
+
+The default way to run minitest tests is with Rake.
+And if you have multiple suites, that can be nice,
+or if you already use Rake, then it's not adding a new dependency.
+But here are some frustrations I have with it as a test runner:
+
+1. It's not a test runner, it's a build tool. As such, it's not well suited to this task.
+1. I shouldn't have to add a dependency on Rake just to run my tests.
+1. The `Rake::TestTask` is confoundingly opaque (I rant about it [here](https://github.com/stripe/stripe-ruby/pull/144#issuecomment-48810307))
+1. It ultimately just [shells out](https://github.com/rspec/rspec-core/blob/3145e2544e1825bc754d0986e893664afe19abf5/lib/rspec/core/rake_task.rb#L70)
+   (as does the [RSpec one](https://github.com/ruby/rake/blob/e644af3a09659c7e04245186607091324d8816e9/lib/rake/testtask.rb#L104),
+   so why do I need layers of translation and abstraction between me and a command-line invocation?
+   And what's the value of adding an entire process between me and my tests?
+   Think how long Rails takes to start up, now imagine paying that twice every time you want to run your tests!
+1. It makes it incredibly difficult to dynamically alter my test invoation.
+   With Minitest, you can pass `-n test_something` and it will only run the test named `test_something`,
+   but now I have to edit code tomake that happen (or write code to uese
+   environment variables, which is better, but still cumbersome,
+   and doesn't fail noisily if I mistype it)
+
+Furthermore, if someone doesn't know about the test task, or it seems formidable, as it often does to new students
+(I'm a [teacher](http://turing.io/team)), then they won't use it. They instead run files one at a time.
+When I go to run the tests, there's just no way built in to run them all. I wind up having to craft clever command-line invocations
+using custom tools ([1](https://github.com/JoshCheek/dotfiles/blob/master/bin/ff),
+[2](https://github.com/JoshCheek/dotfiles/blob/master/bin/prepend)).
+
+```sh
+$ ff test '\.rb' | prepend -r | xargs ruby -e ''
+```
+
+Oftentimes, this is the first time they've all been run together, and we find out they haven't run a test in a long time,
+because it's too cumbersome for them (they're not good with their tools yet), it's failing or worse, syntactically invalid.
+Maybe they even know it, but they run them one at a time, so it hasn't been a problem for them yet.
+
+Anyway, all of this is to say that Minitest needs a runner.
+I hear Rails is working on one, but I don't know when that'll be available,
+and who knows if they'll write it well enough to be used outside of Rails.
+
+But the RSpec runner is very nice, it has a lot of features that I use frequently.
+Someone suggested running Minitest with the RSpec runner (see attribution section),
+and I thought that was an interesting idea that could have value if it worked.
+...so, here we are.
+
+Nuances
+-------
+
+Changes the default pattern to look for any files suffixed with `_test.rb` or `_spec.rb`, or prefixed with `test_`
+(RSpec, by itself, only looks for suffixes of `_spec.rb`).
+
+Changes the default search directories to be `test` and `spec`
+(RSpec, by itself, only looks in `spec`).
+
+Turns off monkey patching, so you cannot use RSPec's toplevel describe, or `should`.
+There are 2 reasons for this:
+
+1. It conflicts with `Minitest::Spec`'s definition of `Kernel#describe`
+   ([here](https://github.com/seattlerb/minitest/blob/f1081566ec6e9e391628bde3a26fb057ad2576a8/lib/minitest/spec.rb#L71)).
+   And must be preemptively turned off, because after-the-fact disabling
+   causes it to be undefined on both `main` and `Module` ([here](https://github.com/rspec/rspec-core/blob/3145e2544e1825bc754d0986e893664afe19abf5/lib/rspec/core/dsl.rb#L72)),
+   which means that even if you don't use it, it will still interfere with `Minitest::Spec`
+   (removing methods allows method lookup to find superclass definitions,
+   but undefining them ends method lookup.)
+2. You should just not do that in general. Monkey patching is a bad plan, all around,
+   just use the namespaced methods, or create your own methods to wrap the assertion syntax.
+   I'm looking forward to when this feature is removed altogether.
+
+
+Running the tests
+-----------------
+
+```sh
+$ bundle
+$ bundle exec cucumber
+```
+
+Why are all the tests written in Cucumber?
+Well... mostly just b/c I initially wrote this as a script for my dotfiles,
+which I mostly test with Cucumber and [Haiti](https://github.com/JoshCheek/haiti),
+as they are usually heavily oriented towards integration,
+and often not written in Ruby.
+
+
+Attribution
+-----------
+
+Idea from [e2](https://github.com/e2), proposed [here](https://github.com/rspec/rspec-core/issues/1786).
+Iniitial code was based off of [this gist](https://gist.github.com/e2/bcd2be81b4ac28c85ea0)
+
+
+MIT License
+-----------
+
+```
+Copyright (c) 2015 Josh Cheek
+
+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/bin/mrspec

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby
+
+$LOAD_PATH.unshift File.expand_path("../../lib", __FILE__)
+require 'mrspec'
+
+# All your config are belong to us
+RSpec.configuration = MRspec::Configuration.new
+
+# Use our option parser instead of RSpec's
+RSpec::Core::Parser.parser_method = RSpec::Core::Parser.instance_method :mrspec_parser
+
+# Run tests with our runner at program exit
+MRspec::Runner.autorun
+
+# Disable RSpec and Minitest's autorun methods
+# so that loading tests doesn't lead to multiple runners
+RSpec::Core::Runner.define_singleton_method(:autorun) { }
+Minitest.define_singleton_method(:autorun) { }

data/features/mrspec.feature

@@ -0,0 +1,475 @@
+Feature: mrspec
+  Minitest doesn't have a runner, but a runner would be really nice.
+  RSpec has a nice runner... so lets join them together!
+
+  Scenario: Finds spec/**/*_spec.rb and test/**/*_test.rb and test/**/test_*.rb
+    Given the file "spec/a_spec.rb":
+    """
+    RSpec.describe 'a' do
+      it('passes') { }
+    end
+    """
+    And the file "spec/dir/b_spec.rb":
+    """
+    RSpec.describe 'b' do
+      it('passes') { }
+    end
+    """
+    And the file "test/c_test.rb":
+    """
+    class CTest < Minitest::Test
+      def test_passes
+      end
+    end
+    """
+    And the file "test/dir/d_test.rb":
+    """
+    class DTest < Minitest::Test
+      def test_passes
+      end
+    end
+    """
+    And the file "test/dir/test_e.rb":
+    """
+    class ETest < Minitest::Test
+      def test_passes
+      end
+    end
+    """
+    And the file "test/a_test_file.rb":
+    """
+    raise "I should not be loaded!"
+    """
+    And the file "spec/a_spec_file.rb":
+    """
+    raise "I should not be loaded!"
+    """
+    When I run 'mrspec -f json'
+    Then the program ran successfully
+    And stdout includes "5 examples"
+    And stdout includes "0 failures"
+
+
+  Scenario: Registers minitest tests as RSpec tests, recording skips, passes, errors, failures
+    Given the file "some_test.rb":
+    """
+    class LotaStuffsTest < Minitest::Test
+      def test_passes
+      end
+
+      def test_fails
+        assert_equal 1, 2
+      end
+
+      def test_errors
+        raise 'omg'
+      end
+
+      def test_skips
+        skip
+      end
+    end
+    """
+    When I run "mrspec some_test.rb --no-color --format progress"
+
+    # counts correctly
+    Then stdout includes "4 examples"
+    And stdout includes "2 failures"
+    And stdout includes "1 pending"
+    And stdout does not include "No examples found"
+
+    # displays the failed assertion, not an error
+    And stdout includes "Expected: 1"
+    And stdout includes "Actual: 2"
+
+    # displays the test's code, not the integration code
+    And stdout includes "raise 'omg'"
+    And stdout includes "assert_equal 1, 2"
+    And stdout does not include "Minitest.run_one_method"
+
+
+  Scenario: Works with Minitest::Test, choosing intelligent names
+    Given the file "some_test.rb":
+    """
+    class MyClass1Test < Minitest::Test
+      def test_it_does_stuff
+      end
+    end
+
+    class TestMyClass2 < Minitest::Test
+      def test_it_does_stuff
+      end
+    end
+    """
+    When I run "mrspec some_test.rb -f json"
+    Then the program ran successfully
+    And stdout includes '"full_description":"MyClass1 it does stuff"'
+    And stdout includes '"full_description":"MyClass2 it does stuff"'
+
+
+  Scenario: Works with Minitest::Spec, choosing intelligent names
+    Given the file "some_spec.rb":
+    """
+    require 'minitest/spec'
+    describe 'the description' do
+      it 'the example' do
+        assert true
+        if kind_of? Minitest::Spec
+          puts "I am defined by Minitest::Spec"
+        end
+      end
+    end
+    """
+    When I run "mrspec some_spec.rb -f json"
+    Then stdout includes "1 example"
+    And stdout includes "0 failures"
+    And stdout includes "I am defined by Minitest::Spec"
+    And stdout includes '"description":"the example"'
+    And stdout includes '"full_description":"the description the example"'
+
+
+  Scenario: Filters the runner and minitest code out of the backtrace do
+    Given the file "some_test.rb":
+    """
+    class LotaStuffsTest < Minitest::Test
+      def test_errors
+        raise "zomg"
+      end
+    end
+    """
+    When I run "mrspec some_test.rb"
+    Then stdout does not include "minitest"
+    And stdout does not include "mrspec.rb"
+    And stdout does not include "bin/mrspec"
+
+
+  Scenario: --fail-fast flag
+    Given the file "fails_fast_test.rb":
+    """
+    class TwoFailures < Minitest::Test
+      i_suck_and_my_tests_are_order_dependent!
+      def test_1
+        raise
+      end
+      def test_2
+        raise
+      end
+    end
+    """
+    When I run 'mrspec fails_fast_test.rb --fail-fast'
+    Then stdout includes "1 example"
+
+
+  Scenario: -e flag
+    Given the file "spec/first_spec.rb":
+    """
+    RSpec.describe 'a' do
+      example('b') { }
+    end
+    """
+    Given the file "test/first_test.rb":
+    """
+    class FirstTest < Minitest::Test
+      def test_1
+      end
+    end
+    """
+    And the file "test/second_test.rb":
+    """
+    class SecondTest < Minitest::Test
+      def test_2
+      end
+    end
+    """
+    When I run 'mrspec -e Second'
+    Then stdout includes "1 example"
+    And stdout does not include "2 examples"
+
+
+  Scenario: Passing a filename overrides the default pattern
+    Given the file "spec/first_spec.rb":
+    """
+    RSpec.describe 'first spec' do
+      example('rspec 1') { }
+    end
+    """
+    Given the file "test/first_test.rb":
+    """
+    class FirstTest < Minitest::Test
+      def test_minitest_1
+      end
+    end
+    """
+    And the file "test/second_test.rb":
+    """
+    class SecondTest < Minitest::Test
+      def test_minitest_2
+      end
+    end
+    """
+    When I run 'mrspec -f d test/second_test.rb'
+    Then stdout includes "1 example"
+    And  stdout includes "minitest 2"
+    And  stdout does not include "rspec 1"
+    And  stdout does not include "minitest 1"
+
+
+  Scenario: Can add metadata to examples, ie run only tagged tests
+    Given the file "test/tag_test.rb":
+    """
+    class TagTest < Minitest::Test
+      meta first: true
+      def test_1
+        puts "ran test 1"
+      end
+
+      # multiple tags in meta, and aggregated across metas
+      meta second: true, second2: true
+      meta second3: true
+      def test_2
+        puts "ran test 2"
+      end
+
+      def test_3
+        puts "ran test 3"
+      end
+    end
+    """
+
+    # only test_1 is tagged w/ first
+    When I run 'mrspec test/tag_test.rb -t first'
+    Then the program ran successfully
+    Then stdout includes "1 example"
+    And stdout includes "ran test 1"
+    And stdout does not include "ran test 2"
+    And stdout does not include "ran test 3"
+
+    # test_2 is tagged w/ second, and second2 (multiple tags in 1 meta)
+    When I run 'mrspec test/tag_test.rb -t second'
+    Then stdout includes "1 example"
+    And stdout includes "ran test 2"
+    And stdout does not include "ran test 1"
+    And stdout does not include "ran test 3"
+
+    When I run 'mrspec test/tag_test.rb -t second2'
+    Then stdout includes "1 example"
+    And stdout includes "ran test 2"
+    And stdout does not include "ran test 1"
+    And stdout does not include "ran test 3"
+
+    # test_2 is tagged with second3 (consolidates metadata until they are used)
+    When I run 'mrspec test/tag_test.rb -t second3'
+    Then stdout includes "1 example"
+    And stdout includes "ran test 2"
+    And stdout does not include "ran test 1"
+    And stdout does not include "ran test 3"
+
+    # for sanity, show that test_3 is actually a test, just not tagged (metadata gets cleared)
+    When I run 'mrspec test/tag_test.rb'
+    Then stdout includes "3 examples"
+    And stdout includes "ran test 1"
+    And stdout includes "ran test 2"
+    And stdout includes "ran test 3"
+
+
+  Scenario: Can add metadata to groups
+    Given the file "tag_groups.rb":
+    """
+    class Tag1Test < Minitest::Test
+      classmeta tag1: true
+
+      meta tag2: true
+      def test_tagged_with_1_and_2
+      end
+
+      def test_tagged_with_1_only
+      end
+    end
+
+    class UntaggedTest < Minitest::Test
+      def test_untagged
+      end
+    end
+    """
+
+    # tag1 runs all tests in Tag1Test (b/c the tag is on the class)
+    When I run 'mrspec -f d -t tag1 tag_groups.rb'
+    Then the program ran successfully
+    And  stdout includes "tagged with 1 and 2"
+    And  stdout includes "tagged with 1 only"
+    And  stdout does not include "untagged"
+
+    # tag2 runs only Tag1Test#test_tagged_with_1_and_2 (b/c the tag is on the method)
+    When I run 'mrspec -f d -t tag2 tag_groups.rb'
+    Then the program ran successfully
+    And  stdout includes "tagged with 1 and 2"
+    And  stdout does not include "tagged with 1 only"
+    And  stdout does not include "untagged"
+
+    # no tags runs all tests (ignores all tagging)
+    When I run 'mrspec -f d tag_groups.rb'
+    Then the program ran successfully
+    And  stdout includes "tagged with 1 and 2"
+    And  stdout includes "tagged with 1 only"
+    And  stdout includes "untagged"
+
+  Scenario: Intelligently formats Minitest's assertions
+    Given the file "test/some_assertions.rb":
+    """
+    RSpec.describe 'a' do
+      it('fails1') { expect('rspec-1').to eq 'rspec-2' }
+      it('fails2') { expect(%w[rspec a b c]).to include 'd' }
+    end
+
+    class A < Minitest::Test
+      def test_fails1() assert_equal 'minitest-1', 'minitest-2' end
+      def test_fails2() assert_includes %w[minitest a b c], 'd' end
+    end
+    """
+    When I run 'mrspec --no-color test/some_assertions.rb'
+    # RSpec eq
+    Then stdout includes 'expected: "rspec-2"'
+    And  stdout includes '     got: "rspec-1"'
+    # Minitest assert_equal
+    And  stdout includes 'Expected: "minitest-1"'
+    And  stdout includes '  Actual: "minitest-2"'
+
+    # RSpec includes
+    And  stdout includes 'expected ["rspec", "a", "b", "c"] to include "d"'
+    # Minitest assert_includes
+    And  stdout includes 'Expected ["minitest", "a", "b", "c"] to include "d"'
+
+    # Doesn't print Minitest::Assertion class, as if it's an exception
+    And  stdout does not include "Minitest::Assertion"
+
+  Scenario: Respects Minitest's lifecycle hooks
+    Given the file "test/lifecycle_test.rb":
+    """
+    class A < Minitest::Test
+      %w(before_teardown teardown after_teardown before_setup setup after_setup).shuffle.each do |methodname|
+        define_method methodname do
+          @order ||= []
+          @order << methodname
+        end
+      end
+
+      def test_1
+        @order << :test_1
+        at_exit { puts "[#{@order.join " "}]" }
+      end
+
+      def test_2
+        @order << :test_2
+        at_exit { puts "[#{@order.join " "}]" }
+      end
+    end
+    """
+    When I run "mrspec test/lifecycle_test.rb"
+    Then the program ran successfully
+    And  stdout includes "[before_setup setup after_setup test_1 before_teardown teardown after_teardown]"
+    And  stdout includes "[before_setup setup after_setup test_2 before_teardown teardown after_teardown]"
+
+
+  Scenario: Doesn't get fucked up by Minitest autorunning
+    Given the file "requires_minitest_autorun.rb":
+    """
+    require 'minitest/autorun'
+    class A < Minitest::Test
+      def test_a
+        p caller.last # will tell us which lib is running this test
+      end
+    end
+    """
+    When I run "mrspec requires_minitest_autorun.rb"
+    Then stdout includes "rspec/core/runner.rb"
+    And  stdout does not include "lib/minitest.rb"
+
+
+  Scenario: Doesn't get fucked up by RSpec autorunning
+    Given the file "requires_rspec_autorun.rb":
+    """
+    require 'rspec/autorun'
+
+    $load_count ||= 0
+    $load_count += 1
+
+    RSpec.describe 'something' do
+      it 'does whatever' do
+        $run_count ||= 0
+        $run_count += 1
+        puts "load count: #{$load_count}"
+        puts "run count:  #{$run_count}"
+      end
+    end
+    """
+    When I run "mrspec requires_rspec_autorun.rb"
+    Then stdout includes "load count: 1"
+    And  stdout includes "run count:  1"
+    And  stdout does not include "load count: 2"
+    And  stdout does not include "run count:  2"
+
+
+  Scenario: Doesn't depend on RSpec::Mocks or RSpec::Expectations
+    Given the file "no_dev_deps/Gemfile":
+    """
+    source 'https://rubygems.org'
+    gem 'mrspec', path: "{{root_dir}}"
+    """
+    When I run "env BUNDLE_GEMFILE=no_dev_deps/Gemfile bundle install"
+    Then the program ran successfully
+
+    Given the file "no_dev_deps/print_results.rb":
+    """
+    at_exit do
+      exception = $!
+      if exception.kind_of? SystemExit
+        puts "ERROR: SYSTEM EXIT (RSpec raises this if there's a failure)"
+      elsif exception
+        puts "AN ERROR: #{$!.inspect}"
+      else
+        puts "NO ERROR"
+      end
+
+      unexpected_deps = $LOADED_FEATURES.grep(/rspec/).grep(/mocks|expectations/)
+      if unexpected_deps.any?
+        puts "UNEXPECTED DEPS: #{unexpected_deps}"
+      else
+        puts "NO UNEXPECTED DEPS"
+      end
+    end
+    """
+    And the file "no_dev_deps/test_with_failures.rb":
+    """
+    require_relative 'print_results'
+    class A < Minitest::Test
+      def test_that_passes() assert_equal 1, 1 end
+      def test_that_fails()  assert_equal 1, 2 end
+      def test_that_errors() raise "wat"       end
+      def test_that_skips()  skip              end
+    end
+    """
+
+    When I run "env BUNDLE_GEMFILE=no_dev_deps/Gemfile bundle exec mrspec no_dev_deps/test_with_failures.rb"
+    Then stderr is empty
+    And  stdout includes "4 examples"
+    And  stdout includes "2 failures"
+    And  stdout includes "1 pending"
+    And  stdout includes "ERROR: SYSTEM EXIT"
+    And  stdout includes "NO UNEXPECTED DEPS"
+
+    Given the file "no_dev_deps/test_that_passes.rb":
+    """
+    require_relative 'print_results'
+    class A < Minitest::Test
+      def test_that_passes() assert true end
+    end
+    """
+    When I run "env BUNDLE_GEMFILE=no_dev_deps/Gemfile bundle exec mrspec -f p no_dev_deps/test_that_passes.rb"
+    Then the program ran successfully
+    And  stdout includes "NO ERROR"
+    And  stdout includes "NO UNEXPECTED DEPS"
+
+  Scenario: The help screen is custom to mrspec
+    When I run "mrspec -h"
+    Then stdout includes "Usage: mrspec"
+    # Probably add more later

data/features/support/env.rb

@@ -0,0 +1,31 @@
+require 'haiti'
+require 'tmpdir'
+require 'fileutils'
+
+proving_grounds_dir = Dir.mktmpdir
+After { FileUtils.remove_entry proving_grounds_dir }
+
+Haiti.configure do |config|
+  config.proving_grounds_dir = proving_grounds_dir
+  config.bin_dir             = File.expand_path('../../../bin', __FILE__)
+end
+
+module GeneralHelpers
+  def pwd
+    Haiti.config.proving_grounds_dir
+  end
+
+  def root_dir
+    @root_dir ||= File.expand_path '../../..', __FILE__
+  end
+end
+
+When 'I pry' do
+  require "pry"
+  binding.pry
+end
+
+Then 'the program ran successfully' do
+  expect(@last_executed.stderr).to eq ""
+  expect(@last_executed.exitstatus).to eq 0
+end

data/lib/mrspec/configuration.rb

@@ -0,0 +1,18 @@
+require 'mrspec/declare_minitests'
+require 'rspec/core'
+
+module MRspec
+  class Configuration < RSpec::Core::Configuration
+    def initialize(*)
+      super
+      disable_monkey_patching!
+      filter_gems_from_backtrace 'mrspec', 'minitest'
+      self.pattern = pattern.sub '*_spec.rb', '{*_spec,*_test,test_*}.rb'
+    end
+
+    def load_spec_files(*)
+      super
+      MRspec::DeclareMinitests.call
+    end
+  end
+end

data/lib/mrspec/declare_minitests.rb

@@ -0,0 +1,64 @@
+require 'minitest'
+require 'mrspec/minitest_assertion_for_rspec'
+
+module MRspec
+  module DeclareMinitests
+    extend self
+
+    def self.call
+      init_minitest
+      wrap_classes Minitest::Runnable.runnables
+    end
+
+    def group_name(klass)
+      klass.name.sub(/^Test/, '').sub(/Test$/, '')
+    end
+
+    def example_name(method_name)
+      # remove test_, and turn underscores into spaces
+      #   https://github.com/seattlerb/minitest/blob/f1081566ec6e9e391628bde3a26fb057ad2576a8/lib/minitest/test.rb#L62
+      # remove test_0001_, where the number increments
+      #   https://github.com/seattlerb/minitest/blob/f1081566ec6e9e391628bde3a26fb057ad2576a8/lib/minitest/spec.rb#L218-222
+      method_name.sub(/^test_(?:\d{4}_)?/, '').tr('_', ' ')
+    end
+
+    def init_minitest
+      Minitest.reporter = Minitest::CompositeReporter.new # we're not using the reporter, but some plugins, (eg minitest/pride) expect it to be there
+      Minitest.load_plugins
+      Minitest.init_plugins Minitest.process_args([])
+    end
+
+    def wrap_classes(klasses)
+      klasses.each { |klass| wrap_class klass }
+    end
+
+    def wrap_class(klass)
+      example_group = RSpec.describe group_name(klass), klass.class_metadata
+      klass.runnable_methods.each do |method_name|
+        wrap_test example_group, klass, method_name
+      end
+    end
+
+    def wrap_test(example_group, klass, mname)
+      metadata = klass.example_metadata[mname.intern]
+      example = example_group.example example_name(mname), metadata do
+        instance = Minitest.run_one_method klass, mname
+        next              if instance.passed?
+        pending 'skipped' if instance.skipped?
+        error = instance.failure.error
+        raise error unless error.kind_of? Minitest::Assertion
+        raise MinitestAssertionForRSpec.new error
+      end
+      fix_metadata example.metadata, klass.instance_method(mname)
+    end
+
+    def fix_metadata(metadata, method)
+      file, line = method.source_location
+      return unless file && line # not sure when this wouldn't be true, so no tests on it, but hypothetically it could happen
+      metadata[:file_path]          = file
+      metadata[:line_number]        = line
+      metadata[:location]           = "#{file}:#{line}"
+      metadata[:absolute_file_path] = File.expand_path(file)
+    end
+  end
+end

data/lib/mrspec/minitest_assertion_for_rspec.rb

@@ -0,0 +1,15 @@
+module MRspec
+  # With assertions, we must wrap it in a class that has "RSpec" in the name
+  #   https://github.com/rspec/rspec-core/blob/3145e2544e1825bc754d0986e893664afe19abf5/lib/rspec/core/formatters/exception_presenter.rb#L94
+  #   This is how RSpec differentiates failures from exceptions (errors get their class printed, failures do not)
+  #   We could wrap it in an ExpectationNotMetError, as all their errors seem to be,
+  #   but that is defined in rspec-expectations, which we otherwise don't depend on.
+  #
+  # We'll keep the Minitest error messages, though, as they were on par with RSpec's for all the examples I tried
+  class MinitestAssertionForRSpec < Exception
+    def initialize(assertion)
+      super assertion.message
+      set_backtrace assertion.backtrace
+    end
+  end
+end

data/lib/mrspec/minitest_metadata.rb

@@ -0,0 +1,35 @@
+require 'minitest'
+
+# Allow Minitest to support RSpec's metadata (eg tagging)
+# Thus you can tag a test or a class, and then pass `-t mytag` to mrspec,
+# and it will only run the tagged code.
+class << Minitest::Runnable
+  # Add metadata to the current class
+  def classmeta(metadata)
+    class_metadata.merge! metadata
+  end
+
+  # Add metadata to the next defined test
+  def meta(metadata)
+    pending_metadata.merge! metadata
+  end
+
+  def class_metadata
+    @selfmetadata ||= {}
+  end
+
+  def example_metadata
+    @metadata ||= Hash.new { |metadata, mname| metadata[mname] = {} }
+  end
+
+  private
+
+  def method_added(manme)
+    example_metadata[manme.intern].merge! pending_metadata
+    pending_metadata.clear
+  end
+
+  def pending_metadata
+    @pending_metadata ||= {}
+  end
+end

data/lib/mrspec/option_parser.rb

@@ -0,0 +1,30 @@
+require 'rspec/core/option_parser'
+
+class RSpec::Core::Parser
+  # Trying to mitigate the invasiveness of this code.
+  # It's not great, but it's better than unconditionally overriding the method.
+  # We have to do this, b/c OptionParser will print directly to stdout/err
+  # and call `exit`: https://gist.github.com/JoshCheek/7adc25a46e735510558d
+  # The RSpec portion does this, too https://github.com/rspec/rspec-core/blob/3145e2544e1825bc754d0986e893664afe19abf5/lib/rspec/core/option_parser.rb#L267-299
+  # so we need to get between the definition and the parsing to make any changes
+
+  # Save RSpec's parser
+  alias rspec_parser parser
+
+  # Ours calls RSpec's, then modifies values on the returned parser
+  def mrspec_parser(*args, &b)
+    rspec_parser(*args, &b).tap { |parser| parser.banner.gsub! /\brspec\b/, 'mrspec' }
+  end
+
+  # A place to store which method `parser` actually resolves to
+  singleton_class.class_eval { attr_accessor :parser_method }
+
+  # Default it to RSpec's, because requiring this file shouldn't fuck up your environment,
+  # We'll swap the value in the binary, that decision belongs as high in the callstack as we can get it.
+  self.parser_method = instance_method :rspec_parser
+
+  # The actual parser method just delegates to the saved one (ultra-late binding :P)
+  define_method :parser do |*args, &b|
+    self.class.parser_method.bind(self).call(*args, &b)
+  end
+end

data/lib/mrspec/runner.rb

@@ -0,0 +1,12 @@
+require 'rspec/core/runner'
+
+module MRspec
+  class Runner < RSpec::Core::Runner
+    def initialize(*)
+      super
+      # seems like there should be a better way, but I can't figure out what it is
+      files_and_dirs = @options.options[:files_or_directories_to_run]
+      files_and_dirs << 'spec' << 'test' if files_and_dirs.empty?
+    end
+  end
+end

data/lib/mrspec/version.rb

@@ -0,0 +1,3 @@
+module MRspec
+  VERSION = '0.0.1'
+end

data/lib/mrspec.rb

@@ -0,0 +1,4 @@
+require 'mrspec/minitest_metadata'
+require 'mrspec/runner'
+require 'mrspec/configuration'
+require 'mrspec/option_parser'

data/mrspec.gemspec

@@ -0,0 +1,24 @@
+$:.push File.expand_path("../lib", __FILE__)
+require "mrspec/version"
+
+Gem::Specification.new do |s|
+  s.name        = "mrspec"
+  s.version     = MRspec::VERSION
+  s.authors     = ["Josh Cheek"]
+  s.email       = ["josh.cheek@gmail.com"]
+  s.homepage    = "https://github.com/JoshCheek/mrspec"
+  s.summary     = %q{Minitest tests + RSpec's test runner}
+  s.description = %q{Allows you to run Minitest tests and specs with RSpec's runner, thus you can write both Minitest and RSpec, side-by-side, and take advantage of the many incredibly helpful features it supports (primarily: better formatters, --colour, --fail-fast, and tagging).}
+  s.license     = "MIT"
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = ['mrspec']
+  s.require_paths = ['lib']
+
+  s.add_dependency "rspec-core", "~> 3.0"
+  s.add_dependency "minitest",   "~> 5.0"
+
+  s.add_development_dependency "haiti",    ">= 0.2.2", "< 0.3"
+  s.add_development_dependency "cucumber", "~> 2.0"
+end

metadata

@@ -0,0 +1,129 @@
+--- !ruby/object:Gem::Specification
+name: mrspec
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Josh Cheek
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2015-05-20 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rspec-core
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: minitest
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+- !ruby/object:Gem::Dependency
+  name: haiti
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.2.2
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '0.3'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.2.2
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '0.3'
+- !ruby/object:Gem::Dependency
+  name: cucumber
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+description: 'Allows you to run Minitest tests and specs with RSpec''s runner, thus
+  you can write both Minitest and RSpec, side-by-side, and take advantage of the many
+  incredibly helpful features it supports (primarily: better formatters, --colour,
+  --fail-fast, and tagging).'
+email:
+- josh.cheek@gmail.com
+executables:
+- mrspec
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".travis.yml"
+- Gemfile
+- Readme.md
+- bin/mrspec
+- features/mrspec.feature
+- features/support/env.rb
+- lib/mrspec.rb
+- lib/mrspec/configuration.rb
+- lib/mrspec/declare_minitests.rb
+- lib/mrspec/minitest_assertion_for_rspec.rb
+- lib/mrspec/minitest_metadata.rb
+- lib/mrspec/option_parser.rb
+- lib/mrspec/runner.rb
+- lib/mrspec/version.rb
+- mrspec.gemspec
+homepage: https://github.com/JoshCheek/mrspec
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.4.1
+signing_key: 
+specification_version: 4
+summary: Minitest tests + RSpec's test runner
+test_files:
+- features/mrspec.feature
+- features/support/env.rb
+has_rdoc: