mrspec 0.0.1 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6cbbcda0055d2073b1bc987184afd21145c4a527
-  data.tar.gz: 6131f41d4ffd68a89a00b1ba92f70f1e6b87bccb
+  metadata.gz: c9b7422e1ee184d93d1efcb320e1d66d95261d72
+  data.tar.gz: 2cb80072ccc287fce0ae9deeeaf5e4cf7714f755
 SHA512:
-  metadata.gz: 4f1e700ae9c81848aede3a469920d55685152b22e2d68bc65b9c65592a97f99c229af26c3d1adaa5035e7577cc8073696d0997fe42bca983f271c3d2b49ea283
-  data.tar.gz: b9cd655c7c06136b3abd010c66a4b70e2525a21f458971e2d5b6b6c2f3a9938ef39b02892b185217809d733edbd90ec762eb2f00b1d13dcc2c9e0dd56fa56253
+  metadata.gz: a4f44abb23f546d633264ad6d0f91d769cb8e56afc3c92051c4371bc2c5ae582f80aef74dae65ca1349d839775316fe0bc9311501c26e1019e02d7ee54ddc3f5
+  data.tar.gz: 5d7e7dc0778e64e6d6269caf5b03930a5d09d24f0fc6844fabfecad914dd53edc9c07ce98863f18fe29890a399a83de7f1f0b2c55d44c201538daad5333c21cd

data/.travis.yml

@@ -1,5 +1,5 @@
 language: ruby
-script:   cucumber
+script:   bin/mrspec --colour --format documentation && cucumber
 rvm:
   - 1.9.3
   - 2.0.0

data/Readme.md

@@ -3,7 +3,7 @@
 mrspec
 ======
 
-Minitest and RSpec, sitting in a tree...
+Minitest and RSpec, sitting in a tree, T. E. S. T. I. N. G!
 
 Runs Minitest tests using RSpec's runner.
 Also runs RSpec's tests, so if you want to use them side-by-side,
