lemon 0.8.0 → 0.8.1

data/HISTORY.rdoc

@@ -0,0 +1,64 @@
+= RELEASE HISTORY
+
+== 0.8.1 / 2010-07-11
+
+This release adds a timer to the verbose output, which help isolate unit tests
+that are slow. It also fixed bug in Before and After advice that prevented them
+from triggering correctly.
+
+Changes:
+
+* Add times to verbose reporter.
+
+
+== 0.8.0 / 2010-06-21
+
+This release removes coverage information from testing. Coverage can be time
+consuming, but running test should be as fast as possbile. For this reason 
+coverage and testing are kept two independent activities. This release also
+adds some test coverage for Lemon itself via Cucumber.
+
+Changes:
+
+* Separated coverage from testing completely.
+* Test generator defaults to public methods only.
+
+
+== 0.7.0 / 2010-05-04
+
+This release fixes issue with coverage reports. To do this we have interoduced
+the +Covers+ method. This allows Lemon to distingush between code that is
+inteded to be covered by the tests and mere support code.
+
+Keep in mind that there is no perfect way to handle coverage. Even with the
+distiction the +Covers+ method provides, coverage might not be reported exactly
+as desired. Other techinques can be used to refine coverage however, such
+a preloading embedded support libraries.
+
+Changes:
+
+* Add +Covers+ method to solidify coverage reporting.
+* New Snapshot class improves encapsulation to coverage state.
+
+
+== 0.6.0 / 2010-03-06
+
+This release adds coverage reporting to testing and improves the generator.
+
+Changes:
+
+* Runner can provide uncovered and undefined testunit list.
+* Generator can exclude already covered testunits with -u option.
+* Suite class has Coverage instance.
+
+
+== 0.5.0 / 2009-12-31
+
+This is the initial public release of Lemon. Lemon is still under development
+and should be considered betaware, but it's API is stable and the system usable
+enough to warrant a release.
+
+Changes:
+
+* Happy First Release Day!
+

data/README.rdoc

@@ -21,7 +21,7 @@ Say our library 'mylib.rb' consists of the class X:
     def a; "a"; end
   end
 
-The simplist test case would be written as follows:
+The simplest test case would be written as follows:
 
   Covers 'mylib'
 
@@ -32,7 +32,7 @@ The simplist test case would be written as follows:
     end
   end
 
-The +Covers+ method works just like +require+ with the exception that loading the file does not occur until just before the tests are run. This allows Lemon to cacluate accurate coverage reports.
+The +Covers+ method works just like +require+ with the exception that loading the file does not occur until just before the tests are run. This allows Lemon to calculate accurate coverage reports.
 
 As tests grow, we might need to organize them into special concerns. For this Lemon provides the #Concern method.
 
@@ -59,17 +59,17 @@ Normal output is typical <i>dot-progress</i>. For verbose output, use the <code>
 
 === Checking Test Coverage
 
-Lemon can check test coverage by loading your target system and comparing it to your tests. To do this suppy the <code>lemon</code> command the <code>--coverage</code> or <code>-c</code> option.
+Lemon can check test coverage by loading your target system and comparing it to your tests. To do this supply the <code>lemon</code> command the <code>--coverage</code> or <code>-c</code> option.
 
   $ lemon --coverage -Ilib test/cases/
 
 === Generating Test Skeletons
 
-Because of the one to one correspondance of case-unit to class-method, Lemon can also generate test scaffolding for previously written code. To do this, use the <code>--generate</code> or <code>-g</code> option and provide the lib location, or files, of the scripts for which to generate test scaffolding, and the output location for the test scripts.
+Because of the one to one correspondence of case-unit to class-method, Lemon can also generate test scaffolding for previously written code. To do this, use the <code>--generate</code> or <code>-g</code> option and provide the lib location, or files, of the scripts for which to generate test scaffolding, and the output location for the test scripts.
 
   $ lemon --generate -Ilib test/cases/
 
-Generating test case scaffodling from code will undoubtedly strike test-driven developers as a case of putting the cart before the horse. However, it is not unreasonable to argue that high-level, behavior-driven, functional testing frameworks, such as Q.E.D. and Cucumber are better suited to test-first methodologies. While test-driven development can obviously be done with Lemon, unit-testing is more appropriate for testing specific, critical protions of code, or for achieving full test coverage for mission critical applications.
+Generating test case scaffolding from code will undoubtedly strike test-driven developers as a case of putting the cart before the horse. However, it is not unreasonable to argue that high-level, behavior-driven, functional testing frameworks, such as Q.E.D. and Cucumber are better suited to test-first methodologies. While test-driven development can obviously be done with Lemon, unit-testing is more appropriate for testing specific, critical portions of code, or for achieving full test coverage for mission critical applications.
 
 
 == COPYRIGHT

data/VERSION

@@ -2,5 +2,5 @@
 name : lemon
 major: 0
 minor: 8
-patch: 0
-date : 2010-06-21
+patch: 1
+date : 2010-07-10

data/lib/lemon/dsl.rb

@@ -52,7 +52,7 @@ end
 #
 # This sucks and it is not thread safe. If anyone know how to fix,
 # please let me know. See Unit#call for the other end of this hack.
-
+#
 def Object.const_missing(name)
   if unit = Lemon.test_stack.last
     begin
@@ -65,6 +65,16 @@ def Object.const_missing(name)
   end
 end
 
