initial commit - no meat to the tests yet...

.gitignore

@@ -0,0 +1,40 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+
+game.rb
+.idea
+work.rb

.ruby-gemset

@@ -0,0 +1 @@
+urug_bowling

.ruby-version

@@ -0,0 +1 @@
+ruby-2.3.0

Gemfile

@@ -0,0 +1,9 @@
+# source "https://rubygems.org"
+
+# NOTE:   bundling these gems like this does not work.  It gets an old version
+# of minitest and the reporters and tests won't run.  install the gems from
+# the command line with "gem install minitest"  and "gem install minitest-reporters"
+
+# gem "minitest"
+# gem "minitest-reporters"
+

Gemfile.lock

@@ -0,0 +1,11 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+
+BUNDLED WITH
+   1.15.1

README.md

@@ -0,0 +1,121 @@
+URUG Bowling Game Kata Exercise
+================================
+
+what is a kata?   (from http://codekata.com/)
+---------------------------------------------
+####A kata is an exercise in karate where you repeat a form many, many times, making little improvements in each. 
+
+>There are many exercises and challenges that are used as short katas to help 
+programmers improve their craft.  We are going to use one of Uncle Bob's favorite 
+katas, the bowling game, to gain some experience with TDD and using it for problem 
+solving. This exercise has been designed in a TDD format by utilizing a premade 
+repositor of tests.  Each stage of the kata is tagged in a git repository found 
+at git remote add origin https://github.com/urug/2017_bowling_game.git.  
+
+Pull the repo to your local development environment and checkout the first tag (v0.1).
+You will need to have the minitest and minitest-reporters gem installed.  Run the test suite 
+with "ruby game_test.rb" and go to work to make the test pass.  Once it passes you can refactor
+and then checkout the next tag.  Here is the list of tags:
+
+v0.1 - Initial checkin - all gutter balls
+
+v0.2
+
+v0.3
+
+v0.4
+
+v0.5
+
+v0.6
+
+v1.0 - Game rules fully implemented
+
+With these tests in place you don't even need to know how to score bowling.  In case you're
+interested, here are the rules and an example:
+
+
+>The game consists of 10 frames (or turns) as shown above.  In each 
+frame the player has
+two opportunities to knock down 10 pins.  The score for the frame is the total
+number of pins knocked down, plus bonuses for strikes and spares.
+
+>A spare is when the player knocks down all 10 pins in two tries.  The bonus for
+that frame is the number of pins knocked down by the next roll.  So in frame 3
+above, the score is 10 (the total number knock>>ed down) plus a bonus of 5 (the
+number of pins knocked down on the next roll.)
+
+>A strike is when the player knocks down all 10 pins on his first try.  The bonus
+for that frame is the value of the next two balls rolled.
+
+>In the tenth frame a player who rolls a spare or strike is allowed to 
+roll the extra
+balls to complete the frame.  However no more than three balls can be rolled in
+tenth frame.
+
+##bowling game example:
+####frame 1
+>roll 1:  1<br/>
+>roll 2:  4<br/>
+>score:  5
+
+####frame 2
+>roll 1:  4<br/>
+roll 2:  5<br/>
+score:  14
+
+####frame 3
+>roll 1:  6<br/>
+roll 2:  4 (spare)<br/>
+score:  29
+
+####frame 4
+>roll 1:  5<br/>
+roll 2:  5 (spare)<br/>
+score:  49
+
+####frame 5
+>roll 1:  10 (strike)<br/>
+score:  60
+
+####frame 6
+>roll 1: 0<br/>
+roll 2: 1<br/>
+score: 61
+
+####frame 7
+>roll 1: 7<br/>
+roll 2: 3 (spare)<br/>
+score: 77
+
+####frame 8
+>roll 1: 6<br/>
+roll 2: 4 (spare)<br/>
+score: 97
+
+####frame 9:
+>roll 1: 10 (strike)<br/>
+score: 117
+
+####frame 10:
+>roll 1: 2<br/>
+roll 2: 8 (spare)<br/>
+roll 3: 6
+###score: 133
+
+
+###PROGRAMMING NOTES:
+>1. you may assume that all rolls are valid
+	>>a. no frames will amount to more than 10 pins<br/>
+	>>b. there will be exactly the correct number of rolls made for the 
+	game<br/>
+	>>c. you don't need to account for invalid roll parameters (i.e. 
+	negative numbers etc.)<br/>
+>2. the score method will not be called until all rolls for a game have 
+been made<br/>
+>3. Work in pairs and use TDD to build your solution.  Our tests are 
+using minitest so it will be easiest if you use that in your work.  
+>4. We have supplied the Gemfile that we used to build our solution, 
+this should be all you need to complete the challenge.
+
+##Go for it and have fun!

game_test.rb

@@ -0,0 +1,20 @@
+require './test_helper'
+require './game'
+
+reporter_options = {color: true}
+Minitest::Reporters.use! #[Minitest::Reporters::DefaultReporter.new(reporter_options)]
+
+class GameTest < Minitest::Test
+  def setup
+    @game = Game.new
+  end
+
+  def test_20_rolls_of_0_is_0
+    (1..20).each do |roll|
+      @game.add_roll(0)
+    end
+
+    assert_equal(0, @game.score, "game score wrong for 0 pins")
+  end
+
+end

test_helper.rb

@@ -0,0 +1,3 @@
+require 'minitest/spec'
+require "minitest/autorun"
+require 'minitest/reporters'