Fixed forking issue

.rspec

@@ -0,0 +1 @@
+--require spec_helper

Gemfile

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# gem "rails"
+
+gem "rspec", "~> 3.12"

Gemfile.lock

@@ -0,0 +1,26 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.5.0)
+    rspec (3.12.0)
+      rspec-core (~> 3.12.0)
+      rspec-expectations (~> 3.12.0)
+      rspec-mocks (~> 3.12.0)
+    rspec-core (3.12.2)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.3)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.5)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-support (3.12.0)
+
+PLATFORMS
+  arm64-darwin-21
+
+DEPENDENCIES
+  rspec (~> 3.12)
+
+BUNDLED WITH
+   2.4.12

lib/scoreboard.rb

@@ -0,0 +1,34 @@
+class Scoreboard
+  def initialize
+    @rolls = [] # array that will store down number of knocked pins after each roll
+    @current_roll = 0 #to keep track of the current roll. Initalising means it is ready to take information so it 
+    # can calculate the score
+  end
+
+  def roll(pins)
+    @rolls[@current_roll] = pins
+    @current_roll += 1
+  end
+
+  def score
+    total_score = 0 
+    roll_number = 0
+    10.times do
+      if @rolls[roll_number] == 10 # FOR A STRIKE
+        total_score += 10 + @rolls[roll_number + 1] + @rolls[roll_number + 2]
+        roll_number += 1
+      elsif @rolls[roll_number] + @rolls[roll_number + 1] == 10 # STRIKE
+        total_score += 10 + @rolls[roll_number + 2]
+        roll_number += 2
+      else
+        total_score += @rolls[roll_number] + @rolls[roll_number + 1] # frame 
+        roll_number += 2
+      end
+    end
+    return total_score
+  end
+
+  def gutter(roll_number)
+    return @rolls[roll_number] == 0
+  end
+end

spec/scoreboard_spec.rb

@@ -0,0 +1,43 @@
+require 'scoreboard'
+
+
+# Define a method roll(pins) 
+# that takes in the number of pins knocked down in a roll and adds it to the @rolls array.
+
+RSpec.describe do
+  context 'player never hits a pin(20 zero scores)' do
+    it 'is a gutter game' do
+      game = Scoreboard.new
+      rolls = [0] * 20
+      rolls.each { |pins| game.roll(pins) }
+      expect(game.score).to eq(0)
+    end
+  end
+
+  context 'Perfect Game' do
+    it 'scores 300' do
+      game = Scoreboard.new
+      rolls = [10] * 12
+      rolls.each { |pins| game.roll(pins) }
+      expect(game.score).to eq(300)
+    end
+  end
+
+  context '10th frame with strike' do
+    it 'allows for two extra rols and adds the next two rolls as a bonus' do
+      game = Scoreboard.new
+      rolls = [0] * 18 + [10, 3, 4]
+      rolls.each { |pins| game.roll(pins) }
+      expect(game.score).to eq(17)
+    end
+  end
+
+  context '10th frame with only one strike' do
+    it 'one extra roll used as bonus' do
+      game = Scoreboard.new
+      rolls = [0] * 18 + [5, 5, 3]
+      rolls.each { |pins| game.roll(pins) }
+      expect(game.score).to eq(13)
+    end
+  end
+end

spec/spec_helper.rb

@@ -0,0 +1,98 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See https://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  # https://rspec.info/features/3-12/rspec-core/configuration/zero-monkey-patching-mode/
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end