Create unit-tests for weather components
In order to make current work and future integration as stable and seamless as possible, we should cover all code by unit-tests.
To start with, we could begin with a test suite containing all re-written components and move towards full coverage once the integration is stable.
Unless any team member has prior experience with testing Python/Django applications ([[https://nose.readthedocs.org/en/latest/|Nose]] looks promising), I suggest we stick with Python's [[http://docs.python.org/2/library/unittest.html|unittest]]-module for the following reasons: a) preferred way of [Django] b) part of batteries-included Python - no extra installation necessary, which lends itself well to portability
Measuring code coverage and performing CI could be possible next steps.