Merge pull request #2 from esambo/master

Awesome, thanks! RSpec 2 support

.gitignore

@@ -3,3 +3,4 @@
 coverage
 rdoc
 pkg
+rerun.txt

.rspec

@@ -0,0 +1,2 @@
+--color
+--format documentation

.rvmrc

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Based on: http://rvm.beginrescueend.com/workflow/rvmrc/
+
+ruby_string="ruby-1.9.3-p0"
+gemset_name="practice_game_of_life"
+
+if rvm list strings | grep -q "${ruby_string}" ; then
+
+  # Load or create the specified environment
+  if [[ -d "${rvm_path:-$HOME/.rvm}/environments" \
+    && -s "${rvm_path:-$HOME/.rvm}/environments/${ruby_string}@${gemset_name}" ]] ; then
+    \. "${rvm_path:-$HOME/.rvm}/environments/${ruby_string}@${gemset_name}"
+  else
+    rvm --create  "${ruby_string}@${gemset_name}"
+  fi
+
+  (
+    # Ensure that Bundler is installed, install it if it is not.
+    if ! command -v bundle ; then
+      gem install bundler
+    fi
+
+    # Bundle while redcing excess noise.
+    bundle | grep -v 'Using' | grep -v 'complete' | sed '/^$/d'
+  )&
+
+else
+
+  # Notify the user to install the desired interpreter before proceeding.
+  echo "${ruby_string} was not found, please run 'rvm install ${ruby_string}' and then cd back into the project directory."
+
+fi

Gemfile

@@ -0,0 +1,12 @@
+source :rubygems
+gem 'rake'
+gem 'jeweler'
+gem 'rdoc'
+gem 'rcov'
+gem 'relish'
+
+gem 'rspec'
+gem 'cucumber'
+gem 'guard-rspec'
+gem 'guard-cucumber'
+gem 'growl_notify'

Gemfile.lock

@@ -0,0 +1,66 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    archive-tar-minitar (0.5.2)
+    builder (3.0.0)
+    cucumber (1.0.0)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.2)
+      gherkin (~> 2.4.1)
+      json (>= 1.4.6)
+      term-ansicolor (>= 1.0.5)
+    diff-lcs (1.1.2)
+    gherkin (2.4.1)
+      json (>= 1.4.6)
+    git (1.2.5)
+    growl_notify (0.0.1)
+      rb-appscript
+    guard (0.6.3)
+      thor (~> 0.14.6)
+    guard-cucumber (0.6.2)
+      cucumber (>= 0.10)
+      guard (>= 0.4.0)
+    guard-rspec (0.4.4)
+      guard (>= 0.4.0)
+    jeweler (1.6.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+    json (1.5.3)
+    mime-types (1.17.2)
+    rake (0.9.2.2)
+    rb-appscript (0.6.1)
+    rcov (0.9.11)
+    rdoc (3.11)
+      json (~> 1.4)
+    relish (0.5.3)
+      archive-tar-minitar (>= 0.5.2)
+      json (>= 1.4.6)
+      rest-client (>= 1.6.1)
+    rest-client (1.6.7)
+      mime-types (>= 1.16)
+    rspec (2.6.0)
+      rspec-core (~> 2.6.0)
+      rspec-expectations (~> 2.6.0)
+      rspec-mocks (~> 2.6.0)
+    rspec-core (2.6.4)
+    rspec-expectations (2.6.0)
+      diff-lcs (~> 1.1.2)
+    rspec-mocks (2.6.0)
+    term-ansicolor (1.0.5)
+    thor (0.14.6)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  cucumber
+  growl_notify
+  guard-cucumber
+  guard-rspec
+  jeweler
+  rake
+  rcov
+  rdoc
+  relish
+  rspec

Guardfile

@@ -0,0 +1,11 @@
+guard 'rspec', version: 2 do
+  watch(%r{^spec/.+_spec\.rb$})
+  watch(%r{^lib/(.+)\.rb$})     { |m| "spec/lib/#{m[1]}_spec.rb" }
+  watch('spec/spec_helper.rb')  { "spec/" }
+end
+
+guard 'cucumber', cli: '--profile guard' do
+  watch(%r{^features/.+\.feature$})
+  watch(%r{^features/support/.+$})          { 'features' }
+  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'features' }
+end

Rakefile

