Hi! I cleaned up your code for you!

README

@@ -9,10 +9,10 @@ Work in Ruby on Rails development? Great! Interviewing you just because a little
   5. Branching master with a good description name
   6. Writing an integration test to help prevent the error from happening again
   7. Committing the work and merging it back into master
-  
-  = Depending on how they handle writing tests 
+
+  = Depending on how they handle writing tests
   1. Create a new story for adding comments to a fruit (without a plugin please)
   2. Implementing the story with correct branches
   3. Optimising the queries to help make the app fast
-  
+
 Ideally the further they get along the more they know about Rails, feel free to fork this and extend.

app/models/fruit.rb

@@ -1,5 +1,5 @@
 class Fruit < ActiveRecord::Base
 
   validates_presence_of :name
-  
+
 end

config/initializers/inflections.rb

@@ -1,6 +1,6 @@
 # Be sure to restart your server when you modify this file.
 
-# Add new inflection rules using the following format 
+# Add new inflection rules using the following format
 # (all these examples are active by default):
 # ActiveSupport::Inflector.inflections do |inflect|
 #   inflect.plural /^(ox)$/i, '\1en'

config/initializers/session_store.rb

@@ -2,7 +2,7 @@
 
 # Your secret key for verifying cookie session data integrity.
 # If you change this key, all old sessions will become invalid!
-# Make sure the secret is at least 30 characters and all random, 
+# Make sure the secret is at least 30 characters and all random,
 # no regular words or you'll be exposed to dictionary attacks.
 ActionController::Base.session = {
   :key         => '_job-interview_session',

db/schema.rb

@@ -1,4 +1,4 @@
-# This file is auto-generated from the current state of the database. Instead of editing this file, 
+# This file is auto-generated from the current state of the database. Instead of editing this file,
 # please use the migrations feature of Active Record to incrementally modify your database, and
 # then regenerate this schema definition.
 #

db/seeds.rb

@@ -2,6 +2,6 @@
 # The data can then be loaded with the rake db:seed (or created alongside the db with db:setup).
 #
 # Examples:
-#   
+#
 #   cities = City.create([{ :name => 'Chicago' }, { :name => 'Copenhagen' }])
 #   Major.create(:name => 'Daley', :city => cities.first)

test/test_helper.rb

@@ -16,7 +16,7 @@ class ActiveSupport::TestCase
   # don't care one way or the other, switching from MyISAM to InnoDB tables
   # is recommended.
   #
-  # The only drawback to using transactional fixtures is when you actually 
+  # The only drawback to using transactional fixtures is when you actually
   # need to test transactions.  Since your test is bracketed by a transaction,
   # any transactions started in your code will be automatically rolled back.
   self.use_transactional_fixtures = true