Merge branch 'feature/travis' into develop

.travis.yml

@@ -0,0 +1,12 @@
+language: python
+
+install:
+  - "wget -q -O - http://apt.mopidy.com/mopidy.gpg | sudo apt-key add -"
+  - "sudo wget -q -O /etc/apt/sources.list.d/mopidy.list http://apt.mopidy.com/mopidy.list"
+  - "sudo apt-get update"
+  - "sudo apt-get install $(apt-cache depends mopidy | awk '$2 !~ /mopidy/ {print $2}')"
+
+before_script:
+  - "rm $VIRTUAL_ENV/lib/python$TRAVIS_PYTHON_VERSION/no-global-site-packages.txt"
+
+script: nosetests

README.rst

@@ -2,6 +2,8 @@
 Mopidy
 ******
 
+.. image:: https://secure.travis-ci.org/mopidy/mopidy.png?branch=develop
+
 Mopidy is a music server which can play music from `Spotify
 <http://www.spotify.com/>`_ or from your local hard drive. To search for music
 in Spotify's vast archive, manage playlists, and play music, you can use most

docs/development/contributing.rst

@@ -104,17 +104,26 @@ For more documentation on testing, check out the `nose documentation
 <http://somethingaboutorange.com/mrl/projects/nose/>`_.
 
 
-Continuous integration server
-=============================
+Continuous integration
+======================
 
-We run a continuous integration (CI) server at http://ci.mopidy.com/ that runs
-all test on multiple platforms (Ubuntu, OS X, etc.) for every commit we push to
-GitHub.
+Mopidy uses the free service `Travis CI <http://travis-ci.org/#mopidy/mopidy>`_
+for automatically running the test suite when code is pushed to GitHub. This
+works both for the main Mopidy repo, but also for any forks. This way, any
+contributions to Mopidy through GitHub will automatically be tested by Travis
+CI, and the build status will be visible in the GitHub pull request interface,
+making it easier to evaluate the quality of pull requests.
 
-In addition to running tests, the CI server also gathers coverage statistics
-and uses pylint to check for errors and possible improvements in our code. So,
-if you're out of work, the code coverage and pylint data at the CI server
-should give you a place to start.
+In addition, we run a Jenkins CI server at http://ci.mopidy.com/ that runs all
+test on multiple platforms (Ubuntu, OS X, x86, arm) for every commit we push to
+the ``develop`` branch in the main Mopidy repo on GitHub. Thus, new code isn't
+tested by Jenkins before it is merged into the ``develop`` branch, which is a
+bit late, but good enough to get broad testing before new code is released.
+
+In addition to running tests, the Jenkins CI server also gathers coverage
+statistics and uses pylint to check for errors and possible improvements in our
+code. So, if you're out of work, the code coverage and pylint data at the CI
+server should give you a place to start.
 
 
 Writing documentation

tests/gstreamer_test.py

@@ -12,9 +12,13 @@ from tests import unittest, path_to_data_dir
 class GStreamerTest(unittest.TestCase):
     def setUp(self):
         settings.BACKENDS = ('mopidy.backends.local.LocalBackend',)
+        settings.OUTPUT = 'fakesink'
         self.song_uri = path_to_uri(path_to_data_dir('song1.wav'))
         self.gstreamer = GStreamer()
 
+    def tearDown(self):
+        settings.runtime.clear()
+
     def prepare_uri(self, uri):
         self.gstreamer.prepare_change()
         self.gstreamer.set_uri(uri)