Stevie Spiegl RPS

CONTRIBUTING.md

@@ -1,24 +1,20 @@
-Tech Test Submission Requirements/Guidelines
-======
+# Tech Test Submission Requirements/Guidelines
 
 Before submitting your test, please review the requirements/guidelines belows. Note that the requirements are mandatory and if you do not satisfy them we won't review your code (we don't mean to be harsh but this is based on the minimum expectations that our hiring partners require when you submit code for tech tests).
 
-Requirements
-------
+## Requirements
 
-* We use [Hound CI](https://houndci.com/) to check for violations to our style guide. When you submit your Pull Request, please then check over and correct everything that Hound has sniffed out that is wrong with your code (unless you feel you really can't do anything to fix it). Once you've fixed Hound errors, push your code again and the Pull Request should update automatically.
-* Make sure you have written your own README that briefly explains your approach to solving the challenge.
-* If your code isn't finished it's not ideal but acceptable as long as you explain in your README where you got to and how you would plan to finish the challenge.
-* All code must be written test-first - we're looking for 100% test coverage or as near as possible to that figure.
-* Ensure all your tests are passing.
+- We use [Hound CI](https://houndci.com/) to check for violations to our style guide. When you submit your Pull Request, please then check over and correct everything that Hound has sniffed out that is wrong with your code (unless you feel you really can't do anything to fix it). Once you've fixed Hound errors, push your code again and the Pull Request should update automatically.
+- Make sure you have written your own README that briefly explains your approach to solving the challenge.
+- If your code isn't finished it's not ideal but acceptable as long as you explain in your README where you got to and how you would plan to finish the challenge.
+- All code must be written test-first - we're looking for 100% test coverage or as near as possible to that figure.
+- Ensure all your tests are passing.
 
-Desirable
--------
+## Desirable
 
-* Set up [Travis CI](https://travis-ci.org/) on your own repo and add a [status badge](http://docs.travis-ci.com/user/status-images/) to your README showing that all tests are passing - and make sure it passes our own CI when you submit your PR.
+- Set up [Travis CI](https://travis-ci.org/) on your own repo and add a [status badge](http://docs.travis-ci.com/user/status-images/) to your README showing that all tests are passing - and make sure it passes our own CI when you submit your PR.
 
-Guidelines
--------
+## Guidelines
 
-* Ensure you've understood the specification and built the code according to the challenge guidelines.
-* Read through [Code Reviews :pill:](https://github.com/makersacademy/course/blob/main/pills/code_reviews.md) to understand what we're looking for in your code.
+- Ensure you've understood the specification and built the code according to the challenge guidelines.
+- Read through [Code Reviews :pill:](https://github.com/makersacademy/course/blob/main/pills/code_reviews.md) to understand what we're looking for in your code.

Gemfile

@@ -3,14 +3,28 @@ source 'https://rubygems.org'
 ruby '3.0.2'
 
 gem 'sinatra'
+gem 'sinatra-contrib'
+gem 'webrick'
+gem 'puma'
+gem 'rack'
 
 group :test do
   gem 'capybara'
   gem 'rspec'
+  gem 'pg'
   gem 'simplecov', require: false
   gem 'simplecov-console', require: false
 end
 
 group :development, :test do
   gem 'rubocop', '1.20'
+  gem 'sinatra'
+  gem 'sinatra-contrib'
+  gem 'rack'
+  gem 'webrick'
+  gem 'launchy'
+end
+
+group :production do
+  gem 'pg'
 end

Gemfile.lock

@@ -15,17 +15,24 @@ GEM
       xpath (~> 3.2)
     diff-lcs (1.4.4)
     docile (1.4.0)
+    launchy (2.5.0)
+      addressable (~> 2.7)
     mini_mime (1.1.1)
     mini_portile2 (2.6.1)
+    multi_json (1.15.0)
     mustermann (1.1.1)
       ruby2_keywords (~> 0.0.1)
+    nio4r (2.5.8)
     nokogiri (1.12.3)
       mini_portile2 (~> 2.6.1)
       racc (~> 1.4)
     parallel (1.20.1)
     parser (3.0.2.0)
       ast (~> 2.4.1)
+    pg (1.4.1)
     public_suffix (4.0.6)
+    puma (5.6.4)
+      nio4r (~> 2.0)
     racc (1.5.2)
     rack (2.2.3)
     rack-protection (2.1.0)
@@ -76,10 +83,17 @@ GEM
       rack (~> 2.2)
       rack-protection (= 2.1.0)
       tilt (~> 2.0)
+    sinatra-contrib (2.1.0)
+      multi_json
+      mustermann (~> 1.0)
+      rack-protection (= 2.1.0)
+      sinatra (= 2.1.0)
+      tilt (~> 2.0)
     terminal-table (3.0.1)
       unicode-display_width (>= 1.1.1, < 3)
     tilt (2.0.10)
     unicode-display_width (2.0.0)
+    webrick (1.7.0)
     xpath (3.2.0)
       nokogiri (~> 1.8)
 
@@ -88,14 +102,20 @@ PLATFORMS
 
 DEPENDENCIES
   capybara
+  launchy
+  pg
+  puma
+  rack
   rspec
   rubocop (= 1.20)
   simplecov
   simplecov-console
   sinatra
+  sinatra-contrib
+  webrick
 
 RUBY VERSION
    ruby 3.0.2p107
 
 BUNDLED WITH
-   2.2.26
+   2.3.15

Procfile

@@ -0,0 +1 @@
+web: bundle exec rackup config.ru -p $PORT

README.md

@@ -1,15 +1,42 @@
 # RPS Challenge
 
-Instructions
--------
+# <a href="https://rock-paper-spiegl.herokuapp.com/">Play the deployed app here!!!</a> 
+<!-- ## App currently down while I implement database - 8/8/22 -->
 
-* Feel free to use google, your notes, books, etc. but work on your own
-* If you refer to the solution of another coach or student, please put a link to that in your README
-* If you have a partial solution, **still check in a partial solution**
-* You must submit a pull request to this repo with your code by 9am Monday morning
+### If you'd still rather play it locally, do the following:
 
-Task
-----
+- clone this repo
+- run ```bundler``` to install dependencies
+- run ```rackup```
+- navigate to the port specified by rackup
+- choose wisely...
+- (the game keeps track of your score - updated videos to follow)
+
+
+## Enter your name
+
+
+
+https://user-images.githubusercontent.com/98267087/182941868-333978af-56bf-47ae-a9c7-510ac6216a22.mov
+
+## Choose an option...
+
+https://user-images.githubusercontent.com/98267087/182941875-07bc66aa-8a57-423f-90fa-2e8c4dab266f.mov
+
+## Choose another option...
+
+https://user-images.githubusercontent.com/98267087/182941881-57eba3fc-45fd-4988-84dc-6498bbdd9ec8.mov
+
+## Choose another option...
+
+https://user-images.githubusercontent.com/98267087/182941887-f2594826-201f-49d5-aff8-25ef4432662f.mov
+
+
+## Further steps
+- a login, with a database to keep scores
+- different images/messages depending on what the outcome is
+
+## Task
 
 Knowing how to build web applications is getting us almost there as web developers!
 
@@ -35,11 +62,10 @@ Hints on functionality
 - the game will choose a random option
 - a winner will be declared
 
-
 As usual please start by
 
-* Forking this repo
-* TEST driving development of your app
+- Forking this repo
+- TEST driving development of your app
 
 [You may find this guide to setting up a new Ruby web project helpful.](https://github.com/makersacademy/course/blob/main/pills/ruby_web_project_setup_list.md)
 
@@ -59,14 +85,13 @@ Use the _special_ rules ( _you can find them here http://en.wikipedia.org/wiki/R
 
 In code review we'll be hoping to see:
 
-* All tests passing
-* High [Test coverage](https://github.com/makersacademy/course/blob/main/pills/test_coverage.md) (>95% is good)
-* The code is elegant: every class has a clear responsibility, methods are short etc.
+- All tests passing
+- High [Test coverage](https://github.com/makersacademy/course/blob/main/pills/test_coverage.md) (>95% is good)
+- The code is elegant: every class has a clear responsibility, methods are short etc.
 
-Reviewers will potentially be using this [code review rubric](docs/review.md).  Referring to this rubric in advance may make the challenge somewhat easier.  You should be the judge of how much challenge you want this at this moment.
+Reviewers will potentially be using this [code review rubric](docs/review.md). Referring to this rubric in advance may make the challenge somewhat easier. You should be the judge of how much challenge you want this at this moment.
 
-Notes on test coverage
-----------------------
+## Notes on test coverage
 
 Please ensure you have the following **AT THE TOP** of your spec_helper.rb in order to have test coverage stats generated
 on your pull request:

app.rb

@@ -0,0 +1,48 @@
+require 'sinatra/base'
+require 'sinatra/reloader'
+require './lib/player'
+require './lib/round'
+require './lib/game'
+# require './database_connection_setup'
+
+class RockPaperScissors < Sinatra::Base
+  configure :development do
+    register Sinatra::Reloader
+  end
+
+  enable :sessions
+
+  get '/' do
+    $game = Game.new
+    erb :form
+  end
+
+  post '/play' do
+    session[:player] = params[:player]
+    $player = Player.new(params[:player])
+    @player_name = $player.name
+    @game = $game
+    erb :play
+  end
+
+  post '/play_again' do
+    # session[:player] = params[:player]
+    # $player = Player.new(params[:player])
+    # @player_name = $player.name
+    @game = $game
+    erb :play_again
+
+  end
+
+  post '/battle' do
+    @player = $player
+    @player_weapon = @player.select_weapon(params[:player_choice])
+    round = Round.new(@player_weapon, $game)
+    @message = round.engine
+    @computer_weapon = round.computer_weapon
+    erb :battle
+  end
+
+# Start the server if this file is executed directly (don't change the line below)
+  run! if app_file == $0
+end

config.ru

@@ -0,0 +1,2 @@
+require_relative 'app'
+run RockPaperScissors

database_connection_setup.rb

@@ -0,0 +1,7 @@
+require './lib/database_connection'
+
+if ENV['RACK_ENV'] == 'test'
+  DatabaseConnection.setup('rps_test')
+else
+  DatabaseConnection.setup('rps')
+end

db/migrations/01_create_databases.sql

@@ -0,0 +1,3 @@
+CREATE DATABASE rps;
+
+CREATE DATABASE rps_test;

db/migrations/02_create_tables.sql

@@ -0,0 +1,7 @@
+CREATE TABLE scores (id SERIAL PRIMARY KEY, won INT, drew INT, lost INT);
+INSERT INTO scores (won, drew, lost) VALUES(0, 0, 0);
+
+
+-- CREATE TABLE users (id SERIAL PRIMARY KEY, username VARCHAR(30));
+
+-- CREATE TABLE spaces (id SERIAL PRIMARY KEY, name_of_space VARCHAR(100), available BOOLEAN, user_id INT, description VARCHAR(240), price_per_night INT);