@@ -18,35 +18,35 @@ rescue LoadError
   puts "Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler"
 end
 
-require 'spec/rake/spectask'
-Spec::Rake::SpecTask.new(:spec) do |spec|
-  spec.libs << 'lib' << 'spec'
-  spec.spec_files = FileList['spec/**/*_spec.rb']
+require 'rspec'
+require 'rspec/core/rake_task'
+RSpec::Core::RakeTask.new(:spec) do |spec|
+  spec.rspec_opts = ['--format doc', '--color']
 end
 
-Spec::Rake::SpecTask.new(:rcov) do |spec|
-  spec.libs << 'lib' << 'spec'
+RSpec::Core::RakeTask.new(:rcov) do |spec|
   spec.pattern = 'spec/**/*_spec.rb'
   spec.rcov = true
 end
 
-task :spec => :check_dependencies
+# task :spec => :check_dependencies
 
 begin
   require 'cucumber/rake/task'
-  Cucumber::Rake::Task.new(:features)
-
-  task :features => :check_dependencies
+  Cucumber::Rake::Task.new(:features) do |f|
+    f.cucumber_opts = "features --format pretty"
+    # task :features => :check_dependencies
+  end
 rescue LoadError
   task :features do
     abort "Cucumber is not available. In order to run features, you must: sudo gem install cucumber"
   end
 end
 
-task :default => :spec
+task :default => [:spec, :cucumber]
 
-require 'rake/rdoctask'
-Rake::RDocTask.new do |rdoc|
+require 'rdoc/task'
+RDoc::Task.new do |rdoc|
   if File.exist?('VERSION')
     version = File.read('VERSION')
   else

cucumber.yml

@@ -0,0 +1,2 @@
+wip: --tags @wip:3 --wip features
+guard: --tags @wip --format progress --wip features

features/.nav

@@ -0,0 +1,9 @@
+- doc (Documentation):
+  - rules_of_life.md (Rules of Life)
+  - rules_of_simple_design.md (Rules of Simple Design)
+  - source_code.md (Source Code)
+- live_cell.feature
+- dead_cell.feature
+- multiple_cells.feature
+- static_structures.feature
+- multiple_generations.feature

features/README.md

