lemon 0.9.0 → 0.9.1

data/notes/2010-08-02-enforcing-the-unit.md

@@ -1,68 +0,0 @@
-2010-08-02 | Enforcing the Unit
-
-The current API for creating a Lemon unit testcase looks like this:
-
-    covers 'someclass'
-
-    testcase SomeClass do
-
-      unit :some_method => "does something or another" do
-        # ...
-      end
-
-    end
-
-As it currentlt standa the current design is little more than a means of
-organization, orienting the developer to think in terms of test units.
-What is does not do is enforce the actual testing the the unit referenced.
-We could put any old mess in the unit block and as long as it did not raise
-an exception, it would get a *pass*.
-
-Taking some time to consider this in depth, I've concieved of a way in which
-that use of the method could in fact be enforced.
-
-    covers 'someclass'
-
-    testcase SomeClass do
-
-      setup do
-        SomeClass.new
-      end
-
-      unit :some_method => "does something or another" do |unit|
-        unit.object      # object from setup
-        unit.call(...)   # calls #some_method on unit.object
-      end
-
-    end
-
-What is intersting about this, beyond that fact that it enforces the use of
-the class or module and method involved, but that it also does so in
-a way naturally suited to mocking --the `unit` delegator could even have
-mocking methods built-in.
-
-      unit :some_method => "does something or another" do |unit|
-        unit.receives.foo(:bar)  # object from setup would receive this call
-        unit.returns(:baz)       # the subsequent #call will return this
-        unit.call(...)           # calls #some_method on unit.object
-      end
-
-On the downside this approach limits what can be done in the unit block.
-One _has_ to utilize the object as defined in `setup` and one _has_ to invoke
-the unit method via the `#call` interface. Though, I suppose one could argue
-that these limitations are a good thing, as they help the unit stay narrowly
-focused on that goal at hand.
-
-I think this approach is worth considering for a possible furture version.
-Perhaps a "Lemon 2.0". For the time being I believe we can enforce the unit
-without resorting this major API change.
-
-The next release of Lemon will temporarily override the unit method on the
-target class for each unit execution. If the unit method gets called within
-the unit block, then it will be noted by the overridden method before passing
-off to the original definition. The approach is perhaps a bit draconian, and 
-is certainly only possible thanks to the remarkable dynamicism of Ruby, but
-it should work perfectly well. So now, if the target method is not called within
-the taget block, the unit will raise a Pending exception, regardless of the 
-code in the block. Unit Enforced!
-

data/notes/2010-08-03-new-api.md

@@ -1,37 +0,0 @@
-# 2010-08-03 | A New API
-
-Simplified API. There is one main method.
-
-  unit_test SomeClass, :some_method, "description" do
-    # test ...
-  end
-
-It will be a global method. The block notations would still work, but
-they would simple become wrappers for the main method.
-
-  testcase SomeClass do
-
-    unit :some_method, "description" do
-
-    end
-
-  end
-
-If I can make it backward compatible, I may also allow something like:
-
-  testcase SomeClass do
-
-    unit :some_method do
-
-      concern "description" do
-
-      end
-
-    end
-
-  end
-
-By using this global method, I should be able to simplify the underlying
-implementation a great deal, which has been major concern about Lemon
-as of late.
-

data/notes/2011-07-07-nailing-down-the-nomenclature.md

@@ -1,6 +0,0 @@
-# 2011-07-07 | Nailing Down the Nomenclature
-
-I have finally settled on `test_class` and `test_module` as thew new toplevel method for defining Lemon test cases. I decided against reusing `test_case` from Citron b/c I determined it is best that these types of test cases not be mixed together, but rather stay cleanly separated.
-
-I also decided against the original KO inspired nomenclature of `Test.case`. Though it looks very cool at first glance, in the end it goes against the grain. For instance, would one design an RSpec-stlye nomenclature as `Test.describe`, or a Cucumber-style nomenclature using `Test.feature`? While one could do so, it's completely uneccessry.
-

data/site/.rsync-filter

