Integration with Travis-CI automated build testing#1
Open
nickponvert wants to merge 17 commits intosjara:masterfrom
Open
Integration with Travis-CI automated build testing#1nickponvert wants to merge 17 commits intosjara:masterfrom
nickponvert wants to merge 17 commits intosjara:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi Santiago,
I have been having a good time playing with the taskontrol code and getting it running on my home machine. I have also been working on integrating my branch with travis-ci, which is an automated build system. Every time I push a new commit to github, travis-ci runs tests on the code (using python-nose) and shows whether or not the build passed all of the tests. I am now in the process of writing more tests, but I am wondering whether you think that this is a good direction for the project as a whole. Using this system, any pull request would also be validated by travis-ci before it is sent to you, so that you would know exactly what type of machine the code runs on and what tests are passed.
I also changed the README to markdown for pretty github formatting and inline images, and I moved several tests into main() functions before switching to nose for testing.
The README for my fork contains a badge that shows the current travis build state:
The URL for the image link will have to be changed for each fork that is synchronized with travis.
Let me know what you think, I hope to see you Monday morning
Nick