Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on May 5, 2015
  1. @zamith
  2. @zamith

    No need to bundle install in travis

    zamith authored
    All the required gems to run the test should be required by the
    appraisals gemfiles
  3. @zamith

    Use require instead of load for small performance gain

    zamith authored
    * Require allocates much less strigs in memory, and has the advantage
    that it will only require the same file once (it should never be a
    problem, as each run will wipe this cache)
    * Improves benchmark outputs so it has the commit SHA when it was run,
    for future reference
    * Adds allocation test
Commits on May 2, 2015
  1. @zamith

    Bumps to version 1.3.4

    zamith authored
  2. @zamith
Commits on Apr 30, 2015
  1. @zamith

    Refactors runner into separate classes

    zamith authored
    Adds more benchmarks, and stores results in a benchmarks directory, so
    that they can be compared over time.
Commits on Apr 29, 2015
  1. @zamith

    Corrects travis build

    zamith authored
  2. @zamith
  3. @zamith
Commits on Apr 28, 2015
  1. @zamith
Commits on Apr 27, 2015
  1. @zamith

    Add Minitest 5 tests to the CI

    zamith authored
  2. @zamith

    Drop Ruby 1.9.3 and add 2.2.0

    zamith authored
    Ruby 1.9.3 has been EOLed
    (, and thus support for it will no longer be given by M.
  3. @zamith

    Add ruby 2.2 support on the test

    zamith authored
    The tests were assuming that test unit was present on the stdlib, which
    as of Ruby 2.2 is no longer true
Commits on Apr 26, 2015
  1. @zamith

    Updates some gems

    zamith authored
  2. @zamith

    Extract a strategy for each supported framework into a proper file

    zamith authored
    This is a refactor that should not affect any public facing methods.
    Handling different frameworks (or different versions of the same
    framework) was becoming messy really fast. The conditionals for each of
    them were scattered through the code. Thus, the solution was to use the
    strategy pattern (almost), and abstract the differences into what I
    called a runner.
    The different runners could not be injected into the initializer as a
    dependency, because at that point the testing framework is not yet
    loaded, which means there is no way of knowing what runner to use. So,
    it is lazy loaded, and only calculated when it is first used.
    Removed the main Runner class from the M module file, in order to make it
    simpler and easier to understand and reason about.
    The framework runner class now uses instance methods instead of class
    methods, mostly because of a personal preference, but also because I
    feel it instance methods are more flexible, and easier to change.
  3. @zamith
  4. @zamith

    Merge branch 'warning-free' of git:// into t…

    zamith authored
  5. @zamith

    Merge branch 'travis-new-ruby' of git:// into…

    zamith authored
    … duggiefresh-travis-new-ruby
Commits on Apr 24, 2015
  1. @zamith

    Bumping to version 1.3.3

    zamith authored
Commits on Sep 6, 2014
  1. @teoljungberg
  2. @teoljungberg
  3. @teoljungberg
Commits on Apr 4, 2014
  1. @duggiefresh

    Add Ruby 2.1.0 to Travis

    duggiefresh authored
Commits on Mar 21, 2014
  1. @zamith
  2. @zamith

    Corrects indentation

    zamith authored
  3. @zamith

    Reverts indentation changes

    zamith authored
  4. @zamith
  5. @zamith

    Support for Minitest 5

    zamith authored
    Uses Appraisal in order to test the different versions of minitest. The
    entire test suite will not run with minitest 5, since ruby relies on
    `Minitest::Unit::TestCase`, which was deprecated.
    Also, the previous solution was flawed since the `Minitest` constant was
    defined in minitest 4 as an alias to `MiniTest`, therefore I also check
    for the version number (`Minitest::Unit::VERSION`).
    I extracted the logic of checking which framework is loaded to a
    separate class, `M::Frameworks`, so it can be checked them on both the
    tests and the library code.
Commits on Mar 10, 2014
  1. @unmanbearpig
Commits on Dec 6, 2013
  1. @tristandunn

    Regexp.escape test names.

    tristandunn authored
  2. @maxidr @tristandunn

    It runs more than one method when names start equals

    maxidr authored tristandunn committed
Commits on Dec 5, 2013
  1. @tristandunn

    Add Coveralls back.

    tristandunn authored
    Fixes #33.
  2. @tristandunn

    Test 2.0.0 on Travis too.

    tristandunn authored
Commits on Jun 11, 2013
  1. @bcardarella

    Support completely empty test classes

    bcardarella authored
    In the case of an empty test class similar to:
    class SomeTest < Test::Unit::TestCase
    `m` was bombing out because `exit!` expects a non-nil value. The
    `Runner#run` method was only returning values in the case of tests that
    were found or tests not found within a file that does have tests. The
    third case of no tests at all was not being covered and would result in
    a `nil` being returned.
Commits on May 20, 2013
  1. Merge pull request #32 from krainboltgreene/patch-1

    Website looks terrible now, readme had no real information
Something went wrong with that request. Please try again.