@@ -1,8 +0,0 @@
-- .svn
-- .gitignore
-P usage
-P statcvs
-P statsvn
-P robot.txt
-P robots.txt
-P wiki

data/site/assets/images/lemon.svg

@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN" "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg id="svg1" sodipodi:version="0.32" inkscape:version="0.38.1" width="400.00000pt" height="400.00000pt" sodipodi:docbase="/var/www/html/svg_gallery/svg/fruits" sodipodi:docname="lemon.svg" xmlns="http://www.w3.org/2000/svg" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:xlink="http://www.w3.org/1999/xlink">
-  <defs id="defs3">
-    <linearGradient id="linearGradient831">
-      <stop style="stop-color: rgb(255, 255, 0); stop-opacity: 1;" offset="0.0000000" id="stop832"/>
-      <stop style="stop-color: rgb(255, 227, 0); stop-opacity: 1;" offset="1.0000000" id="stop833"/>
-    </linearGradient>
-    <radialGradient xlink:href="#linearGradient831" id="radialGradient834" cx="0.33703703" cy="0.28358209" r="0.38183698" fx="0.33703703" fy="0.28358209"/>
-  </defs>
-  <sodipodi:namedview id="base" pagecolor="#ffffff" bordercolor="#666666" borderopacity="1.0" inkscape:pageopacity="0.0" inkscape:pageshadow="2" inkscape:zoom="1.3195079" inkscape:cx="120.13018" inkscape:cy="204.09312" inkscape:window-width="910" inkscape:window-height="775" inkscape:window-x="119" inkscape:window-y="24"/>
-  <g id="g838">
-    <path style="fill: url(#radialGradient834) rgb(0, 0, 0); fill-rule: evenodd; stroke: rgb(0, 0, 0); stroke-width: 10; stroke-linejoin: round; stroke-dasharray: none;" d="M 68.708186,148.12939 C 228.69852,9.5810597 474.45687,146.15839 471.15810,289.65487 C 497.54826,315.22034 467.85933,343.25988 451.36548,350.68211 C 309.51838,525.51691 17.577254,382.02043 34.895796,237.69925 C 12.847026,174.32754 32.421718,155.55162 68.708186,148.12939 z " id="path827" sodipodi:nodetypes="ccccc"/>
-    <path style="fill-opacity: 0.133333; fill-rule: evenodd; stroke-width: 1pt;" d="M 44.330330,267.99099 C 65.580330,246.74099 68.080330,411.74099 378.08033,350.49099 C 371.83033,344.24099 338.08033,201.74099 458.08033,249.24099 C 504.95533,263.61599 358.70533,239.55349 410.58033,339.24099 C 418.62433,352.33698 416.20533,352.36599 438.08033,357.99099 C 305.58033,500.49099 46.830330,390.49099 44.330330,267.99099 z " id="path828" sodipodi:nodetypes="cccccc"/>
-    <path style="fill: rgb(255, 255, 255); fill-opacity: 0.7; fill-rule: evenodd; stroke-width: 1pt;" d="M 68.080330,155.83295 C 124.36962,90.490990 313.68568,43.977604 438.08033,203.33295 C 395.58033,249.58295 275.58033,49.582958 68.080330,155.83295 z " id="path829" sodipodi:nodetypes="ccc"/>
-    <path style="fill: rgb(255, 255, 255); fill-opacity: 0.7; fill-rule: evenodd; stroke-width: 1pt;" d="M 469.33033,295.49099 C 483.64639,312.99099 470.58033,332.99099 460.58033,330.49099 C 381.83033,309.24099 424.33033,287.99099 469.33033,295.49099 z " id="path830" sodipodi:nodetypes="ccc"/>
-  </g>
-
-  <rdf:RDF xmlns="http://web.resource.org/cc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
-  <Work rdf:about="">
-    <dc:title>Clipart by Nicu Buculei - pear</dc:title>
-    <dc:rights>
-       <Agent>
-         <dc:title>Nicu Buculei</dc:title>
-       </Agent>
-    </dc:rights>
-    <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>
-    <license rdf:resource="http://web.resource.org/cc/PublicDomain"/>
-  </Work>
-   
-  <License rdf:about="http://web.resource.org/cc/PublicDomain">
-     <permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
-     <permits rdf:resource="http://web.resource.org/cc/Distribution"/>
-     <permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
-  </License>
-
-</rdf:RDF>
-</svg>

