Permalink
Commits on Aug 3, 2012
  1. Fix the specs

    Maher4Ever committed Aug 3, 2012
Commits on Aug 2, 2012
  1. Fix #2 - Add support for Windows

    Maher4Ever committed Aug 2, 2012
Commits on Jun 15, 2012
  1. Release version 0.1.3

    Maher4Ever committed Jun 15, 2012
  2. Add a working submodule

    Maher4Ever committed Jun 15, 2012
  3. Remove broken submodule

    Maher4Ever committed Jun 15, 2012
  4. Update the README

    Maher4Ever committed Jun 15, 2012
  5. Update to Guard v1.1

    Maher4Ever committed Jun 15, 2012
Commits on Jan 26, 2012
  1. Release version 0.1.2

    Maher4Ever committed Jan 26, 2012
  2. Correct fixture name

    Maher4Ever committed Jan 26, 2012
Commits on Jan 3, 2012
  1. Release version 0.1.1

    Maher4Ever committed Jan 3, 2012
  2. Update gems

    Maher4Ever committed Jan 3, 2012
Commits on Nov 30, 2011
  1. Release version 0.1.0

    Maher4Ever committed Nov 30, 2011
  2. Add the all_after_pass option

    When the all_after_pass option is enabled (which it is by default), all the tests
    will be run after a failing test pass. This ensures that the process of makeing
    the test pass didn't break something else.
    Maher4Ever committed Nov 30, 2011
  3. Add the keep_failed option

    When the keep_failed option is enabled, the failed tests are remembered
    and run with every change untill they pass.
    Maher4Ever committed Nov 30, 2011
  4. Refactor the runner

    The 'run' method now checks that the tests could be run and if that's the case,
    it calls the 'run_tests' method which handles the real work.
    Maher4Ever committed Nov 30, 2011
  5. Add a notifier module

    Maher4Ever committed Nov 30, 2011
Commits on Nov 29, 2011
  1. Enhance yardoc generated docs

    Maher4Ever committed Nov 29, 2011
Commits on Nov 27, 2011
Commits on Nov 25, 2011
  1. Release version 0.0.3

    Maher4Ever committed Nov 25, 2011