@@ -138,6 +138,13 @@ end
 ![Examples of Tagging](https://s3.amazonaws.com/josh.cheek/mrspec/tagging.png)
 
 
+Default configuration
+---------------------
+
+You can place a file named `.rspec` in your home directory with command-line arguments in it.
+These will be used as defaults when you run `mrspec` or `rspec`.
+[Here](https://github.com/JoshCheek/dotfiles/blob/5948132cd2367ef3b86fd2ce5351948a65d7aec7/rspec) is mine.
+
 
 Why?
 ----
@@ -147,37 +154,27 @@ 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.
+1. I don't want to add a dependency on Rake, unless I need it.
+1. The `Rake::TestTask` is difficult to make sense of.
+1. The Rake tasks ultimately just shell out ([RSpec's](https://github.com/rspec/rspec-core/blob/3145e2544e1825bc754d0986e893664afe19abf5/lib/rspec/core/rake_task.rb#L70),
+   [Minitest's](https://github.com/ruby/rake/blob/e644af3a09659c7e04245186607091324d8816e9/lib/rake/testtask.rb#L104)).
+   So I don't see what they offer over invoking the program directly (usually I know what I want to pass the program,
+   and I am trying to figure out how to configure the test task to do that).
+   The overhead of running additional processes can also be high:
+   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 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)
+   but now I have to edit code tomake that happen.
 
 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.
+When I go to run the tests, they don't have a way to run all of them.
+This overhead, in turn, disinclines them to run the tests,
+such that they may be failing and not realize it.
 
 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.
+or if it will be written in a way that it can 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),
@@ -193,6 +190,9 @@ Changes the default pattern to look for any files suffixed with `_test.rb` or `_
 Changes the default search directories to be `test` and `spec`
 (RSpec, by itself, only looks in `spec`).
 
+Adds `test` to the `$LOAD_PATH`, if it exists.
+(RSpec, by itself, only adds `spec`).
+
 Turns off monkey patching, so you cannot use RSPec's toplevel describe, or `should`.
 There are 2 reasons for this:
 
@@ -203,9 +203,10 @@ There are 2 reasons for this:
    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,
+2. You should avoid things like this, 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.
+
+Only expected to support Rubies in the [.travis.yml](https://github.com/JoshCheek/mrspec/blob/fa1945d3d4941a90a3272020b51468dfb42f8212/.travis.yml).
 
 
 Running the tests
@@ -213,6 +214,7 @@ Running the tests
 
 ```sh
 $ bundle
+$ bundle exec bin/mrspec
 $ bundle exec cucumber
 ```
 
@@ -222,6 +224,13 @@ 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.
 
+What about the `test` directory?
+I decided to describe all the behaviour that can be unit tested,
+but haven't taken the time to implement most of them yet,
+because I don't currently have any features I'm trying to add.
+As I maintain this, though, I'll begin implementing them,
+as it will be easier in the end :)
+
 
 Attribution
 -----------

data/bin/mrspec

@@ -1,8 +1,13 @@
 #!/usr/bin/env ruby
 
+# Load our lib
 $LOAD_PATH.unshift File.expand_path("../../lib", __FILE__)
 require 'mrspec'
 
+# Put ./test in the load path
+test_dir = File.expand_path('test', Dir.pwd)
+$LOAD_PATH.unshift test_dir if Dir.exist? test_dir
+
 # All your config are belong to us
 RSpec.configuration = MRspec::Configuration.new
 

data/features/mrspec.feature

@@ -469,7 +469,26 @@ Feature: mrspec
     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
+
+
+  # Only specifying the major version, so I get enough to be confident
+  # but not enough to be too volatile
+  Scenario: Prints mrspec, rspec, and minitest versions for --version
+    When I run "mrspec --version"
+    Then the program ran successfully
+    And  stdout includes "mrspec     0."
+    And  stdout includes "rspec-core 3."
+    And  stdout includes "minitest   5."
+
+
+  Scenario: Adds absolute path to `./test` to the $LOAD_PATH, if it exists
+    Given the file "test/my_helper.rb" "puts 'I got loaded!'"
+    And   the file "test/some_test.rb" "Dir.chdir('/') { require 'my_helper' }"
+    When I run "mrspec"
+    Then the program ran successfully
+    And stdout includes "I got loaded!"

data/lib/mrspec.rb

@@ -1,3 +1,4 @@
+require 'mrspec/version'
 require 'mrspec/minitest_metadata'
 require 'mrspec/runner'
 require 'mrspec/configuration'

data/lib/mrspec/configuration.rb

@@ -12,7 +12,7 @@ module MRspec
 
     def load_spec_files(*)
       super
-      MRspec::DeclareMinitests.call
+      MRspec::DeclareMinitests.call(RSpec, Minitest, Minitest::Runnable.runnables)
     end
   end
 end

data/lib/mrspec/declare_minitests.rb

@@ -5,13 +5,18 @@ module MRspec
   module DeclareMinitests
     extend self
 
-    def self.call
-      init_minitest
-      wrap_classes Minitest::Runnable.runnables
+    def self.call(rspec, minitest, klasses)
+      init_minitest minitest
+      wrap_classes rspec, klasses
     end
 
     def group_name(klass)
-      klass.name.sub(/^Test/, '').sub(/Test$/, '')
+      if klass.name
+        klass.name.to_s.sub(/^Test/, '').sub(/Test$/, '')
+      else
+        inspection = Kernel.instance_method(:inspect).bind(klass).call
+        "Anonymous Minitest for class #{inspection}"
+      end
     end
 
     def example_name(method_name)
@@ -19,21 +24,21 @@ module MRspec
       #   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('_', ' ')
+      method_name.to_s.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([])
+    def init_minitest(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 }
+    def wrap_classes(rspec, klasses)
+      klasses.each { |klass| wrap_class rspec, klass }
     end
 
-    def wrap_class(klass)
-      example_group = RSpec.describe group_name(klass), klass.class_metadata
+    def wrap_class(rspec, 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

data/lib/mrspec/option_parser.rb

@@ -13,7 +13,22 @@ class RSpec::Core::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' }
+    option_parser = rspec_parser(*args, &b)
+
+    # update the program name
+    option_parser.banner.gsub! /\brspec\b/, 'mrspec'
+
+    # print mrspec version, and dependency versions.
+    # calling exit and toplevel puts, b/c that's what RSpec's does https://github.com/rspec/rspec-core/blob/c7c1154934c42b5f6905bb7bd22025fe6c8a816c/lib/rspec/core/option_parser.rb#L290
+    # and I don't feel like figuring out how to work around it.
+    option_parser.on('-v', '--version', 'Display the version.') do
+      puts "mrspec     #{MRspec::VERSION}\n"\
+           "rspec-core #{RSpec::Core::Version::STRING}\n"\
+           "minitest   #{Minitest::VERSION}\n"
+      exit
+    end
+
+    option_parser
   end
 
   # A place to store which method `parser` actually resolves to

data/lib/mrspec/version.rb

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

data/test/support/helper.rb

@@ -0,0 +1,6 @@
+# Don't filter mrspec out of the backtrace when testing itslef!
+RSpec.configure do |config|
+  config.backtrace_formatter.exclusion_patterns.reject! do |pattern|
+    pattern =~ "/mrspec/"
+  end
+end

data/test/support/mock.rb

@@ -0,0 +1,65 @@
+module Mock
+  def mock_rspec
+    @mock_rspec ||= Mock::RSpec.new
+  end
+
+  def mock_minitest
+    @mock_minitest ||= Mock::Minitest.new
+  end
+
+  # This name can't match /^test_/, or https://github.com/seattlerb/minitest/blob/f1081566ec6e9e391628bde3a26fb057ad2576a8/lib/minitest/spec.rb#L167-171
+  # ...legit thought I'd forgotten the object model for a moment there O.o
+  def a_test_named(name, &block)
+    Class.new(Mock::MinitestTest, &block).tap do |klass|
+      klass.define_singleton_method(:name) { name }
+    end
+  end
+
+  def a_spec_named(name)
+    skip 'Not worth figuring this out right now'
+    Class.new Mock::MinitestSpec do
+    end
+  end
+end
+
+class Mock::MinitestTest < ::Minitest::Test
+  # noop, just preventing our testing from globally registering tests
+  def self.inherited(*)
+  end
+
+  # And unregister this mock class
+  Minitest::Runnable.runnables.delete self
+end
+
+class Mock::RSpec
+  def groups
+    @groups ||= []
+  end
+
+  def group_names
+    groups.map &:name
+  end
+
+  def examples
+    groups.flat_map &:examples
+  end
+
+  def describe(name, metadata, &block)
+    group = ExampleGroup.new name, metadata
+    groups << group
+    group.module_exec(&block) if block # https://github.com/rspec/rspec-core/blob/c7c1154934c42b5f6905bb7bd22025fe6c8a816c/lib/rspec/core/example_group.rb#L363
+    group
+  end
+end
+
+Mock::RSpec::Example = Struct.new :name, :metadata, :block
+
+Mock::RSpec::ExampleGroup = Struct.new :name, :metadata do
+  def examples
+    @examples ||= []
+  end
+
+  def example(name, metadata, &block)
+    Example.new name, metadata, block
+  end
+end

data/test/test_mrspec.rb

@@ -0,0 +1,172 @@
+require 'minitest/spec'
+require 'support/helper'
+require 'support/mock'
+
+
+# Just wrote down the behaviour,
+# but as of right now, it's not worth the effort of writing all of them,
+# the cukes test all this behaviour, already
+
+class TestMRspec < Minitest::Spec
+  include ::Mock
+
+  describe 'default files and patterns' do
+    it 'looks in the test and spec directories'
+    it 'finds files that end in _spec.rb, recursively'
+    it 'finds files that end in _test.rb, recursively'
+    it 'finds files that begin with test_ and end with .rb, recursively'
+  end
+
+  describe 'registering tests' do
+    it 'registers Minitest::Test tests with RSpec, using the class name' do
+      test1 = a_test_named 'First'
+      test2 = a_test_named 'Second'
+      MRspec::DeclareMinitests.wrap_classes mock_rspec, [test1, test2]
+      assert_equal ['First', 'Second'], mock_rspec.group_names
+    end
+
+    it 'registers Minitest::Spec tests with RSpec, using the spec description' do
+      spec1 = a_spec_named 'spec 1'
+      spec2 = a_spec_named 'spec 2'
+      MRspec::DeclareMinitests.wrap_classes mock_rspec, [test1, test2]
+      assert_equal ['spec 1', 'spec 2'], mock_rspec.group_names
+    end
+
+    describe 'descriptions' do
+      def description_for(class_name)
+        MRspec::DeclareMinitests.group_name a_test_named(class_name)
+      end
+
+      it 'removes leading `Test` in the class name, from the description' do
+        assert_equal 'ClassName', description_for('ClassName')
+        assert_equal 'ClassName', description_for('TestClassName')
+      end
+
+      it 'removes trailing `Test` in the class name, from the description' do
+        assert_equal 'ClassName', description_for('ClassName')
+        assert_equal 'ClassName', description_for('ClassNameTest')
+      end
+
+      it 'can deals with anonymous classes (nil class name) by using their to_s' do
+        klass1       = a_test_named nil
+        description1 = MRspec::DeclareMinitests.group_name klass1
+
+        klass2       = a_test_named nil
+        description2 = MRspec::DeclareMinitests.group_name klass2
+
+        assert_match /^Anonymous Minitest for class #<Class:0x/, description1
+
+        # Just double checking it's bypassing this code that makes them all have the same name:
+        # https://github.com/seattlerb/minitest/blob/f1081566ec6e9e391628bde3a26fb057ad2576a8/lib/minitest/assertions.rb#L118
+        refute_equal description1, description2
+      end
+
+      it 'can deal with symol or string names' do
+        assert_equal 'ClassName', description_for('ClassName')
+        assert_equal 'ClassName', description_for(:ClassName)
+      end
+    end
+
+    describe 'example names' do
+      def example_name_for(method_name)
+        MRspec::DeclareMinitests.example_name method_name
+      end
+
+      it 'removes leading `test_` in the method name, from the test name' do
+        assert_equal 'methodname', example_name_for('methodname')
+        assert_equal 'methodname', example_name_for('test_methodname')
+      end
+
+      it 'removes leading `test_nnnn_` in the method name, from the test name' do
+        assert_equal 'methodname', example_name_for('methodname')
+        assert_equal 'methodname', example_name_for('test_0000_methodname')
+        assert_equal '000 methodname', example_name_for('test_000_methodname')
+      end
+
+      it 'translates underscores to spaces' do
+        assert_equal 'a method name', example_name_for('a_method_name')
+      end
+
+      it 'can deal with string or symbol names' do
+        assert_equal 'methodname', example_name_for('methodname')
+        assert_equal 'methodname', example_name_for(:methodname)
+      end
+    end
+
+    describe 'metadata' do
+      it 'aggregates metadata on the class with classmeta' do
+        klass = a_test_named('a') { classmeta a: true }
+        assert_equal({a: true}, klass.class_metadata)
+      end
+
+      it 'allows for multiple metadata keys to be provided in one classmeta call' do
+        klass = a_test_named('a') { classmeta a: true, b: true }
+        assert_equal({a: true, b: true}, klass.class_metadata)
+      end
+
+      it 'aggregates multiple calls to classmeta' do
+        klass = a_test_named 'a' do
+          classmeta a: true
+          classmeta b: true
+        end
+        assert_equal({a: true, b: true}, klass.class_metadata)
+      end
+
+      it 'aggregates metadata on the next test to be defined, with meta' do
+        klass = a_test_named 'a' do
+          meta a: true
+          def test_a; end
+
+          def test_b; end
+
+          meta c: true
+          def test_c; end
+        end
+
+        assert_equal({a: true}, klass.example_metadata[:test_a])
+        assert_equal({},        klass.example_metadata[:test_b])
+        assert_equal({c: true}, klass.example_metadata[:test_c])
+      end
+
+      it 'allows for multiple metadata keys to be provided in one meta call' do
+        klass = a_test_named 'a' do
+          meta a: true, b: true
+          def test_a; end
+        end
+        assert_equal({a: true, b: true}, klass.example_metadata[:test_a])
+      end
+
+      it 'aggregates multiple calls to meta' do
+        klass = a_test_named 'a' do
+          meta a: true
+          meta b: true
+          def test_a; end
+        end
+        assert_equal({a: true, b: true}, klass.example_metadata[:test_a])
+      end
+    end
+  end
+
+  describe 'recording tests' do
+    it 'records minitest errors as failures, and displays the message and the class'
+    it 'records minitest failed assertions as failures, and displays the message, but not the class'
+    it 'records rspec errors as failures, and displays the message, and the class'
+    it 'records rspec failed assertions as failures, and displays the message and the class'
+    it 'omits minitest code from the backtrace'
+    it 'omits rspec code from the backtrace'
+    it 'omits mrspec code from the backtrace'
+  end
+
+  describe 'identifying which test to run' do
+    it 'matches the -e flag against Minitest tests'
+    it 'overrides the default filenames, when one is provided'
+  end
+
+  describe 'toplevel `describe`' do
+    it 'comes from Minitest::Spec' do
+      filename, _linenum = TOPLEVEL_BINDING.method(:describe).source_location
+      assert_match /minitest/, filename
+      refute_match /rspec/,    filename
+    end
+  end
+end

data/test/test_parser_monkey_patches.rb

@@ -0,0 +1,93 @@
+require 'minitest/spec'
+require 'support/helper'
+
+class TestParserMonkeyPatches < Minitest::Spec
+  Parser = RSpec::Core::Parser
+
+  def rspec_parser
+    Parser.instance_method :rspec_parser
+  end
+
+  def mrspec_parser
+    Parser.instance_method :mrspec_parser
+  end
+
+  it 'can get the original rspec parser with #rspec_parser' do
+    filename, _linenum = rspec_parser.source_location
+    assert_includes filename, '/lib/rspec/core/'
+    refute_includes filename, '/lib/mrspec/'
+  end
+
+  it 'has an overridden parser with #mrspec_parser' do
+    mrspec_parser = Parser.instance_method :mrspec_parser
+    filename, _linenum = mrspec_parser.source_location
+    refute_includes filename, '/lib/rspec/core/'
+    assert_includes filename, '/lib/mrspec/'
+  end
+
+  describe '#mrspec_parser' do
+    def record_hostile_parsing(option_parser, flag)
+      stdout, stderr, *rest = capture_io do
+        begin option_parser.parse([flag])
+        rescue SystemExit
+        end
+      end
+      assert_empty rest
+      assert_empty stderr
+      stdout
+    end
+
+    it 'returns the original #rspec_parser' do
+      # just showing that it does RSpec parsery things
+      options = {}
+      Parser.new.mrspec_parser(options).parse(['-I', 'somepath'])
+      assert_equal options[:libs], ['somepath']
+    end
+
+    it 'modifies the description to replace uses of rspec with uses of mrpspec' do
+      assert_match /\bmrspec\b/, Parser.new.mrspec_parser({}).banner
+      refute_match /\brspec\b/,  Parser.new.mrspec_parser({}).banner
+    end
+
+    it 'overrides -v and --version includes the Mrspec version, the RSpec::Core version, and the Minitest version' do
+      rspec_version  = record_hostile_parsing Parser.new.rspec_parser({}),  '--version'
+      rspec_v        = record_hostile_parsing Parser.new.rspec_parser({}),  '-v'
+      mrspec_version = record_hostile_parsing Parser.new.mrspec_parser({}), '--version'
+      mrspec_v       = record_hostile_parsing Parser.new.mrspec_parser({}), '-v'
+
+      # RSpec version parser defines both of these flags to return its version
+      assert_equal rspec_version, rspec_v
+      assert_equal RSpec::Core::Version::STRING, rspec_version.chomp
+
+      # MRspec overrides both of these flags to print versions of all relevant libs
+      expected = "mrspec     #{MRspec::VERSION}\n"\
+                 "rspec-core #{RSpec::Core::Version::STRING}\n"\
+                 "minitest   #{Minitest::VERSION}\n"
+      assert_equal mrspec_version, mrspec_v
+      assert_equal expected, mrspec_version
+    end
+
+    # Giving up on making sure these are equivalent, it's not the end of the world if they aren't
+    # I'm basically at a point where I think that no one should use OptionParser
+    it 'sets the correct description for the versions'
+  end
+
+  it 'stores the current parser in .parser_method' do
+    Parser.parser_method = rspec_parser
+    assert_equal Parser.parser_method, rspec_parser
+    refute_equal Parser.parser_method, mrspec_parser
+
+    Parser.parser_method = mrspec_parser
+    refute_equal Parser.parser_method, rspec_parser
+    assert_equal Parser.parser_method, mrspec_parser
+  end
+
+  it 'redefines #parser to use the parser in .parser_method' do
+    # have to do it a bit roundabout, b/c OptionParser does not override #==, so it uses object equality
+    Parser.parser_method = rspec_parser
+    assert_match /\brspec\b/, Parser.new.parser({}).banner
+
+    Parser.parser_method = mrspec_parser
+    assert_match /\bmrspec\b/, Parser.new.parser({}).banner
+  end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mrspec
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.1.0
 platform: ruby
 authors:
 - Josh Cheek
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-05-20 00:00:00.000000000 Z
+date: 2015-05-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec-core
@@ -99,6 +99,10 @@ files:
 - lib/mrspec/runner.rb
 - lib/mrspec/version.rb
 - mrspec.gemspec
+- test/support/helper.rb
+- test/support/mock.rb
+- test/test_mrspec.rb
+- test/test_parser_monkey_patches.rb
 homepage: https://github.com/JoshCheek/mrspec
 licenses:
 - MIT
@@ -126,4 +130,8 @@ summary: Minitest tests + RSpec's test runner
 test_files:
 - features/mrspec.feature
 - features/support/env.rb
+- test/support/helper.rb
+- test/support/mock.rb
+- test/test_mrspec.rb
+- test/test_parser_monkey_patches.rb
 has_rdoc: