Enable continuous integration with travis-ci. #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the number of contributors increase, it becomes more important to make sure that everyone is able to get started quickly on a clean slate, where 'clean' is defined by the unit tests and integration tests. It also avoids "but it runs on my machine!" scenarios. This pull request adds a travis configuration file which instructs travis-ci to run the tests. A badge indicating the status is included in the README. Rails is a great example of a project using travis successfully.
Note that you will need to enable github to notify travis whenever a push is made.
At this point, it appears that py2.6 doesn't work too well with
expectFailures
, and that some of the integration tests are failing. I would like to have your help with these.