RPS Challenge

Progress

###Planning

###Part 1 - Name registration page

User Story:

I would like to register my name before playing an online game

Required elements:

• Welcome headers.
• "Please enter name" header.
• Input form
• Submit button

Input: Output: Name New page that confirms name Submit

###Part 2 - /Play page that will host the options

I would like to be able to play rock/paper/scissors

Require elements:

• Game description headers
• Select options for separate rock, paper and scissors options

Input: Output: Rock Rock,Paper,Scissors - You win or you lose Paper Scissors

Game Logic / Page layout

If Rock - Paper: Lose Scissors: Win If Paper - Scissors: Lose Rock: Win If Scissors - Rock: Lose Paper: Win

Ver.1 Idea

When a player clicks on a button on the play page, it takes the user to a page specific for that play. /rock, /paper, /scissors. On that page, there will be 2 randomized strings using .sample to control them. And the user will see their selection, the computer's selection and the win/lose statment.

###Project Progress so far.

Step 1 - Setup gems and installed bundles. Created files such as the App.rb, config and first spec test. I also included the rack env requirement for my tests to pass in the spec helper. I've written my first test and created an index.erb to create the page and pass my first test which is a simple test to display the main header for the page.

Step 2 - I've now created the buttons and created a new /play page that will take the contents of the filled form into the following page. I've written a test to expect the user's name to be taken to the next page and passed this.

Step 3 - A test was written to allow the user to see an output on the rock button press. This was written and the functionality of a random win/lose scenario was built in using strings and the .sample to make this functionality work. Whilst this is a static setting, given more time, I would like this to be dynamic and not controlled by strings.

Step 4 - Tried to write tests for win/lose scenarios but ran out of time.

Tests created: 12 Tests passed: 9 Test Coverage so far: 100%

###Things I would like to continue to work on

I'd like to continue working on this to make the tests work as well as add in the extra rules and players. I would also like to try and learn how to shorten my code in my app.rb so I wouldn't have things like my .sample methods in the main body of app.rb.

Instructions

• Challenge time: rest of the day and weekend, until Monday 9am
• 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

Task

Knowing how to build web applications is getting us almost there as web developers!

The Makers Academy Marketing Array ( MAMA ) have asked us to provide a game for them. Their daily grind is pretty tough and they need time to steam a little.

Your task is to provide a Rock, Paper, Scissors game for them so they can play on the web with the following user stories:

As a marketeer
So that I can see my name in lights
I would like to register my name before playing an online game

As a marketeer
So that I can enjoy myself away from the daily grind
I would like to be able to play rock/paper/scissors

Hints on functionality

• the marketeer should be able to enter their name before the game
• the marketeer will be presented the choices (rock, paper and scissors)
• the marketeer can choose one option
• 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

Bonus level 1: Multiplayer

Change the game so that two marketeers can play against each other ( yes there are two of them ).

Bonus level 2: Rock, Paper, Scissors, Spock, Lizard

Use the special rules ( you can find them here http://en.wikipedia.org/wiki/Rock-paper-scissors-lizard-Spock )

Basic Rules

• Rock beats Scissors
• Scissors beats Paper
• Paper beats Rock

In code review we'll be hoping to see:

• All tests passing
• High Test coverage (>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. Referring to this rubric in advance may make the challenge somewhat easier. You should be the judge of how much challenge you want this weekend.

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:

require 'simplecov'
require 'simplecov-console'

SimpleCov.formatter = SimpleCov::Formatter::MultiFormatter.new([
  SimpleCov::Formatter::Console,
  # Want a nice code coverage website? Uncomment this next line!
  # SimpleCov::Formatter::HTMLFormatter
])
SimpleCov.start

You can see your test coverage when you run your tests. If you want this in a graphical form, uncomment the HTMLFormatter line and see what happens!