@@ -0,0 +1,20 @@
+# Practice Game of Life
+
+## [Code Retreat](http://coderetreat.com)
+w/ [Corey Haines](http://www.twitter.com/coreyhaines)  
+*- honing the craft together*
+
+Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and modular design, primarily the [4 Rules of Simple Design](http://c2.com/cgi/wiki?XpSimplicityRules):
+
+1. Tests Pass (green)
+2. Reveal Intent (good names)
+3. No Duplication (DRY)
+4. Small
+
+
+## Wikipedia: [Conway's Game of Life](http://en.wikipedia.org/wiki/Conway%27s_Game_of_Life)
+
+The **Game of Life**, also known simply as **Life**, is a cellular automaton devised by the British mathematician John Horton Conway in 1970.
+
+The "game" is a zero-player game, meaning that its evolution is determined by its initial state, requiring no further input. One interacts with the Game of Life by creating an initial configuration and observing how it evolves.
+

features/dead_cell.feature

@@ -1,7 +1,7 @@
 Feature: Evolving a dead cell
-  In order to create a functioning rules engine
-  As a programmer of Conway's Game of Life
-  I can evolve a single dead cell based
+  In order to create a functioning rules engine  
+  As a programmer of Conway's Game of Life  
+  I can evolve a single dead cell based  
 
   Scenario: Dead cell with 0 neighbors stays dead
     Given the following setup

features/doc/rules_of_life.md

@@ -0,0 +1,18 @@
+Based on Wikipedia: Conway's Game of Life: [Rules](http://en.wikipedia.org/wiki/Conway%27s_Game_of_Life#Rules)
+
+The universe of the Game of Life is an infinite two-dimensional orthogonal grid of square *cells*, each of which is in one of two possible states, *alive* or *dead*. Every cell interacts with its eight *neighbors*, which are the cells that are horizontally, vertically, or diagonally adjacent. At each step in time, the following transitions occur:
+
+### 1. Under-Population
+- Any live cell with *fewer than 2* live neighbors *dies*
+
+### 2. Next Generation
+- Any live cell with *2 or 3* live neighbors *lives* on
+
+### 3. Overcrowding
+- Any live cell with *more than 3* live neighbors *dies*
+
+### 4. Reproduction
+- Any dead cell with *exactly 3* live neighbors becomes a *live* cell
+
+The initial pattern constitutes the *seed* of the system. The first generation is created by applying the above rules simultaneously to every cell in the seed—births and deaths occur simultaneously, and the discrete moment at which this happens is sometimes called a *tick* (in other words, each generation is a pure function of the preceding one). The rules continue to be applied repeatedly to create further generations.
+

features/doc/rules_of_simple_design.md

@@ -0,0 +1,8 @@
+[4 Rules of Simple Design](http://c2.com/cgi/wiki?XpSimplicityRules):
+
+Based on the [SCNA 2011 Code Retreat](http://twitpic.com/7gz0k2)
+
+1. Tests Pass (green)
+2. Reveal Intent (good names)
+3. No Duplication (DRY)
+4. Small

features/doc/source_code.md

@@ -0,0 +1,3 @@
+## [Cucumber Features](http://cukes.info/)
+Building a Conways’ Game of Life simulator is a great way to practice different techniques in the language of your choice. This ***[git repository](https://github.com/coreyhaines/practice_game_of_life)*** contains a set of cucumber features that describe the rules of Conway’s Game of Life. I’ve also included a few standard, larger patterns that you can use to check multiple generation evolution.
+

features/live_cell.feature

@@ -1,7 +1,7 @@
 Feature: Evolving a living cell
-  In order to create a functioning rules engine
-  As a programmer of Conway's Game of Life
-  I can evolve a single living cell
+  In order to create a functioning rules engine  
+  As a programmer of Conway's Game of Life  
+  I can evolve a single living cell  
 
   Scenario: Living cell with 0 neighbors dies
     Given the following setup

features/multiple_cells.feature

@@ -1,7 +1,7 @@
 Feature: Evolving a grid with some cells in it
-  In order to create a functioning rules engine
-  As a programmer of Conway's Game of Life
-  I can evolve a multiple cell grid
+  In order to create a functioning rules engine  
+  As a programmer of Conway's Game of Life  
+  I can evolve a multiple cell grid  
 
   Scenario: Sparse grid with nobody staying alive
     Given the following setup

features/multiple_generations.feature

@@ -1,7 +1,7 @@
 Feature: Evolving a grid over multiple generations
-  In order to create a functioning rules engine
-  As a programmer of Conway's Game of Life
-  I can evolve a grid over multiple generations
+  In order to create a functioning rules engine  
+  As a programmer of Conway's Game of Life  
+  I can evolve a grid over multiple generations  
 
   Scenario: Cells come alive, then die off
     Given the following setup
@@ -24,4 +24,3 @@ Feature: Evolving a grid over multiple generations
       | . | x | x | x | . |
       | . | . | . | . | . |
       | . | . | . | . | . |
-

features/static_structures.feature

@@ -1,7 +1,7 @@
 Feature: Cell configurations that are static
-  In order to create a functioning rules engine
-  As a programmer of Conway's Game of Life
-  I can see static structures surviving in my world
+  In order to create a functioning rules engine  
+  As a programmer of Conway's Game of Life  
+  I can see static structures surviving in my world  
 
   Scenario: Block
     Given the following setup

features/support/env.rb

@@ -1,4 +1,4 @@
 $LOAD_PATH.unshift(File.dirname(__FILE__) + '/../../lib')
 require 'game_of_life'
 
-require 'spec/expectations'
+require 'rspec/expectations'

spec/game_of_life_spec.rb

@@ -1,4 +1,4 @@
-require File.expand_path(File.dirname(__FILE__) + '/spec_helper')
+require 'spec_helper'
 
 describe "GameOfLife" do
   it "fails" do

spec/spec_helper.rb

@@ -1,9 +1,16 @@
 $LOAD_PATH.unshift(File.dirname(__FILE__))
 $LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib'))
 require 'game_of_life'
-require 'spec'
-require 'spec/autorun'
-
-Spec::Runner.configure do |config|
+require 'rspec'
+require 'rspec/autorun'
 
+RSpec.configure do |config|
+  # == Mock Framework
+  #
+  # If you prefer to use mocha, flexmock or RR, uncomment the appropriate line:
+  #
+  # config.mock_with :mocha
+  # config.mock_with :flexmock
+  # config.mock_with :rr
+  config.mock_with :rspec
 end