README.markdown in spud_photos-0.1.5 vs README.markdown in spud_photos-0.9.0

@@ -28,11 +28,11 @@
 	    :small => '50x50#',
 	    :medium => '200x200#',
 	    :large => '400x400#',
 	    :huge => '600x600'
 	  }
-	  self.paperclip_storage = :filesystem #use :s3 to use s3 storage (aws gem required)
+	  config.paperclip_storage = :filesystem #use :s3 to use s3 storage (aws gem required)
     	  config.s3_credentials = "#{Rails.root}/config/s3.yml"
     	  config.storage_path = ":rails_root/public/system/spud_photos/:id/:style/:basename.:extension"
     	  config.storage_url = "/system/spud_photos/:id/:style/:basename.:extension"
 	end
 
@@ -50,6 +50,26 @@
 
 __NOTE:__ The built-in views are likely to undergo changes as features are added to the photos engine. If a new version of Spud Photos does not play nicely with your customized views, try backing up your views to an alternate location and running the views generator again to see what has changed. 
 
 
 [1]:https://github.com/davydotcom/spud_core_admin
-[2]:https://github.com/thoughtbot/paperclip
+[2]:https://github.com/thoughtbot/paperclip
+
+Testing
+-----------------
+
+Spud uses RSpec for testing. Get the tests running with a few short commands:
+
+1. Create and migrate the databases:
+   
+        rake db:create
+        rake db:migrate
+
+2. Load the schema in to the test database:
+
+        rake app:db:test:prepare
+
+3. Run the tests with RSpec
+
+        rspec spec
+
+After the tests have completed the current code coverage stats is available by opening ```/coverage/index.html``` in a browser.
\ No newline at end of file