+#def Object.const_missing(name)
+#  if unit = Lemon.test_stack.last
+#    klass = (class << unit.testcase; self; end)
+#    if klass.const_defined?(name)
+#      return klass.const_get(name)
+#    end
+#  end
+#  super(name)
+#end
+
 # Get current running test. Used for the BIG FAT HACK.
 def Lemon.test_stack
   @@test_stack ||= []

data/lib/lemon/reporter/abstract.rb

@@ -73,6 +73,11 @@ module Reporter
       @ansicolor ? ANSI::Code.green{ string } : string
     end
 
+    #
+    def cyan(string)
+      @ansicolor ? ANSI::Code.cyan{ string } : string
+    end
+
     #
     def total
       successes.size + failures.size + errors.size + pendings.size

data/lib/lemon/reporter/verbose.rb

@@ -7,22 +7,24 @@ module Reporter
 
     #
     def report_start(suite)
+      timer_reset
     end
 
     #
     def report_concern(concern)
       puts
-      puts "#{concern.description}\n\n" unless concern.description.empty?
+      puts "== #{concern.description}\n\n" unless concern.description.empty?
+      timer_reset
     end
 
     #
     def report_success(testunit)
-      puts green("* #{testunit}")
+      puts "%12s  %s  %s" % [timer, green("SUCCESS"), green("#{testunit}")]
     end
 
     #
     def report_failure(testunit, exception)
-      puts red("* #{testunit} (FAILURE)")
+      puts "%12s  %s  %s" % [timer, red("FAILURE"), red("#{testunit}")]
       puts
       puts "        FAIL #{exception.backtrace[0]}"
       puts "        #{exception}"
@@ -31,7 +33,7 @@ module Reporter
 
     #
     def report_error(testunit, exception)
-      puts red("* #{testunit} (ERROR)")
+      puts "%12s  %s  %s" % [timer, red("ERRORED"), red("#{testunit}")]
       puts
       puts "        ERROR #{exception.backtrace[0]}"
       puts "        #{exception}"
@@ -40,7 +42,7 @@ module Reporter
 
     #
     def report_pending(testunit, exception)
-      puts yellow("* #{testunit} (PENDING)")
+      puts "%12s  %s  %s" % [timer, yellow("PENDING"), yellow("#{testunit}")]
       #puts
       #puts "        PENDING #{exception.backtrace[1]}"
       #puts
@@ -122,6 +124,18 @@ module Reporter
       puts tally
     end
 
+    #
+    def timer
+      secs  = Time.now - @time
+      @time = Time.now
+      return "%0.5fs" % [secs.to_s]
+    end
+
+    #
+    def timer_reset
+      @time = Time.now
+    end
+
   end
 
 end

data/lib/lemon/test/case.rb

@@ -97,7 +97,7 @@ module Lemon::Test
 
     # Define a before procedure for this case.
     def Before(*matches, &block)
-      matches == [nil] if matches.empty?
+      matches = [nil] if matches.empty?
       matches.each do |match|
         @before_clauses[match] = block #<< Advice.new(match, &block)
       end
@@ -107,7 +107,7 @@ module Lemon::Test
 
     # Define an after procedure for this case.
     def After(*matches, &block)
-      matches == [nil] if matches.empty?
+      matches = [nil] if matches.empty?
       matches.each do |match|
         @after_clauses[match] = block #<< Advice.new(match, &block)
       end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: lemon
 version: !ruby/object:Gem::Version 
-  hash: 63
+  hash: 61
   prerelease: false
   segments: 
   - 0
   - 8
-  - 0
-  version: 0.8.0
+  - 1
+  version: 0.8.1
 platform: ruby
 authors: 
 - Thomas Sawyer
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-06-20 00:00:00 -04:00
+date: 2010-07-11 00:00:00 -04:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -127,10 +127,10 @@ files:
 - test/fixtures/case_complete.rb
 - test/fixtures/case_incomplete.rb
 - test/fixtures/example.rb
+- HISTORY.rdoc
 - PROFILE
 - LICENSE
 - README.rdoc
-- HISTORY
 - REQUIRE
 - VERSION
 has_rdoc: true

data/HISTORY

@@ -1,43 +0,0 @@
-= RELEASE HISTORY
-
-== 0.8.0 / 2010-06-21
-
-This release removes coverage information from testing. Coverage can be time consuming, but running test should be as fast as possbile. For this reason coverage and testing are kept two independent activities. This release also adds some test coverage for Lemon itself via Cucumber.
-
-Changes:
-
-* Separated coverage from testing completely.
-* Test generator defaults to public methods only.
-
-
-== 0.7.0 / 2010-05-04
-
-This release fixes issue with coverage reports. To do this we have interoduced the +Covers+ method. This allows Lemon to distingush between code that is inteded to be covered by the tests and mere support code.
-
-Keep in mind that there is no perfect way to handle coverage. Even with the distiction the +Covers+ method provides, coverage might not be reported exactly as desired. Other techinques can be used to refine coverage however, such a preloading embedded support libraries.
-
-Changes:
-
-* Add +Covers+ method to solidify coverage reporting.
-* New Snapshot class improves encapsulation to coverage state.
-
-
-== 0.6.0 / 2010-03-06
-
-This release adds coverage reporting to testing and improves the generator.
-
-Changes:
-
-* Runner can provide uncovered and undefined testunit list.
-* Generator can exclude already covered testunits with -u option.
-* Suite class has Coverage instance.
-
-
-== 0.5.0 / 2009-12-31
-
-This is the initial public release of Lemon. Lemon is still under development and should be considered betaware, but it's API is stable and the system usable enough to warrant a release.
-
-Changes:
-
-* Happy First Release Day!
-