<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

  

  <id>http://blog.zenspider.com/</id>
  <title>Polishing Ruby + Software Releases - zenspider.com</title>
  <updated>2013-05-20T15:46:03-07:00</updated>

  <author>
    <name>ryan davis</name>
    <email>ryand-ruby@zenspider.com</email>
  </author>

  <link href="http://blog.zenspider.com/atom.xml" rel="self"/>
  <link href="http://blog.zenspider.com/"/>

  <rights> © ryan davis - ryand-ruby@zenspider.com </rights>

  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-2-has-been-released.html</id>
      <title>minitest version 5.0.2 has been released!</title>
      <updated>2013-05-20T15:46:03-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-2-has-been-released.html"/>

      <published>2013-05-20T15:46:03-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;5.0.2 / 2013-05-20&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;3 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Gem.find_files is smarter than I remember&amp;hellip; cause I wrote it that way. &lt;em&gt;sigh&lt;/em&gt; I&amp;rsquo;m getting old.&lt;/li&gt;
      &lt;li&gt;Pride wasn&amp;rsquo;t doing puts through its #io. (tmiller/tenderlove)&lt;/li&gt;
      &lt;li&gt;Replaced Runnable#dup and Test#dup with marshal_dump/load. Too many problems cropping up on untested rails code. (tenderlove/rubys)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-1-has-been-released.html</id>
      <title>minitest version 5.0.1 has been released!</title>
      <updated>2013-05-14T17:15:45-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-1-has-been-released.html"/>

      <published>2013-05-14T17:15:45-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;5.0.1 / 2013-05-14&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Documented Assertions&amp;rsquo; need for @assertions to be defined by the includer.&lt;/li&gt;
      &lt;li&gt;Only load one plugin version per name. Tries for latest.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-happy-version-1-0-0-has-been-released.html</id>
      <title>minitest-happy version 1.0.0 has been released!</title>
      <updated>2013-05-10T16:49:02-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-happy-version-1-0-0-has-been-released.html"/>

      <published>2013-05-10T16:49:02-07:00</published>
      <content type="html">&lt;p&gt;All pride, all the time!&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.0 / 2013-04-24&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 major enhancement&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Birthday!&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest-happy&quot;&gt;https://github.com/seattlerb/minitest-happy&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest-happy&quot;&gt;http://docs.seattlerb.org/minitest-happy&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/flog-version-4-1-0-has-been-released.html</id>
      <title>flog version 4.1.0 has been released!</title>
      <updated>2013-05-10T16:45:49-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/flog-version-4-1-0-has-been-released.html"/>

      <published>2013-05-10T16:45:49-07:00</published>
      <content type="html">&lt;p&gt;Flog reports the most tortured code in an easy to read pain
report. The higher the score, the more pain the code is in.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.1.0 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;3 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Cleaned up tests by adding assert_hash_in_epsilon. yay!&lt;/li&gt;
      &lt;li&gt;Fixed method_location is now cleared on #reset. (makaroni4)&lt;/li&gt;
      &lt;li&gt;to_proc_normal is now penalized based on RUBY_VERSION. Scores were benchmarked.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed code/home urls in readme/gem.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/flog&quot;&gt;http://seattlerb.rubyforge.org/flog&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://ruby.sadi.st/&quot;&gt;http://ruby.sadi.st/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;code: &lt;a href=&quot;https://github.com/seattlerb/flog&quot;&gt;https://github.com/seattlerb/flog&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/flay-version-2-3-0-has-been-released.html</id>
      <title>flay version 2.3.0 has been released!</title>
      <updated>2013-05-10T16:43:52-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/flay-version-2-3-0-has-been-released.html"/>

      <published>2013-05-10T16:43:52-07:00</published>
      <content type="html">&lt;p&gt;Flay analyzes code for structural similarities. Differences in literal
values, variable, class, method names, whitespace, programming style,
braces vs do/end, etc are all ignored. Making this totally rad.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;2.3.0 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Refactored n_way_diff into split_and_group, collapse_and_label, and pad_with_empty_strings.&lt;/li&gt;
      &lt;li&gt;n_way_diff now does leading comments separately from the code, to better align diffs.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed code/home urls in readme/gem.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/flay&quot;&gt;http://seattlerb.rubyforge.org/flay&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;code: &lt;a href=&quot;https://github.com/seattlerb/flay&quot;&gt;https://github.com/seattlerb/flay&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://ruby.sadi.st/&quot;&gt;http://ruby.sadi.st/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-bacon-version-1-0-0-has-been-released.html</id>
      <title>minitest-bacon version 1.0.0 has been released!</title>
      <updated>2013-05-10T16:30:47-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-bacon-version-1-0-0-has-been-released.html"/>

      <published>2013-05-10T16:30:47-07:00</published>
      <content type="html">&lt;p&gt;minitest-bacon extends minitest with bacon-like functionality. It
should allow you to bridge 90+% of your bacon specs over to minitest.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.0 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 major enhancement&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Birthday!&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest-bacon&quot;&gt;https://github.com/seattlerb/minitest-bacon&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest-bacon&quot;&gt;http://docs.seattlerb.org/minitest-bacon&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/vlad-version-2-5-0-has-been-released.html</id>
      <title>vlad version 2.5.0 has been released!</title>
      <updated>2013-05-10T16:25:31-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/vlad-version-2-5-0-has-been-released.html"/>

      <published>2013-05-10T16:25:31-07:00</published>
      <content type="html">&lt;p&gt;Vlad the Deployer is pragmatic application deployment automation,
