picard 0.0.3 → 0.1

data/README.markdown

@@ -0,0 +1,75 @@
+## Now, let’s take a look at a test using Picard
+
+    require 'picard'
+
+    class DemoTest < Test::Unit::TestCase
+	    include Picard::TestUnit
+
+	    def test_simple_math
+  	    given
+    	    x = 1
+    	    y = 2
+
+  	    expect
+    	    x + y == 3
+	    end
+    end
+
+To start using picard you need to mix in Picard::TestUnit module into your TestUnit test case.  It will add a special hook that will transform every test method in your test case. For instance, the "test_simple_math" method will be transformed into something like:
+
+    def test_simple_math
+      given
+        x = 1
+        y = 2
+      
+      expect
+        assert_equal 3, (x + y), MESSAGE
+      end
+    end
+
+
+Where the MESSAGE is:
+
+  --------------------------------------------------------------------------------------
+  | File: "/Users/savkin/projects/picard/test/picard/demo_test.rb", Line: 10           |
+  | Failed Assertion: (x + y == 3)                                    	               |
+  --------------------------------------------------------------------------------------
+
+
+You might notice a few things here:
+1. Picard uses TestUnit, so all your tools we will work with it just fine.
+2. Picard is smart enough to insert assert_equal instead of regular assert.
+3. Picard generates a very descriptive error message containing not only the file name and the line number of the failed assertion but the assertion itself. In most cases it’s enough information to understand what went wrong so you won't have to find that exact line number to figure it out.
+
+
+## What if I want to try?
+
+    gem 'picard'
+
+
+## What is coming next?
+
+There are some things I'm going to add in a week or two:
+
+1. The only special case Picard supports right now is `==`. If you are using something like `x != y` in your `expect` block it will just insert a regular `assert` which is bad. It's going to be much smarter than this soon.
+2.
+In Spock it's possible to write data driven tests:
+ 
+    expect:
+    x + y == z
+    
+    where:
+    x = [1, 10, 100]
+    y = [2, 20, 200]
+    z = [3, 30, 300]
+
+Basically it will transform into something like:
+
+    expect:
+    1 + 2 == 3
+    10 + 20 == 30
+    100 + 200 == 300
+
+Which is totally awesome! I'm going to add a similar feature to Picard soon.
+
+3. Right now Picard is written in Ruby 1.9 but it can parse only 1.8 syntax (which is weird). It needs to be put in order so it will work properly on 1.8 and 1.9.

data/lib/picard/version.rb

@@ -1,3 +1,7 @@
-module Picard
-  VERSION = "0.0.3"
+module PicardTestFramework
+  module V01
+    VERSION = "0.1"
+  end
 end
+
+Picard = PicardTestFramework::V01

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: picard
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: '0.1'
   prerelease: 
 platform: ruby
 authors:
@@ -9,12 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2011-10-02 00:00:00.000000000 -04:00
-default_executable: 
+date: 2011-10-15 00:00:00.000000000Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: live_ast
-  requirement: &2169351160 !ruby/object:Gem::Requirement
+  requirement: &2156661700 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - =
@@ -22,10 +21,10 @@ dependencies:
         version: 1.0.2
   type: :runtime
   prerelease: false
-  version_requirements: *2169351160
+  version_requirements: *2156661700
 - !ruby/object:Gem::Dependency
   name: live_ast_ripper
-  requirement: &2169350560 !ruby/object:Gem::Requirement
+  requirement: &2156659860 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - =
@@ -33,10 +32,10 @@ dependencies:
         version: 0.6.5
   type: :runtime
   prerelease: false
-  version_requirements: *2169350560
+  version_requirements: *2156659860
 - !ruby/object:Gem::Dependency
   name: flexmock
-  requirement: &2169350180 !ruby/object:Gem::Requirement
+  requirement: &2156659180 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -44,7 +43,7 @@ dependencies:
         version: '0'
   type: :development
   prerelease: false
-  version_requirements: *2169350180
+  version_requirements: *2156659180
 description: Test framework inspired by Spock
 email:
 - vic.savkin@gmail.com
@@ -55,7 +54,7 @@ files:
 - .gitignore
 - Gemfile
 - Gemfile.lock
-- README.rdoc
+- README.markdown
 - Rakefile
 - lib/picard.rb
 - lib/picard/assertion_wrapper.rb
@@ -79,7 +78,6 @@ files:
 - test/picard/preprocessor_test.rb
 - test/picard/test_unit_test.rb
 - test/test_helper.rb
-has_rdoc: true
 homepage: ''
 licenses: []
 post_install_message: 
@@ -100,7 +98,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: picard
-rubygems_version: 1.6.2
+rubygems_version: 1.8.10
 signing_key: 
 specification_version: 3
 summary: Test framework inspired by Spock

data/README.rdoc

@@ -1,15 +0,0 @@
-== Test Framework "Picard"
-
-Picard is a test framework heavily inspired by "Spock" (an excellent test framework for the Groovy programming language). It does some AST manipulation to make the structure of your test explicit:
-
-    def test_method
-      given
-        x = 1
-
-      expect
-        x == 1
-    end
-
-The "given" block is a setup you do for your test. Every line in the "expect" block is an assertion.
-
-