slacker 1.0.2 → 1.0.4

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    slacker (1.0.2)
+    slacker (1.0.4)
       bundler (~> 1.0.15)
       rspec (~> 2.5.0)
       ruby-odbc (= 0.99994)

data/README.markdown

@@ -1,44 +1,8 @@
 # Slacker
-Behavior Driven Development for SQL Server
-
-# Description
-Slacker is a Ruby (RSpec-based) framework for developing automated tests for SQL Server programmable objects such as stored procedures and scalar/table functions.
-
-# Installation
-    gem install slacker
-
-### Requirements
-
-* Ruby 1.9.2.
-
-Runs on Windows and Linux.
-
-_Note_: Before installing on Windows, you need to install the [Ruby Windows Development Kit](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit).
-
-# Quick Start
-To create a new Slacker project, run the following command:
-
-    slacker_new my_project
 
-This will create a new project directory `my_project`.
-
-Navigate to the new project directory and modify file `database.yml` to tell Slacker which database to connect to.
-
-Run Slacker:
-
-    slacker
-
-If all is good, you should see something like this:
-
-    my_database (my_server)
-    .....
-
-    Finished in 0.05222 seconds
-    5 examples, 0 failures
-
-Next, check out sample file `my_project\spec\sample_1.rb` to see the BDD specification you just executed.
+Behavior Driven Development for SQL Server
 
-Also take a look at the SQL files generated in folder `my_project\debug\passed_examples`. Those are the actual SQL scripts Slacker generated and executed against your database.
+Slacker is a transacted RSpec-based framework for developing automated tests for SQL Server 2005 and 2008 programmable objects such as stored procedures, scalar/table functions, triggers, etc.
 
 # Resources
 
@@ -55,4 +19,4 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/lib/slacker/version.rb

@@ -1,3 +1,3 @@
 module Slacker
-  VERSION = "1.0.2"
+  VERSION = "1.0.4"
 end

data/lib/slacker_new/project/spec/sample_1.rb

@@ -1,52 +1,41 @@
-# Method describe opens up an example group.
+# Method "describe" opens up an example group.
 describe 'My database' do
-  # Simple example which demonstrates inline query against the database.
+  # Simple inline query example.
   it 'contains system tables' do
-    # Select all system objects in the database.
-    # We should have at least one of those.
+    # Make sure we have at least one system object in the database.
     query("select * from sysobjects where xtype = 'S';").count.should > 0
   end
 
-  # The same query, this time using a SQL template.
-  # See file sql/sample_1/sysobject.sql.erb
+  # The same query, this time using a SQL template stored in file "sql/sample_1/sysobject.sql.erb".
   it 'contains system tables (take two)' do
-    # SQL templates are located in the sql folder and are accessible through the "sql" object (see below).
-    # Each sub-folder of the sql folder appears as a sql object contained within its parent startint at the root - the "sql" object.
-    # Each template file (*.sql.erb) appears as a method of the folder it appears in.
-    # 
-    # For example, the file sysobjects.sql.erb is located in "sql/sample_1/",
-    # so it is accessible like this:
-    # sql.sample_1.sysobjects
+    # Every (*.sql.erb) file in folder "sql" can be called as a method on object "sql".
+    # Subfolders of folder "sql" appear as children of object "sql" with their (*.sql.erb) files automatically available as methods.
     sql.sample_1.sysobjects.count.should > 0
   end
 
   # This time we'll use a parameterized template.
-  # See file sql/sample_1/sysobject_with_params.sql.erb
   it 'contains system tables (take three)' do
-    # You can pass a hash to any SQL template - this hash becomes available to the
-    # template through the "options" object - see file sql/sample_1/sysobject_with_params.sql.erb as an example.
+    # Every template can accept parameters; see file "sql/sample_1/sysobject_with_params.sql.erb".
     sql.sample_1.sysobjects_with_params(:xtype => 'S').count.should > 0
   end
 
   # SQL Templates can contain multiple statements and can return multiple resultsets.
   it 'can play with numbers' do
