Chitter Challenge

• 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

Challenge:

As usual please start by forking this repo.

We are going to write a little Twitter clone that will allow the users to post messages to a public stream.

Features:

STRAIGHT UP

As a Maker
So that I can let people know what I am doing  
I want to post a message (peep) to chitter

As a maker
So that I can see what others are saying  
I want to see all peeps in reverse chronological order

As a Maker
So that I can better appreciate the context of a peep
I want to see the time at which it was made

As a Maker
So that I can post messages on Chitter as me
I want to sign up for Chitter

HARDER

As a Maker
So that only I can post messages on Chitter as me
I want to log in to Chitter

As a Maker
So that I can avoid others posting messages on Chitter as me
I want to log out of Chitter

ADVANCED

As a Maker
So that I can stay constantly tapped in to the shouty box of Chitter
I want to receive an email if I am tagged in a Peep

Notes on functionality:

• Drive the creation of your app using tests - either cucumber or rspec as you prefer
• Use data mapper and postgres to save the data.
• You don't have to be logged in to see the peeps.
• Makers sign up to chitter with their email, password, name and a user name (e.g. [email protected], s3cr3t, Samuel Russell Hampden Joseph, tansaku).
• The username and email are unique.
• Peeps (posts to chitter) have the name of the maker and their user handle.
• Use bcrypt to secure the passwords.
• You only can peep if you are logged in.
• Please ensure that you update your README to indicate the technologies used, and give instructions on how to install and run the tests
• Finally submit a pull request before Monday at 9am with your solution or partial solution. However much or little amount of code you wrote please please please submit a pull request before Monday at 9am

Bonus:

If you have time you can implement the following:

• In order to start a conversation as a maker I want to reply to a peep from another maker.

And/Or:

• Work on the css to make it look good (we all like beautiful things).

Good luck and let the chitter begin!

Code Review

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!