without mercy. Much like Capistrano, but with 1/10th the
complexity. Vlad integrates seamlessly with Rake, and uses familiar
and standard tools like ssh and rsync.&lt;/p&gt;

&lt;p&gt;Impale your application on the heartless spike of the Deployer.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;2.5.0 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 minor enhancement:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Silo vlad:cleanup and vlad:rollback to app role. (contentfree)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed code/home urls in readme/gem.&lt;/li&gt;
      &lt;li&gt;Fixed problem with &amp;lsquo;revisions variable or method not found&amp;rsquo;. (bitboxer/jleo3)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;code: &lt;a href=&quot;https://github.com/seattlerb/vlad&quot;&gt;https://github.com/seattlerb/vlad&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://rubyhitsquad.com/&quot;&gt;http://rubyhitsquad.com/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://hitsquad.rubyforge.org/vlad&quot;&gt;http://hitsquad.rubyforge.org/vlad&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/graph-version-2-5-3-has-been-released.html</id>
      <title>graph version 2.5.3 has been released!</title>
      <updated>2013-05-10T16:23:29-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/graph-version-2-5-3-has-been-released.html"/>

      <published>2013-05-10T16:23:29-07:00</published>
      <content type="html">&lt;p&gt;Graph is a type of hash that outputs in graphviz&amp;rsquo;s dot format. It
comes with a command-line interface that is easily pluggable.&lt;/p&gt;

&lt;p&gt;It ships with plugins to graph dependencies and status of installed
rubygems, rake tasks, homebrew ports, mac ports, and freebsd ports,
coloring leaf nodes blue, outdated nodes red, and outdated leaf nodes
purple (red+blue).&lt;/p&gt;

&lt;p&gt;OSX quick tip: &lt;/p&gt;

