README.md in spree-1.3.2 vs README.md in spree-1.3.3

@@ -19,22 +19,21 @@
 
 All of the gems are designed to work together to provide a fully functional e-commerce platform.  It is also possible,
 however, to use only the pieces you are interested in.  So for example, you could use just the barebones spree\_core gem
 and perhaps combine it with your own custom promotion scheme instead of using spree_promo.
 
-[![Build Status](https://secure.travis-ci.org/spree/spree.png?branch=1-3-stable)](https://travis-ci.org/spree/spree)
-[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/spree/spree)
+[![Code Climate](https://codeclimate.com/github/spree/spree.png)](https://codeclimate.com/github/spree/spree)
 
 Installation
 ------------
 
 The fastest way to get started is by using the spree command line tool
 available in the spree gem which will add Spree to an existing Rails application.
 
-    $ gem install rails -v 3.2.11
+    $ gem install rails -v 3.2.13
     $ gem install spree
-    $ rails _3.2.11_ new my_store
+    $ rails _3.2.13_ new my_store
     $ spree install my_store
 
 This will add the Spree gem to your Gemfile, create initializers, copy migrations and
 optionally generate sample products and orders.
 
@@ -157,37 +156,53 @@
 
 
 Running Tests
 -------------
 
-Each gem contains its own series of tests, and for each directory, you need to do a quick one-time
-creation of a test application and then you can use it to run the tests.  For example, to run the
-tests for the core project.
+[![Team City](http://www.jetbrains.com/img/logos/logo_teamcity_small.gif)](http://www.jetbrains.com/teamcity)
 
-    $ cd core
-    $ bundle exec rake test_app
+We use [TeamCity](http://www.jetbrains.com/teamcity/) to run the tests for Spree.
 
-If you're working on multiple facets of Spree, you may want
-to run this command at the root of the Spree project to
-generate test applications for all the facets:
+You can see the build statuses at [http://ci.spreecommerce.com](http://ci.spreecommerce.com/guestLogin.html?guest=1).
 
-    $ bundle exec rake test_app
+---
 
-You can run all of the tests inside a facet by also running
-this command:
+Each gem contains its own series of tests, and for each directory, you need to do a quick one-time
+creation of a test application and then you can use it to run the tests.  For example, to run the
+tests for the core project.
 
-    $ cd core
-    $ bundle exec rake
+```shell
+cd core
+bundle exec rake test_app
+bundle exec rspec spec
+```
 
 If you want to run specs for only a single spec file
+```shell
+bundle exec rspec spec/models/state_spec.rb
+```
 
-    $ bundle exec rspec spec/models/state_spec.rb
-
 If you want to run a particular line of spec
+```shell
+bundle exec rspec spec/models/state_spec.rb:7
+```
 
-    $ bundle exec rspec spec/models/state_spec.rb:7
+You can also enable fail fast in order to stop tests at the first failure
+```shell
+FAIL_FAST=true bundle exec rspec spec/models/state_spec.rb
+```
 
-Travis, the continuous integration service, runs the test suite for each gem one at a time, using the same commands as contained within [`build.sh`](https://github.com/spree/spree/tree/master/build.sh).
+If you want to run the simplecov code coverage report
+```shell
+COVERAGE=true bundle exec rspec spec
+```
+
+If you're working on multiple facets of Spree, you may want
+to run this command at the root of the Spree project to
+generate test applications and run specs for all the facets:
+```shell
+bash build.sh
+```
 
 Contributing
 ------------
 
 Spree is an open source project and we encourage contributions.  Please see the [contributors guidelines](http://spreecommerce.com/documentation/contributing_to_spree.html) before contributing.