MinitestVisible

This gem provides some very basic and mostly unobtrusive visibility to the progress of a minitest test run. I have found that on more than one occasion, cut and paste errors have caused my testing to not run as expected. This little gem gives me the warm and fuzzy security blanket of seeing each test's filename as it is run and knowing what version of minitest is in charge without all the chaos of going fully verbose. A sample run follows:

C:\Sites\fOOrth>rake test
Run options: --seed 32173

# Running tests:

MiniTest version = 4.7.5, MinitestVisible version = 0.0.1

Running test file: array_test.rb
.
Running test file: complex_test.rb
.
Running test file: context_tests.rb
........
Running test file: core_tests.rb
.........
Running test file: ctrl_stack_tests.rb
.
Running test file: data_stack_tests.rb
.....
Running test file: file_source_tests.rb
....
Running test file: hash_test.rb
.
Running test file: numeric_test.rb
..........
Running test file: object_test.rb
...........
Running test file: parser_tests.rb
........
Running test file: rational_test.rb
.
Running test file: string_test.rb
...
Running test file: string_source_tests.rb
....
Running test file: symbol_map_tests.rb
...

Finished tests in 0.038003s, 1841.9598 tests/s, 11683.2882 assertions/s.

70 tests, 444 assertions, 0 failures, 0 errors, 0 skips

Installation

Add this line to your application's Gemfile:

gem 'minitest_visible'

And then execute:

$ bundle

Or install it yourself as:

$ gem install minitest_visible

Usage

Simply add the line:

require 'minitest_visible'

Then, in the body of your test class add:

MinitestVisible.track self, __FILE__

That is all that is needed. Test output will now be decorated as shown above.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request