minitap 0.5.2 → 0.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3287678f9370253212c9674659d5e2cb9b316511
-  data.tar.gz: 04e448c48c2bdd11d00df0bcc2eff1006fd72766
+  metadata.gz: 411e52de16d0efd7ca361002439076792e8b6ec0
+  data.tar.gz: b21a983ac1758be81486b6131e46596894ad12ae
 SHA512:
-  metadata.gz: 486e83b77907a254da1eedd730adc379ec92369fb03437b99d7b8d31aed2bf0f5d4d25930f5bd833767f762be3ed34f6abf623daa351e6b320e59b1f4ae38b7f
-  data.tar.gz: 505ea556923d93696cfa2f03a53fa942bad75a1c8d60f3602f010dce7f00478677bd7bd1386bc58639f2f6aba38060b67d21b2e4dbd2066e8f60b17902e9a7f6
+  metadata.gz: 8c60e2728c098add4be85933e0c0886233d4f8d6fa893eff08c69ca02b59124515ae8b14b13ebcbc50054feb99fcf314b2600332b1a7b43a0064761a242736ae
+  data.tar.gz: 5658499aeaf41290d62b421720153548ed4433933a54353e5176cfdd17f0bf899e39d24cd86c53c04d6e05bf679b50d093384475bd1558f2e1acbd5083aaeea4

data/.index

@@ -62,5 +62,5 @@ title: MiniTap
 summary: TAP-Y/J reporters for MiniTest
 description: MiniTap provides a MiniTest TAP-Y/J report format suitable for use with
   TAPOUT.
-version: 0.5.2
-date: '2013-11-18'
+version: 0.5.3
+date: '2013-11-20'

data/HISTORY.md

@@ -1,5 +1,16 @@
 # RELEASE HISTORY
 
+## 0.5.3 | 2013-11-20
+
+Small change made to ensure that output i/o is un sync mode.
+This prevents test results fro being buffered over the pipe
+
+Changes:
+
+* Add `io.sync = true` *after* Minitest reporter class is initialized.
+* Add notes to README about use tapout's pause and resume feature.
+
+
 ## 0.5.2 | 2013-11-18
 
 This release makes it possible to specify reporters in code

data/README.md

@@ -113,6 +113,33 @@ Then pipe the output to the `tapout` command, e.g.
     $ rpt=tapy ruby test/some_test.rb | tapout progressbar
 
 
+# Using Pry & Other Tools
+
+Becuase Tapout communicates with Minitest via a shell pipe it is improtant
+to keep in mind that any non TAP-Y/J output that tapout receives might 
+force it to halt. To ensure this doesn't occur a *pause code* (`16.chr`) can
+be sent over the pipe to instruct the tapout comamnd to stop processing test
+results and route `$stdin` directly to `$stdout` instead. A *resume code*
+(`23.chr`) can be sent to restart test result processing.
+
+A good example of this is when using `binding.pry` for debugging. To do so
+while using tapout:
+
+    require 'tapout/utility'
+    tapout.pause{ binding.pry }
+
+Or, even more convenient, specifically for use with pry:
+
+    require 'tapout/utility'
+    tapout.pry(binding)
+
+Which is a more covenient way of coding:
+
+    STDOUT.puts 16.chr
+    binding.pry
+    STDOUT.puts 23.chr
+
+
 # Copying
 
 Copyright (c) 2011 Rubyworks

data/lib/minitap/minitest5.rb

@@ -41,6 +41,9 @@ module Minitest
 
       super(io, options)
 
+      # since tapout uses a unix pipe, we don't want any buffering
+      io.sync = true
+
       #@_stdout = StringIO.new
       #@_stderr = StringIO.new
 
@@ -876,7 +879,6 @@ module Minitest
 
     def wp(str)
       io.puts(str)
-      #STDOUT.puts(str)
     end
   end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: minitap
 version: !ruby/object:Gem::Version
-  version: 0.5.2
+  version: 0.5.3
 platform: ruby
 authors:
 - trans
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-11-18 00:00:00.000000000 Z
+date: 2013-11-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: tapout