data/site/assets/styles/class.css

@@ -1,6 +0,0 @@
-.page { width: 730px; margin: 0 auto; }
-
-.bordered { border-top: 2px solid yellow; border-bottom: 2px solid yellow; }
-
-.copyright { padding: 0; text-align: left; }
-.copyright td { font-size: 10px; color: #444; }

data/site/assets/styles/reset.css

@@ -1,17 +0,0 @@
-html { font-family: sans-serif; font-size: 16px; color: black; }
-body { padding: 0; margin: 0; font-family: sans-serif; font-size: 12px; background: #fff; }
-
-h1 { font-size: 90px; margin: 20px; }
-
-p { font-size: 110%; text-align: justify; margin: 20px 0; line-height: 150%; }
-
-a { text-decoration: none; font-size: 100%; }
-a:hover { text-decoration: underline; }
-
-ul { margin: 0 auto; list-style-type: none; width: 300px; }
-li { float: left; padding: 10px; text-align: center; }
-
-pre  { font-size: 130%; padding: 10px 0 0 0; -moz-border-radius: 10px; font-family: courier, monospace; color: #000; }
-code { font-family: courier, monospace; }
-
-img { border: none; }

data/site/assets/styles/site.css

@@ -1,33 +0,0 @@
-h1 { font-family: times; font-size: 400%; margin: 20px 0; color: #f7d901; }
-h2 { font-size: 220%; margin-top: 30px; color: #444; }
-h3 { font-size: 190%; color: orange; }
-
-p { color: #222; font-weight: normal; font-size: 120%; }
-a { color: #262; }
-a:hover { text-decoration: underline; }
-
- pre { background: #ffffff; -moz-border-radius: 10px; line-height: 140%; }
-code { color: #222; font-weight: bold; }
-  tt { color: #222; font-weight: bold; }
-
-#nav { padding: 0 30px 20px 60px; text-align: left; color: pink; float: right; }
-#nav a { font-size: 160%; font-weight: bold; line-height: 150%; }
-#nav a:hover { color: #0C0; text-decoration: none; }
-
-#header { height: 250px; text-align: left; }
-#header h1 { font-size: 100px; padding: 40px 0 0 0; color: #f7d901; margin-left: -10px; }
-
-#main { color: white; padding: 20px 0 30px 0; background: url(../images/skin.jpg) #f7e931; }
-#main p { font-weight: bold; font-family: times; font-size: 150%; }
-#main h2 { color: #333333; }
-#main h3 { color: #333333; }
-
-#footer { margin-top: 40px; padding: 40px 0; text-align: center; background: url(../images/skin.jpg) #f7e931; }
-#footer .copyright { padding-top: 0; }
-#footer .copyright p { color: #222; font-weight: normal; font-size: 80%; line-height: 150%; }
-
-#forkme {
-  position: absolute;
-  top: 0; right: 0;
-  width: 150px;
-}

data/site/index.html

@@ -1,218 +0,0 @@
-<html>
-<head>
-  <title>Lemon</title>
-  <link href="assets/styles/reset.css" rel="stylesheet" type="text/css"/>
-  <link href="assets/styles/class.css" rel="stylesheet" type="text/css"/>
-  <link href="assets/styles/site.css"  rel="stylesheet" type="text/css"/>
-  <link href="assets/images/lemon.jpg" rel="shortcut icon"/>
-
-  <!-- syntax highlighing -->
-  <script src="http://rubyworks.github.com/assets/includes/shjs/sh_main.min.js"></script>
-  <script src="http://rubyworks.github.com/assets/includes/shjs/lang/sh_ruby.min.js"></script>
-  <script src="http://rubyworks.github.com/assets/includes/shjs/lang/sh_sh.min.js"></script>
-  <link  href="http://rubyworks.github.com/assets/includes/shjs/css/sh_acid.min.css" rel="stylesheet" type="text/css" />
-</head>
-<body onload="sh_highlightDocument();">
-
-<div id="forkme">
-  <a href="http://github.com/rubyworks/lemon"><img src="assets/images/forkme.png" /></a>
-</div>
-
-<div id="header">
-<div class="page">
-  <img src="assets/images/cut-lemon.png" height="200px" align="right" style="padding-top: 15px;"/>
-  <h1><img src="assets/images/title.png"/></h1>
-  <h2>Pucker-Strength Unit Testing</h2>
-</div>
-</div>
-
-<div id="main" class="bordered">
-<div class="page">
-
-  <div id="nav">
-    <!-- <a href="guide/doc.en/index.html">English Manual</a> &nbsp;&middot;&nbsp; -->
-    <a href="http://wiki.github.com/rubyworks/lemon">Wiki</a> <br/>
-    <a href="http://rubydoc.info/gems/lemon/frames">API</a> <br/>
-    <a href="http://googlegroups.com/group/rubyworks-mailinglist">Email</a> <br/>
-    <a href="http://github.com/rubyworks/lemon/issues">Issue</a> <br/>
-    <a href="http://github.com/rubyworks/lemon">Code</a>
-  </div>
-
-  <p>Lemon is a unit testing framework which enforces highly formal
-  case-to-class and unit-to-method test construction.
-  This strict approach is arguably a more proper technique for unit
-  testing because it helps focus concern on individual units of
-  behavior and thus helps promote good test coverage. This is unlike
-  functional and integration testing which rightly focus on more
-  holistic issues.</p>
-
-<!--
-  <h3>Writing Tests</h3>
-
-  <p>Let's say we have a library that consists of the class <code>HelloWorld</code>
-  with method <code>#to_s</code>:<p>
-
-  <pre class="sh_ruby">
-  class HelloWorld
-    def to_s
-      "Hello, World!"
-    end
-  end
-  </pre>
-
-  <p>We would write a Lemon test case along the following lines:</p>
-
-  <pre class="sh_ruby">
-  TestCase HelloWorld do
-    Concern "String output works as expected."
-
-    Unit :to_s do
-      Test "returns a string" do
-        HelloWorld.new.to_s.assert.is_a?(String)
-      end
-      Test "returns the world famous phrase" do
-        HelloWorld.new.to_s.assert == "Hello, World!"
-      end
-    end
-  end
-  </pre>
-
-  <p>Clearly an overly simplistic example, but it demonstrates well enough the overall design of Lemon
-  tests. Notice that the <code>#TestCase</code> method references a class (this can also be a module) and the units each
-  refer to a method of the class.</p>
-
-  <p>Lemon uses the <a href="http://rubyworks.github.com/ae">Assertive Expressive</a>
-  assertions framework. This is the same verstile framework used by <a href="http://rubyworks.github.com/qed">Q.E.D.</a>.
-  By default Lemon test support the standard <code>#assert</code> and <code>#expect</code> assertion methods.
-  If you wish to use subjunctive terms, either <code>#should</code> or <code>#must</code>, you can load these
-  via a helper script (eg. <code>require 'ae/should'</code>).</p>
-
-  <h3>Running Tests</h3>
-
-  <p>The <tt>lemon</tt> command-line tool is used to run tests. Simply provide the name of the test files as arguments:</p>
-
-  <pre class="sh_sh">
-  > lemon test/cases/*.rb
-  </pre>
-
-  <p>By default the <tt>lemon</tt> command outputs the traditional dot-progress format. The <tt>--verbose</tt>
-  or <tt>-v</tt> option provides additional information about each unit test and concern
-  as they are executed.</p>
-
-  <h3>Test Coverage</h3>
-
-  <p>The <tt>lemon</tt> command can also be used to check test coverage. For this use the <tt>--coverage</tt>
-  or <tt>-c</tt> option.</p>
-
-  <pre class="sh_sh">
-  > lemon -c test/cases/*.rb
-  </pre>
-
-  <p>To enusre only the code you are interested in is checked, you can either use <tt>-r</tt> to pre-require
-  support libraries you wish not to include in the output. Or more conveniently, supply specific namespaces
-  to include via the <tt>--namespace</tt> or <tt>-n</tt> option.
-
-  <pre class="sh_sh">
-  > lemon -c -n HelloWorld test/cases/*.rb
-  </pre>
-
-  <p>For more information on Lemon and how to use it please see the Lemon <a href="http://wiki.github.com/rubyworks/lemon">Wiki</a>.</p>
-
-  <h2>Development</h2>
-
-  <p>Lemon is a RubyWorks project. Development is hosted on GitHub at:</p>
-
-  <pre>
-  <a href="http://github.com/rubyworks/lemon">http://github.com/rubyworks/lemon</a>
-  </pre>
-
-  <h3>License</h3>
-
-  <p>Lemon is an open-source project licensed under the terms of <b>Lesser General Public License</b>.</p>
-
--->
-</div>
-</div>
-
-<div>
-<div class="page">
-  <h3>Example</h3>
-
-  <p>To give you a taste of what a lemon testcase looks like, let's say we have a library
-  that consists of the class <code>HelloWorld</code> with method <code>#to_s</code>:<p>
-
-<pre class="sh_ruby">
-  class HelloWorld
-    def to_s
-      "Hello, World!"
-    end
-  end
-</pre>
-
-  <p>We would write a Lemon test case along the following lines:</p>
-
-<pre class="sh_ruby">
-  TestCase HelloWorld do
-    Concern "String output works as expected."
-
-    Unit :to_s => "returns a string" do
-      HelloWorld.new.to_s.assert.is_a?(String)
-    end
-
-    Unit :to_s => "returns a 13 character phrase" do
-      HelloWorld.new.to_s.size.assert == 13
-    end
-  end
-</pre>
-
-  <p>A silly example to be sure, but one we can all easily understand.</p>
-
-</div>
-</div>
-
-<div id="footer" class="bordered">
-<div class="page">
-  <script type="text/javascript"><!--
-  google_ad_client = "ca-pub-1126154564663472";
-  /* RUBYWORKS 09-10-02 728x90 */
-  google_ad_slot = "0788888658";
-  google_ad_width = 728;
-  google_ad_height = 90;
-  //-->
-  </script>
-  <script type="text/javascript"
-  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-  </script>
-
-  <br/><br/><br/>
-
-  <div class="copyright" width="100%">
-    <a href="http://rubyworks.github.com/">
-      <img src="assets/images/ruby-logo.png" height="110px" align="left" style="margin: 0 5px; padding: 0 10px" />
-    </a>
-    <a href="http://www.apache.org/licenses/LICENSE-2.0.html">
-      <img src="assets/images/opensource.png" height="120px" align="left" style="padding: 0 10px;" />
-    </a>
-    <a href="github.com/rubyworks/lemon">
-      <img src="assets/images/github-logo.png" height="115px" align="left" style="margin: 0; padding: 0 10px;" />
-    </a>
-    <a href="http://testanything.org/wiki/index.php/Main_Page">
-      <img src="assets/images/tap.png" height="113px" align="left" style="margin: 0; padding: 0 20px;" />
-    </a>
-    <a href="">
-      <img src="assets/images/lemons-are-good.png" height="117px" align="left" style="margin: 0; padding: 0 10px;" />
-    </a>
-  </div>
-
-  <br style="clear: both;" />
-
-  <div style="margin-top: 30px;">
-      <b>Lemon</b>, Copyright &copy; 2009 Thomas Sawyer &middot;
-      <b>Contact:</b> transfire @ gmail.com
-  </div>
-</div>
-</div>
-
-</body>
-</html>
-