Fix deprecation warning for minitest 5.3.2
Make it backward compatible
Fix typo in section Usage/color output
Merge pull request #101 from ebouchut/patch-1

Fix typo in section Usage/color output
kern/minitest-reporters#103: Switching from PowerBar to ruby-progressbar

PowerBar seems to be a bit defunct (last updated a year ago, years-old
issues sitting open). But, most importantly, the `ProgressReporter`
makes my tests run 50% slower than any other reporter. That doesn’t
seem right—whatever is being done to generate the progress bar couldn’t
possibly be complicated enough to increase the test run time by 50%.

Since PowerBar is defunct I figured the easiest way is to just switch
to something actively developed, like ruby-progressbar, and that did
the trick. Test run times with the `ProgressReporter` now average the
same as the other reporters.

The output will almost be completely identical. The one change I made
is that now only the progress bar will be colored. Previously the
entire line would be green, and then change to yellow or red if there
was a skip or failure. Now only the progress bar itself will change
color, which makes the output visually easier to read.
Merge pull request #100 from kevintyll/master

Compatibility with newer versions of minitest.  To avoid scary message that wrong file is being required.
Merge pull request #99 from chrisnicola/patch-1

Don't print failure info for skipped tests
Merge pull request #104 from brandonweiss/improving-progress-reporter-performance

kern/minitest-reporters#103: Switching from PowerBar to ruby-progressbar
link to travis updated
Update README.md
Bump version to 1.0.3
.ruby-version should not be under VCS
Fixing ProgressReporter output

The escape code is necessary to erase the remains of the progress bar
after errors are reported.

And it shouldn’t be necessary to put `ENDCODE` any more since the
output is only partially colorized now.
Merge pull request #105 from brandonweiss/improving-progress-reporter-performance

Fixing ProgressReporter output
Do not require autorun

Requiring autorun makes Minitest to run the tests in an `at_exit` block, which
may or may not be what the user wants. This change makes the gem less
opinionated and gives the developer using the gem decide when and how to run the
tests.

Related https://github.com/kern/minitest-reporters/pull/100
Show location of test failures

While exception messages show a the file name/line number where the
exception was thrown, actual test failures (e.g. `refute true`) were
not displaying the location of the exception.

To expose the problem, I ran the bad test gallery with stock minitest
pride output. The __FILE__ and __LINE__ where the failed assert occured
were showing up. However, when I switched to
`Minitest::Reporters::DefaultReporter`, the failure location was gone.

I also added the ability to easily run the galleries with minitest pride
output as a way of testing the formatting of `DefaultReporter` against
stock minitest in the future.
Merge pull request #108 from ntl/show_file_and_line_number_on_failure

Show location of test failures
Merge pull request #107 from antonio/do_not_autorun

Do not require autorun
Pride added to gallery
Versions bumped to 1.0.4