turn-again-reporter 0.0.2 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 33527d89ec72f5cab5ddb42dd34f6c75f64af807
-  data.tar.gz: f326a8167830748b581b51aabdec1f4a251729b9
+  metadata.gz: 968225fdfcb2e87c69f9b310bc938426610398b4
+  data.tar.gz: 4ad55c5b840f8ef438439255dc66aec7aea0f872
 SHA512:
-  metadata.gz: 93a8d5dbc9c57c102f80c5d37134d423cc9b35408574b73e5ba7db62db84b772ce2045a9e9407325de7a0f9989f0e8fbe220515737cb674c1096d8779a071e58
-  data.tar.gz: cdadfbb9c3872d81b3381280c9e21b4714ae78011ebcde8de290d44ed41ce768b193a4fbb38e6bda3dc24e857c201511281eead48d66b995482d1f2b627a070a
+  metadata.gz: 7d68946da7fe2038a2a4385856fec784cece4e802a3894272fbf101d2011cae7f64dd6f2b290e4aae911d0208d01d2067ffee878ec72e2604d602e49683a89ed
+  data.tar.gz: 0cc1564a0aff0f1a55f11af77b0fe7e8d0f9eb75575e2c126598869e29851992454a2c179bb512061840554f0488b49f0fa6d3b63c52a20e58eabfb5ee5bad0e

data/.gitignore

@@ -12,3 +12,4 @@
 *.o
 *.a
 mkmf.log
+*.gem

data/README.md

@@ -1,31 +1,61 @@
-# Turn::Again::Reporter
+# A Turn-like Minitest Reporter (Again)
 
-TODO: Write a gem description
+One of my favorite aspects of the now-abandoned [turn gem](https://github.com/turn-project/turn)'s was how the status banners for each test (i.e. PASS, FAIL, ERROR, SKIP) lined up nicely on the right side, providing a comfy, at-a-glance view.
 
-## Installation
+These days I'm using the [minitest-reporters](https://github.com/kern/minitest-reporters) gem everywhere, but I've felt a little picky about the SpecReporter's claims to be "Turn-like". Also, placing the status banners on the right side, after each test, has the undesirable effect of limiting the length of my test names.
+
+**Q: Do I really need tests with 60-character names?**
+*A: Yes, sometimes. And it's none of your business!*
+
+This might be better off included in the minitest-reporters gem itself, but it varies so minimally/cosmetically from its parent that I can't bring myself to bother the wonderful [Alex Kern](https://github.com/kern) about it with a pull request. It's really just an easy way for me to spread this code across all my projects without copy-pasting it. If someone else out there enjoys this formatting, I'm glad to hear it.
 
-Add this line to your application's Gemfile:
+## Usage and Features (so-called)
+
+In your `test_helper.rb` file, or equivalent where you `require 'minitest-reporters'`, just follow it up with:
 
 ```ruby
-gem 'turn-again-reporter'
+require 'minitest/reporters'
+
+Minitest::Reporters.use! Minitest::Reporters::TurnAgainReporter.new
+```
+
+TurnAgainReporter's initializer will pass on all existing Minitest::Reporters::Base keyword argments, such as `color: true` but uses two of its own for some customization:
+
+  1. The `indent` keyword can specify the indentation from the left of the console when running. The default is 4 to faithfully mimic turn itself.
+  2. *Unlike turn*, the duration measurements in next to the test status do not include hours, because the vast majority of tests do not require a whole hour for a single test case. However, hours can be re-enabled by passing the `:hours` keyword as `true`.
+
+An example of these options:
+
+```ruby
+
+Minitest::Reporters.use!(
+  Minitest::Reporters::TurnAgainReporter.new(
+    color: true, hours: true, indent: 2
+  ))
 ```
 
-And then execute:
+## Installation
 
-    $ bundle
+The usual gem installation applies:
 
-Or install it yourself as:
+```ruby
+gem install 'turn-again-reporter'
+```
 
-    $ gem install turn-again-reporter
+Or in your Gemfile:
 
-## Usage
+```ruby
+gem 'turn-again-reporter'
+```
 
-TODO: Write usage instructions here
+and run
+
+```bash
+$ bundle install
+```
 
 ## Contributing
 
-1. Fork it ( https://github.com/[my-github-username]/turn-again-reporter/fork )
-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 a new Pull Request
+Fork away, but I can't imaginee there's much to contribute.
+
+That said, I would be interested to see how one might test the output of a test library? Play with redirecting STDOUT and write a few test cases for Fixnum or something? I would normally shy away from releasing untested code, but *honestly?!* This gem is just two `sprintf` statements and a re-arrangement of `puts` statements.

data/lib/version.rb

@@ -4,7 +4,7 @@ require "minitest/reporters/turn_again_reporter"
 module Minitest
   module Reporters
     class TurnAgainReporter
-      VERSION = "0.0.2"
+      VERSION = "1.0.0"
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: turn-again-reporter
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 1.0.0
 platform: ruby
 authors:
 - Paul Kwiatkowski
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-03-28 00:00:00.000000000 Z
+date: 2015-03-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -76,7 +76,6 @@ files:
 - Rakefile
 - lib/minitest/reporters/turn_again_reporter.rb
 - lib/version.rb
-- turn-again-reporter-0.0.1.gem
 - turn-again-reporter.gemspec
 homepage: https://github.com/swifthand/turn-again-reporter
 licenses: