Valeria bowling_ruby incomplete

.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.1)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.4)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-support (3.12.0)
+
+PLATFORMS
+  x86_64-darwin-22
+
+DEPENDENCIES
+  rspec (~> 3.12)
+
+BUNDLED WITH
+   2.4.8

classes_recipe.md

@@ -0,0 +1,89 @@
+Bowling Multi-Class Planned Design Recipe
+1. Describe the Problem
+Put or write the user story here. Add any clarifying notes you might have.
+
+2. Design the Class System
+Consider diagramming out the classes and their relationships. Take care to focus on the details you see as important, not everything. The diagram below uses asciiflow.com but you could also use excalidraw.com, draw.io, or miro.com
+
+
+Also design the interface of each class in more detail.
+
+class Frame
+  def initialize(number, io)
+    # number is an integer
+
+  end
+
+  def print_number
+    # prints frame number
+  end
+end
+class Roll
+  def initialize(number, io)
+  end
+
+  def print_number
+    # prints frame number
+  end
+
+  def ask_for_pins
+    # makes a puts
+  end
+
+  def get_pins
+    # asks for input
+  end
+end
+
+class Game
+  def initialize
+  end
+
+  def run_game
+    # runs the game
+  end
+end
+
+class Frame10
+  def initialize
+    # child of Frame
+  end
+end
+
+class Score
+  def initialize(score)
+    # score is an int
+  end
+  def calculate_score
+  end
+  def print_score
+  end
+end
+
+
+
+3. Create Examples as Integration Tests
+Create examples of the classes being used together in different situations and combinations that reflect the ways in which the system will be used.
+
+# EXAMPLE
+
+# Gets all tracks
+library = MusicLibrary.new
+track_1 = Track.new("Carte Blanche", "Veracocha")
+track_2 = Track.new("Synaesthesia", "The Thrillseekers")
+library.add(track_1)
+library.add(track_2)
+library.all # => [track_1, track_2]
+4. Create Examples as Unit Tests
+Create examples, where appropriate, of the behaviour of each relevant class at a more granular level of detail.
+
+# EXAMPLE
+
+# Constructs a track
+track = Track.new("Carte Blanche", "Veracocha")
+track.title # => "Carte Blanche"
+Encode each example as a test. You can add to the above list as you go.
+
+5. Implement the Behaviour
+After each test you write, follow the test-driving process of red, green, refactor to implement the behaviour.
+

lib/frame.rb

@@ -0,0 +1,14 @@
+class Frame
+  def initialize(number, io)
+    @number = number
+    @io = io
+  end
+
+  def print_number
+    @io.puts "Frame #{@number}"
+  end
+end
+
+
+#frame = Frame.new(2, Kernel)
+#frame.print_number

lib/roll.rb

@@ -0,0 +1,26 @@
+class Roll
+  def initialize(number, io)
+    @number = number
+    @io = io
+  end
+
+  def print_number
+    @io.puts "Roll #{@number}"
+  end
+
+  def ask_for_pins
+    @io.puts "Insert number of pins"
+  end
+
+  def get_pins
+    input = @io.gets.chomp.to_i
+    if input < 1 || input > 10
+      fail "Invalid number"
+    end
+    return input
+  end
+end
+
+
+#roll = Roll.new(1, Kernel)
+#roll.print_number

spec/frame_spec.rb

@@ -0,0 +1,14 @@
+require 'frame'
+
+describe Frame do
+  it 'prints its number' do
+    io = double :io
+    frame = Frame.new(1, io)
+    expect(io).to receive(:puts).with("Frame 1")
+
+    frame.print_number
+
+  end
+end
+
+

spec/roll_spec.rb

@@ -0,0 +1,33 @@
+require 'roll'
+
+describe Roll do
+  it 'prints its number' do
+    io = double :io
+    roll = Roll.new(1, io)
+    expect(io).to receive(:puts).with("Roll 1")
+
+    roll.print_number
+  end
+
+  it 'asks for user input' do
+    io = double :io
+    roll = Roll.new(1, io)
+    expect(io).to receive(:puts).with("Insert number of pins")
+    roll.ask_for_pins
+  end
+
+  it 'gets user input' do
+    io = double :io
+    roll = Roll.new(1, io)
+    expect(io).to receive(:gets).and_return("2")
+    expect(roll.get_pins).to eq(2)
+  end
+
+  it 'fails with invalid input' do
+    io = double :io
+    roll = Roll.new(1, io)
+    expect(io).to receive(:gets).and_return("11")
+    expect { roll.get_pins }.to raise_error "Invalid number"
+
+  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://relishapp.com/rspec/rspec-core/docs/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