-    # Note that this time we're calling the template with a block.
-    # When called with a block, a template is executed and its results are accessible
-    # from within the block through the "results" object.
+    # Note that this time we're calling the template with a block which receives the results as a block parameter.
     sql.sample_1.play_with_numbers(:x => 2, :y => 12) do |results|
       # The results object contains an array of all the resultsets generated by the query script.
-      # A resultset contains an array of records.
-      # Each record is a hash of field => value pairs.
+      # A resultset contains an array of records. Each record is a hash of field => value pairs.
+      
+      # First resultset; First record; Column "product".
       results[0][0][:product].should == 24
 
-      # A resultset can be matched directly against an array of hashes using the "match" method.
+      # A resultset can be matched directly against an array of hashes using method "match".
       results[1].should match([{:x => 2, :y => 12, :sum => 14}])
 
-      # Or against a CSV file stored in the data folder (see file data/sample_1/numbers_expected_output.csv)
+      # Or against a CSV file stored in project's "data" folder (see file "data/sample_1/numbers_expected_output.csv").
       results[2].should match('sample_1/numbers_expected_output.csv')
 
-      # Or a resultset's values can be matched one-by-one.
-      # Note that the third resultset contains two records:
+      # A resultset's values can be matched one-by-one.
       results[2][0][:p].should == 2
       results[2][0][:s].should == 34
       results[2][1][:p].should == 12
@@ -54,27 +43,24 @@ describe 'My database' do
     end
   end
 
-  # Every "it" (example) is executed in a transaction which is rolled back once the example is complete.
-  # This ensures that every example starts at the same state of the database as any other example in the spec.
-  # No example can ever interfere witht the results of another example.
+  # Every "it" (example) is executed in a T-SQL transaction which is rolled back once the example is complete.
+  # No example can ever interfere with the results of another example.
   # 
   # CSV files can be used to load data directly into a table.
   # In this example, we will create a table, populate it with data,
   # calculate the exponentiation of one column based on another column
   # and verify the results against an expected resultset stored in a CSV file.
-  it 'can play with numbers (take three)' do
-    # Create the table - see file sql/sample_1/create_my_table.sql.erb
+  it 'can play with numbers (take two)' do
+    # Create the table - see file "sql/sample_1/create_my_table.sql.erb".
     sql.sample_1.create_my_table
-    # We can populate any table by calling method "load_csv".
-    # As a first parameter we will pass the name of the CSV file which contains the source data;
-    # The file name is relative to the data folder - see file data/sample_1/my_table_initial_data.csv.
-    # The name of the destination table goes into the second parameter.
-    load_csv 'sample_1/my_table_initial_data.csv', 'MyTable'
+    # We can populate any table with data from the "data" folder by calling method "load_csv".
+    # See file "data/sample_1/my_table_initial_data.csv".
+    load_csv('sample_1/my_table_initial_data.csv', 'MyTable')
 
     # Now let's test the system scalar function Power.
     # We will use it in a query expression executed agaings MyTable and we
     # will compare the results against a CSV file - we should expect them to match.
-    # See files "sql/sample_1/my_table_on_power.sql.erb" and "data/sample_1/my_table_expected_power_results.csv"
+    # See files "sql/sample_1/my_table_on_power.sql.erb" and "data/sample_1/my_table_expected_power_results.csv".
     sql.sample_1.my_table_on_power.should match('sample_1/my_table_expected_power_results.csv')
   end
 end

metadata

@@ -2,7 +2,7 @@
 name: slacker
 version: !ruby/object:Gem::Version 
   prerelease: 
-  version: 1.0.2
+  version: 1.0.4
 platform: ruby
 authors: 
 - Vassil Kovatchev
@@ -10,7 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-07-01 00:00:00 Z
+date: 2011-07-03 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: bundler