&lt;pre&gt;&lt;code&gt;% sudo gem install graph
% sudo brew install graphviz
% gem unpack graph
% cd graph*
% rake gallery
% open gallery/*.png
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;2.5.3 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added &amp;lt;&amp;gt; quoted labels.&lt;/li&gt;
      &lt;li&gt;Added Graph.escape_label.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed issue with labels not escaping double quotes. (tenderlove)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;home: &lt;a href=&quot;https://github.com/seattlerb/graph&quot;&gt;https://github.com/seattlerb/graph&lt;/a&gt;&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/hoe-seattlerb-version-1-3-1-has-been-released.html</id>
      <title>hoe-seattlerb version 1.3.1 has been released!</title>
      <updated>2013-05-10T16:21:00-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/hoe-seattlerb-version-1-3-1-has-been-released.html"/>

      <published>2013-05-10T16:21:00-07:00</published>
      <content type="html">&lt;p&gt;Hoe plugins providing tasks used by seattle.rb including minitest,
perforce, and email providing full front-to-back release/annouce
automation.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.3.1 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Make perforce releases more resilient to working on different branch dirs&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/hoe-seattlerb&quot;&gt;https://github.com/seattlerb/hoe-seattlerb&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe-seattlerb&quot;&gt;http://seattlerb.rubyforge.org/hoe-seattlerb&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/omnifocus-github-version-1-5-0-has-been-released.html</id>
      <title>omnifocus-github version 1.5.0 has been released!</title>
      <updated>2013-05-10T16:17:35-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/omnifocus-github-version-1-5-0-has-been-released.html"/>

      <published>2013-05-10T16:17:35-07:00</published>
      <content type="html">&lt;p&gt;Plugin for omnifocus gem to provide github BTS synchronization.&lt;/p&gt;

&lt;p&gt;Support for Github Enterprise:&lt;/p&gt;

&lt;p&gt;In your git config, set the key omnifocus-github.accounts to a space
separated list of github accounts. &lt;/p&gt;

&lt;pre&gt;&lt;code&gt;git config --global omnifocus-github.accounts &quot;github myghe&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;For each account API end point and authentication information are
should be stored in the git config under a key matching the
account. For example:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;git config --global github.user me
git config --global github.password mypassword
git config --global myghe.api https://ghe.mydomain.com/api/v3
git config --global myghe.token 1a2b3c4d5e6f7e8d
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;For each account can you specify the following parameters:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;api - specify an API endpoint other than
https://api.github.com. This is so you can point this at your Github
Enterprise endpoint.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;user, password - A username and password pair for Basic http authentication.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;token - An OAuth bearer token for OAuth workflows.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If both a token and a username and password are supplied, the token
is used.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.5.0 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 major enhancement:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Remove support for github api tokens (no longer supported by github)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;3 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;add user-agent to api requests (required by github)&lt;/li&gt;
      &lt;li&gt;display error message if trying to authenticate without user/pass&lt;/li&gt;
      &lt;li&gt;remove debugging output&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/omnifocus-github&quot;&gt;https://github.com/seattlerb/omnifocus-github&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/omnifocus-github&quot;&gt;http://seattlerb.rubyforge.org/omnifocus-github&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/hoe-version-3-6-1-has-been-released.html</id>
      <title>hoe version 3.6.1 has been released!</title>
      <updated>2013-05-10T16:06:19-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/hoe-version-3-6-1-has-been-released.html"/>

      <published>2013-05-10T16:06:19-07:00</published>
      <content type="html">&lt;p&gt;Hoe is a rake/rubygems helper for project Rakefiles. It helps you
manage, maintain, and release your project and includes a dynamic
plug-in system allowing for easy extensibility. Hoe ships with
plug-ins for all your usual project tasks including rdoc generation,
testing, packaging, deployment, and announcement..&lt;/p&gt;

&lt;p&gt;See class rdoc for help. Hint: &lt;code&gt;ri Hoe&lt;/code&gt; or any of the plugins listed
below.&lt;/p&gt;

&lt;p&gt;For extra goodness, see: http://seattlerb.rubyforge.org/hoe/Hoe.pdf&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;3.6.1 / 2013-05-10&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Define a blank test task just in case nothing is found&lt;/li&gt;
      &lt;li&gt;Fixed an ancient test to use capture_subprocess_io. More reliable.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;bugs: &lt;a href=&quot;https://github.com/seattlerb/hoe/issues&quot;&gt;https://github.com/seattlerb/hoe/issues&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;code: &lt;a href=&quot;https://github.com/seattlerb/hoe&quot;&gt;https://github.com/seattlerb/hoe&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;other: &lt;a href=&quot;http://github.com/jbarnette/hoe-plugin-examples&quot;&gt;http://github.com/jbarnette/hoe-plugin-examples&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;doco: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe/Hoe.pdf&quot;&gt;http://seattlerb.rubyforge.org/hoe/Hoe.pdf&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe/&quot;&gt;http://seattlerb.rubyforge.org/hoe/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://www.zenspider.com/projects/hoe.html&quot;&gt;http://www.zenspider.com/projects/hoe.html&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-0-has-been-released.html</id>
      <title>minitest version 5.0.0 has been released!</title>
      <updated>2013-05-10T16:02:56-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-version-5-0-0-has-been-released.html"/>

      <published>2013-05-10T16:02:56-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;5.0.0 / 2013-05-10&lt;/h3&gt;

&lt;p&gt;Oh god&amp;hellip; here we go&amp;hellip;&lt;/p&gt;

&lt;p&gt;Minitest 5:&lt;/p&gt;

&lt;p&gt;Deaths in the family:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;MiniTest.runner is dead. No more manager objects.&lt;/li&gt;
  &lt;li&gt;MiniTest::Unit#record is dead. Use a Reporter instance instead.&lt;/li&gt;
  &lt;li&gt;MiniTest::Unit.&lt;em&gt;run&lt;/em&gt;* is dead. Runnable things are responsible for their own runs.&lt;/li&gt;
  &lt;li&gt;MiniTest::Unit.output is dead. No more centralized IO.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Major (oft incompatible) changes:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Renamed MiniTest to Minitest. Your pinkies will thank me. (aliased to MiniTest)&lt;/li&gt;
  &lt;li&gt;Removed MiniTest::Unit entirely. No more manager objects.&lt;/li&gt;
  &lt;li&gt;Added Minitest::Runnable. Everything minitest can run subclasses this.&lt;/li&gt;
  &lt;li&gt;Renamed MiniTest::Unit::TestCase to Minitest::Test (subclassing Runnable).&lt;/li&gt;
  &lt;li&gt;Added Minitest::Benchmark.
    &lt;ul&gt;
      &lt;li&gt;Your benchmarks need to move to their own subclass.&lt;/li&gt;
      &lt;li&gt;Benchmarks using the spec DSL have to have &amp;ldquo;Bench&amp;rdquo; somewhere in their describe.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;MiniTest::Unit.after_tests moved to Minitest.after_tests&lt;/li&gt;
  &lt;li&gt;MiniTest::Unit.autorun is now Minitest.autorun. Just require minitest/autorun pls.&lt;/li&gt;
  &lt;li&gt;Removed ParallelEach#grep since it isn&amp;rsquo;t used anywhere.&lt;/li&gt;
  &lt;li&gt;Renamed Runnable#&lt;strong&gt;name&lt;/strong&gt; to Runnable#name (but uses @NAME internally).&lt;/li&gt;
  &lt;li&gt;Runnable#run needs to return self. Allows for swapping of results as needed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Minor moves:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Moved Assertions module to minitest/assertions.rb&lt;/li&gt;
  &lt;li&gt;Moved Expectations module to minitest/expectations.rb&lt;/li&gt;
  &lt;li&gt;Moved Test to minitest/test.rb&lt;/li&gt;
  &lt;li&gt;Moved everything else in minitest/unit.rb to minitest.rb&lt;/li&gt;
  &lt;li&gt;minitest/unit.rb is now just a small (user-test only) compatibility layer.&lt;/li&gt;
  &lt;li&gt;Moved most of minitest/pride into minitest/pride_plugin.&lt;/li&gt;
  &lt;li&gt;minitest/pride now just activates pride.&lt;/li&gt;
  &lt;li&gt;Moved ParallelEach under Minitest.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Additions:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Added a plugin system that can extend command-line options.&lt;/li&gt;
  &lt;li&gt;Added Minitest.extensions.&lt;/li&gt;
  &lt;li&gt;Added Minitest.reporter (only available during startup).&lt;/li&gt;
  &lt;li&gt;Added Minitest.run(args). This is the very top of any Minitest run.&lt;/li&gt;
  &lt;li&gt;Added Minitest::Reporter. Everything minitest can report goes through here.
    &lt;ul&gt;
      &lt;li&gt;Minitest.reporter is a composite so you can add your own.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Added Minitest::CompositeReporter. Much easier to extend with your own reporters.&lt;/li&gt;
  &lt;li&gt;Added UnexpectedError, an Assertion subclass, to wrap up errors.&lt;/li&gt;
  &lt;li&gt;Minitest::Test#run is now freakin&amp;rsquo; beautiful. 47 -&amp;gt; 17 loc&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Other:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Removed Object.infect_with_assertions (it was already dead code).&lt;/li&gt;
  &lt;li&gt;Runnables are responsible for knowing their result_code (eg &amp;ldquo;.&amp;rdquo; or &amp;ldquo;F&amp;rdquo;).&lt;/li&gt;
  &lt;li&gt;Minitest.autorun now returns boolean, not exit code.&lt;/li&gt;
  &lt;li&gt;Added FAQ entry for extending via modules. (phiggins)&lt;/li&gt;
  &lt;li&gt;Implement Runnable#dup to cleanse state back to test results. Helps with serialization. pair:tenderlove&lt;/li&gt;
  &lt;li&gt;Moved ParallelEach under Minitest.&lt;/li&gt;
  &lt;li&gt;Runnable#run needs to return self. Allows for swapping of results as needed.&lt;/li&gt;
  &lt;li&gt;Minitest.init_plugins passes down options.&lt;/li&gt;
  &lt;li&gt;Minitest.load_plugins only loads once.&lt;/li&gt;
  &lt;li&gt;Fixed minitest/pride to work with rake test loader again. (tmiller)&lt;/li&gt;
  &lt;li&gt;Added count/size to ParallelEach to fix use w/in stdlib&amp;rsquo;s test/unit. :( (btaitelb)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Voodoo:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;Removed mutex from minitest.rb (phiggins)&lt;/li&gt;
  &lt;li&gt;Removed mutex from test.rb (phiggins)&lt;/li&gt;
  &lt;li&gt;Removed Minitest::Reporter.synchronize (phiggins)&lt;/li&gt;
  &lt;li&gt;Removed Minitest::Test.synchronize (phiggins)&lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Upon loading minitest/parallel_each, record, capture_io and capture_subprocess_io are doped with synchronization code. (phiggins)&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/05/minitest-version-4-7-4-has-been-released.html</id>
      <title>minitest version 4.7.4 has been released!</title>
      <updated>2013-05-01T15:42:17-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/05/minitest-version-4-7-4-has-been-released.html"/>

      <published>2013-05-01T15:42:17-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.7.4 / 2013-05-01&lt;/h3&gt;

&lt;p&gt;This is probably the last release of the 4.x series. It will be merged
to ruby and will be put into maintenance mode there.&lt;/p&gt;

&lt;p&gt;I&amp;rsquo;m not set in stone on this, but at this point further development of
minitest (5+) will be gem-only. It is just too hard to work w/in
ruby-core w/ test-unit compatibility holding minitest development
back.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added count/size to ParallelEach to fix use w/in stdlib&amp;rsquo;s test/unit. :( (btaitelb)&lt;/li&gt;
      &lt;li&gt;Allow disabling of info_signal handler in runner. (erikh)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/zenweb-template-version-1-0-1-has-been-released.html</id>
      <title>zenweb-template version 1.0.1 has been released!</title>
      <updated>2013-04-25T16:27:59-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/zenweb-template-version-1-0-1-has-been-released.html"/>

      <published>2013-04-25T16:27:59-07:00</published>
      <content type="html">&lt;p&gt;Simply provides an example zenweb template website.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.1 / 2013-04-25&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed YAML that works in syck but not psych.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/zenweb-template&quot;&gt;https://github.com/seattlerb/zenweb-template&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/zenweb-template&quot;&gt;http://docs.seattlerb.org/zenweb-template&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/ruby2ruby-version-2-0-5-has-been-released.html</id>
      <title>ruby2ruby version 2.0.5 has been released!</title>
      <updated>2013-04-25T16:06:34-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/ruby2ruby-version-2-0-5-has-been-released.html"/>

      <published>2013-04-25T16:06:34-07:00</published>
      <content type="html">&lt;p&gt;ruby2ruby provides a means of generating pure ruby code easily from
RubyParser compatible Sexps. This makes making dynamic language
processors in ruby easier than ever!&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;2.0.5 / 2013-04-25&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed attrasgn w/ multiple keys: a[x, y] = z. (derula)&lt;/li&gt;
      &lt;li&gt;Fixed error w/ attr_* detection when more than 1 ivar/iasgn exist in body.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/ruby2ruby&quot;&gt;http://seattlerb.rubyforge.org/ruby2ruby&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/ruby2ruby&quot;&gt;https://github.com/seattlerb/ruby2ruby&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-macruby-version-1-0-1-has-been-released.html</id>
      <title>minitest-macruby version 1.0.1 has been released!</title>
      <updated>2013-04-22T19:03:58-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-macruby-version-1-0-1-has-been-released.html"/>

      <published>2013-04-22T19:03:58-07:00</published>
      <content type="html">&lt;p&gt;minitest-macruby provides extensions to minitest for macruby UI
testing. It provides a framework to test GUI apps in a live instance.
Documentation and examples are light at the moment as I&amp;rsquo;ve just thrown
this together. Suggestions for extensions are very welcome!&lt;/p&gt;

&lt;p&gt;Currently it provides the following methods in minitest&amp;rsquo;s assertions:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;self.run_macruby_tests&lt;/li&gt;
  &lt;li&gt;find_ui_menu(*path)&lt;/li&gt;
  &lt;li&gt;find_ui_menu_items menu&lt;/li&gt;
  &lt;li&gt;assert_ui_menu menu, *items&lt;/li&gt;
  &lt;li&gt;find_ui_menu_item(*path)&lt;/li&gt;
  &lt;li&gt;assert_ui_action obj, target, action, key = nil&lt;/li&gt;
  &lt;li&gt;assert_ui_binding item, binding_name, target, path&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.1 / 2013-04-22&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed dependency on minitest to 4.x family.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest-macruby&quot;&gt;https://github.com/seattlerb/minitest-macruby&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://bfts.rubyforge.org/minitest-macruby&quot;&gt;http://bfts.rubyforge.org/minitest-macruby&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-excludes-version-1-0-2-has-been-released.html</id>
      <title>minitest-excludes version 1.0.2 has been released!</title>
      <updated>2013-04-22T19:00:23-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-excludes-version-1-0-2-has-been-released.html"/>

      <published>2013-04-22T19:00:23-07:00</published>
      <content type="html">&lt;p&gt;minitest/excludes.rb extends MiniTest::Unit::TestCase to provide a
clean API for excluding certain tests you don&amp;rsquo;t want to run under
certain conditions.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.2 / 2013-04-22&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed dependency on minitest to the 4.x family.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest-excludes&quot;&gt;https://github.com/seattlerb/minitest-excludes&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest-excludes&quot;&gt;http://docs.seattlerb.org/minitest-excludes&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-debugger-version-1-0-1-has-been-released.html</id>
      <title>minitest-debugger version 1.0.1 has been released!</title>
      <updated>2013-04-22T18:56:57-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-debugger-version-1-0-1-has-been-released.html"/>

      <published>2013-04-22T18:56:57-07:00</published>
      <content type="html">&lt;p&gt;This is a stupid simple example of how easy it is to make a minitest
plugin that does something useful. In this case it wraps assert so
that failed assertions will drop into the ruby debugger.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.1 / 2013-04-22&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed minitest dependency to the 4.x family&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest-debugger&quot;&gt;https://github.com/seattlerb/minitest-debugger&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest-debugger&quot;&gt;http://docs.seattlerb.org/minitest-debugger&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-3-has-been-released.html</id>
      <title>minitest version 4.7.3 has been released!</title>
      <updated>2013-04-20T17:59:50-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-3-has-been-released.html"/>

      <published>2013-04-20T17:59:50-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.7.3 / 2013-04-20&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Reverted stubbing of module methods change. Stub the user, not the impl. (ab9/tyabe)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/zenweb-version-3-1-1-has-been-released.html</id>
      <title>zenweb version 3.1.1 has been released!</title>
      <updated>2013-04-18T16:21:04-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/zenweb-version-3-1-1-has-been-released.html"/>

      <published>2013-04-18T16:21:04-07:00</published>
      <content type="html">&lt;p&gt;Zenweb is a set of classes/tools for organizing and formating a
website. It is website oriented rather than webpage oriented, unlike
most rendering tools. It is content oriented, rather than style
oriented, unlike most rendering tools. It uses a rubygems plugin
system to provide a very flexible, and powerful system.&lt;/p&gt;

&lt;p&gt;Zenweb 3 was inspired by jekyll. The filesystem layout is similar to
jekyll&amp;rsquo;s layout, but zenweb isn&amp;rsquo;t focused on blogs. It can do any sort
of website just fine.&lt;/p&gt;

&lt;p&gt;Zenweb uses rake to handle dependencies. As a result, scanning a
website and regenerating incrementally is not just possible, it is
blazingly fast.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;3.1.1 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed description on new_page task. (tenderlove)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/zenweb&quot;&gt;https://github.com/seattlerb/zenweb&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/zenweb&quot;&gt;http://docs.seattlerb.org/zenweb&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;bugs: &lt;a href=&quot;https://github.com/seattlerb/zenweb/issues&quot;&gt;https://github.com/seattlerb/zenweb/issues&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/ZenTest-version-4-9-1-has-been-released.html</id>
      <title>ZenTest version 4.9.1 has been released!</title>
      <updated>2013-04-18T16:19:41-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/ZenTest-version-4-9-1-has-been-released.html"/>

      <published>2013-04-18T16:19:41-07:00</published>
      <content type="html">&lt;p&gt;ZenTest provides 4 different tools: zentest, unit_diff, autotest, and
multiruby.&lt;/p&gt;

&lt;p&gt;zentest scans your target and unit-test code and writes your missing
code based on simple naming rules, enabling XP at a much quicker pace.
zentest only works with Ruby and Minitest or Test::Unit. There is
enough evidence to show that this is still proving useful to users, so
it stays.&lt;/p&gt;

&lt;p&gt;unit_diff is a command-line filter to diff expected results from
actual results and allow you to quickly see exactly what is wrong.
Do note that minitest 2.2+ provides an enhanced assert_equal obviating
the need for unit_diff&lt;/p&gt;

&lt;p&gt;autotest is a continous testing facility meant to be used during
development. As soon as you save a file, autotest will run the
corresponding dependent tests.&lt;/p&gt;

&lt;p&gt;multiruby runs anything you want on multiple versions of ruby. Great
for compatibility checking! Use multiruby_setup to manage your
installed versions.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.9.1 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Make banner more explicit about correct test file location. (rue)&lt;/li&gt;
      &lt;li&gt;Switched to #failed for calculating red/green hook. (bhenderson)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/zentest&quot;&gt;https://github.com/seattlerb/zentest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://zentest.rubyforge.org/ZenTest&quot;&gt;http://zentest.rubyforge.org/ZenTest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/RubyInline-version-3-12-2-has-been-released.html</id>
      <title>RubyInline version 3.12.2 has been released!</title>
      <updated>2013-04-18T16:17:32-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/RubyInline-version-3-12-2-has-been-released.html"/>

      <published>2013-04-18T16:17:32-07:00</published>
      <content type="html">&lt;p&gt;Inline allows you to write foreign code within your ruby code. It
automatically determines if the code in question has changed and
builds it only when necessary. The extensions are then automatically
loaded into the class/module that defines it.&lt;/p&gt;

&lt;p&gt;You can even write extra builders that will allow you to write inlined
code in any language. Use Inline::C as a template and look at
Module#inline for the required API.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;3.12.2 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added #prefix code to MD5 calculation to force rebuilds on non-signature changes.&lt;/li&gt;
      &lt;li&gt;Separated out #prefix code from #src.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;repo: &lt;a href=&quot;https://github.com/seattlerb/rubyinline&quot;&gt;https://github.com/seattlerb/rubyinline&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://www.zenspider.com/ZSS/Products/RubyInline/&quot;&gt;http://www.zenspider.com/ZSS/Products/RubyInline/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/RubyInline/&quot;&gt;http://docs.seattlerb.org/RubyInline/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-2-has-been-released.html</id>
      <title>minitest version 4.7.2 has been released!</title>
      <updated>2013-04-18T16:16:05-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-2-has-been-released.html"/>

      <published>2013-04-18T16:16:05-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.7.2 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed inconsistency in refute_in_delta/epsilon. I double negatived my logic. (nettsundere)&lt;/li&gt;
      &lt;li&gt;Fixed stubbing of module methods (eg Kernel#sleep). (steveklabnik)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/flog-version-4-0-0-has-been-released.html</id>
      <title>flog version 4.0.0 has been released!</title>
      <updated>2013-04-18T16:11:09-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/flog-version-4-0-0-has-been-released.html"/>

      <published>2013-04-18T16:11:09-07:00</published>
      <content type="html">&lt;p&gt;Flog reports the most tortured code in an easy to read pain
report. The higher the score, the more pain the code is in.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.0.0 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 major enhancement:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Renamed Flog#methods to #method_scores. (makaroni4)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;4 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added accessors for methods, scores. Now available for CIs! (makaroni4)&lt;/li&gt;
      &lt;li&gt;Refactored calculations down to 2 methods: total_score and totals. (makaroni4)&lt;/li&gt;
      &lt;li&gt;Refactored to #calculate, #threshold. (makaroni4)&lt;/li&gt;
      &lt;li&gt;Track stack of nested sclass scopes for parser (pithyless)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://ruby.sadi.st/&quot;&gt;http://ruby.sadi.st/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;repo: &lt;a href=&quot;https://github.com/seattlerb/flog&quot;&gt;https://github.com/seattlerb/flog&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/flog&quot;&gt;http://seattlerb.rubyforge.org/flog&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/hoe-version-3-6-0-has-been-released.html</id>
      <title>hoe version 3.6.0 has been released!</title>
      <updated>2013-04-18T15:54:27-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/hoe-version-3-6-0-has-been-released.html"/>

      <published>2013-04-18T15:54:27-07:00</published>
      <content type="html">&lt;p&gt;Hoe is a rake/rubygems helper for project Rakefiles. It helps you
manage, maintain, and release your project and includes a dynamic
plug-in system allowing for easy extensibility. Hoe ships with
plug-ins for all your usual project tasks including rdoc generation,
testing, packaging, deployment, and announcement..&lt;/p&gt;

&lt;p&gt;See class rdoc for help. Hint: &lt;code&gt;ri Hoe&lt;/code&gt; or any of the plugins listed
below.&lt;/p&gt;

&lt;p&gt;For extra goodness, see: http://seattlerb.rubyforge.org/hoe/Hoe.pdf&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;3.6.0 / 2013-04-18&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;5 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added built-in support for markdown.&lt;/li&gt;
      &lt;li&gt;Renamed rubyforge_name to group_name.&lt;/li&gt;
      &lt;li&gt;Aliased and deprecated rubyforge_name from group_name.&lt;/li&gt;
      &lt;li&gt;Strip &amp;lt;&amp;gt; from parse_urls for markdown style raw urls.&lt;/li&gt;
      &lt;li&gt;intuit_values looks for README.md and History.md as well as txt.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fix file_name regex for test file. (bhenderson/veganstraightedge)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://www.zenspider.com/projects/hoe.html&quot;&gt;http://www.zenspider.com/projects/hoe.html&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;doco: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe/Hoe.pdf&quot;&gt;http://seattlerb.rubyforge.org/hoe/Hoe.pdf&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;bugs: &lt;a href=&quot;https://github.com/seattlerb/hoe/issues&quot;&gt;https://github.com/seattlerb/hoe/issues&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;code: &lt;a href=&quot;https://github.com/seattlerb/hoe&quot;&gt;https://github.com/seattlerb/hoe&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe/&quot;&gt;http://seattlerb.rubyforge.org/hoe/&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;other: &lt;a href=&quot;http://github.com/jbarnette/hoe-plugin-examples&quot;&gt;http://github.com/jbarnette/hoe-plugin-examples&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/makerakeworkwell-version-1-0-3-has-been-released.html</id>
      <title>makerakeworkwell version 1.0.3 has been released!</title>
      <updated>2013-04-16T17:36:34-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/makerakeworkwell-version-1-0-3-has-been-released.html"/>

      <published>2013-04-16T17:36:34-07:00</published>
      <content type="html">&lt;p&gt;make/rake/work/well provides two simple modifications to rake that
make working with file tasks cleaner, easier, and faster.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.0.3 / 2013-04-16&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Removed gem activation from the code. No longer needed.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/makerakeworkwell&quot;&gt;https://github.com/seattlerb/makerakeworkwell&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/makerakeworkwell&quot;&gt;http://docs.seattlerb.org/makerakeworkwell&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/ruby_parser-version-3-1-3-has-been-released.html</id>
      <title>ruby_parser version 3.1.3 has been released!</title>
      <updated>2013-04-09T20:13:22-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/ruby_parser-version-3-1-3-has-been-released.html"/>

      <published>2013-04-09T20:13:22-07:00</published>
      <content type="html">&lt;p&gt;ruby_parser (RP) is a ruby parser written in pure ruby (utilizing
racc&amp;ndash;which does by default use a C extension). RP&amp;rsquo;s output is
the same as ParseTree&amp;rsquo;s output: s-expressions using ruby&amp;rsquo;s arrays and
base types.&lt;/p&gt;

&lt;p&gt;As an example:&lt;/p&gt;

&lt;p&gt;def conditional1 arg1
    return 1 if arg1 == 0
    return 0
  end&lt;/p&gt;

&lt;p&gt;becomes:&lt;/p&gt;

&lt;p&gt;s(:defn, :conditional1, s(:args, :arg1),
    s(:if,
      s(:call, s(:lvar, :arg1), :==, s(:lit, 0)),
      s(:return, s(:lit, 1)),
      nil),
    s(:return, s(:lit, 0)))&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;3.1.3 / 2013-04-09&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 bug fixes:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed begin w/ else but no rescue. (whitequark)&lt;/li&gt;
      &lt;li&gt;Removed literal stripping from block_append. Not its job.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/ruby_parser&quot;&gt;https://github.com/seattlerb/ruby_parser&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/ruby_parser&quot;&gt;http://docs.seattlerb.org/ruby_parser&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;bugs: &lt;a href=&quot;https://github.com/seattlerb/ruby_parser/issues&quot;&gt;https://github.com/seattlerb/ruby_parser/issues&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-1-has-been-released.html</id>
      <title>minitest version 4.7.1 has been released!</title>
      <updated>2013-04-09T20:10:10-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/minitest-version-4-7-1-has-been-released.html"/>

      <published>2013-04-09T20:10:10-07:00</published>
      <content type="html">&lt;p&gt;minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;I had a class with Jim Weirich on testing last week and we were
 allowed to choose our testing frameworks. Kirk Haines and I were
 paired up and we cracked open the code for a few test
 frameworks...

 I MUST say that minitest is *very* readable / understandable
 compared to the 'other two' options we looked at. Nicely done and
 thank you for helping us keep our mental sanity.&quot;

-- Wayne E. Seguin
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest/unit is a small and incredibly fast unit testing framework.
It provides a rich set of assertions to make your tests clean and
readable.&lt;/p&gt;

&lt;p&gt;minitest/spec is a functionally complete spec engine. It hooks onto
minitest/unit and seamlessly bridges test assertions over to spec
expectations.&lt;/p&gt;

&lt;p&gt;minitest/benchmark is an awesome way to assert the performance of your
algorithms in a repeatable manner. Now you can assert that your newb
co-worker doesn&amp;rsquo;t replace your linear algorithm with an exponential
one!&lt;/p&gt;

&lt;p&gt;minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
object framework.&lt;/p&gt;

&lt;p&gt;minitest/pride shows pride in testing and adds coloring to your test
output. I guess it is an example of how to write IO pipes too. :P&lt;/p&gt;

&lt;p&gt;minitest/unit is meant to have a clean implementation for language
implementors that need a minimal set of methods to bootstrap a working
test suite. For example, there is no magic involved for test-case
discovery.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;&quot;Again, I can't praise enough the idea of a testing/specing
 framework that I can actually read in full in one sitting!&quot;

-- Piotr Szotkowski
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Comparing to rspec:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;rspec is a testing DSL. minitest is ruby.

-- Adam Hawkins, &quot;Bow Before MiniTest&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;minitest doesn&amp;rsquo;t reinvent anything that ruby already provides, like:
classes, modules, inheritance, methods. This means you only have to
learn ruby to use minitest and all of your regular OO practices like
extract-method refactorings still apply.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;4.7.1 / 2013-04-09&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;1 minor enhancement:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added FAQ section to README&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;1 bug fix:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Fixed bug where guard runs tests bypassing minitest/autorun and an ivar isn&amp;rsquo;t set right. (darrencauthon)&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://docs.seattlerb.org/minitest&quot;&gt;http://docs.seattlerb.org/minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;vim: &lt;a href=&quot;https://github.com/sunaku/vim-ruby-minitest&quot;&gt;https://github.com/sunaku/vim-ruby-minitest&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/minitest&quot;&gt;https://github.com/seattlerb/minitest&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/flay-version-2-2-0-has-been-released.html</id>
      <title>flay version 2.2.0 has been released!</title>
      <updated>2013-04-09T17:43:26-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/flay-version-2-2-0-has-been-released.html"/>

      <published>2013-04-09T17:43:26-07:00</published>
      <content type="html">&lt;p&gt;Flay analyzes code for structural similarities. Differences in literal
values, variable, class, method names, whitespace, programming style,
braces vs do/end, etc are all ignored. Making this totally rad.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;2.2.0 / 2013-04-09&lt;/h3&gt;

&lt;p&gt;Semantic versioning doesn&amp;rsquo;t take into account how AWESOME a release
is. In this case, it severely falls short. I&amp;rsquo;d jump to 4.0 if I could.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;2 major enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added &amp;ndash;fuzzy (ie copy, paste, &amp;amp; modify) duplication detection.&lt;/li&gt;
      &lt;li&gt;Added &amp;ndash;liberal, which changes the way prune works to identify more duplication.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;12 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added -# to turn off item numbering. Helps with diffs to compare runs over time.&lt;/li&gt;
      &lt;li&gt;Added Sexp#+.&lt;/li&gt;
      &lt;li&gt;Added Sexp#code_index to specify where *code starts in some sexps.&lt;/li&gt;
      &lt;li&gt;Added Sexp#has_code?.&lt;/li&gt;
      &lt;li&gt;Added Sexp#initalize_copy to propagate file/line/modified info.&lt;/li&gt;
      &lt;li&gt;Added Sexp#modified, #modified=, and #modified?.&lt;/li&gt;
      &lt;li&gt;Added Sexp#split_at(n). (Something I&amp;rsquo;ve wanted in Array for ages).&lt;/li&gt;
      &lt;li&gt;Added Sexp#split_code.&lt;/li&gt;
      &lt;li&gt;Added mass and diff options to rake debug.&lt;/li&gt;
      &lt;li&gt;Added rake run task w/ mass, diff, and liberal options&lt;/li&gt;
      &lt;li&gt;Made report&amp;rsquo;s sort more stable, so I can do better comparison runs.&lt;/li&gt;
      &lt;li&gt;Wrapped Sexp#[] to propagate file/line/modified info.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;repo: &lt;a href=&quot;https://github.com/seattlerb/flay&quot;&gt;https://github.com/seattlerb/flay&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/flay&quot;&gt;http://seattlerb.rubyforge.org/flay&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;http://ruby.sadi.st/&quot;&gt;http://ruby.sadi.st/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
    <entry>
      <id>http://blog.zenspider.com/releases/2013/04/hoe-seattlerb-version-1-3-0-has-been-released.html</id>
      <title>hoe-seattlerb version 1.3.0 has been released!</title>
      <updated>2013-04-09T17:28:07-07:00</updated>

      <link rel="alternate" href="http://blog.zenspider.com/releases/2013/04/hoe-seattlerb-version-1-3-0-has-been-released.html"/>

      <published>2013-04-09T17:28:07-07:00</published>
      <content type="html">&lt;p&gt;Hoe plugins providing tasks used by seattle.rb including minitest,
perforce, and email providing full front-to-back release/annouce
automation.&lt;/p&gt;

&lt;p&gt;Changes:&lt;/p&gt;

&lt;h3 id=&quot;section&quot;&gt;1.3.0 / 2013-04-09&lt;/h3&gt;

&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt;3 minor enhancements:&lt;/p&gt;

    &lt;ul&gt;
      &lt;li&gt;Added history rake task. Outputs (and caches) flog/flay data across releases.&lt;/li&gt;
      &lt;li&gt;Added hoe/history.rb &amp;ndash; providing historical flog &amp;amp; flay numbers across releases.&lt;/li&gt;
      &lt;li&gt;Hooked in history plugin to be on by default.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;home: &lt;a href=&quot;https://github.com/seattlerb/hoe-seattlerb&quot;&gt;https://github.com/seattlerb/hoe-seattlerb&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;rdoc: &lt;a href=&quot;http://seattlerb.rubyforge.org/hoe-seattlerb&quot;&gt;http://seattlerb.rubyforge.org/hoe-seattlerb&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>
  
</feed>
