Packaging and Unit tests

[rhiever]

From @rasbt:

I think it would be worthwhile to turn TPOT into an importable python module/package and to add unit tests. This would help with the development, especially in collaboration.

For the first public release, I think it would be a big plus to add continuous integration, e.g,. Travis CI (in terms of trustworthiness)

[rhiever]

I'm building some basic unit tests. @rasbt, how should unit tests be written to integrate with Travis CI? Can you lead the way with Travis CI integration?

[rasbt]

Sure, I can deal with the Travis stuff once the unit tests are there. It should be pretty straightforward. You just need to implement the unit tests in a way that they can be executed by e.g., running nosetests from the tpot main directory

[rhiever]

Unit tests are up. Let's see that shmexy Travis CI integration now, @rasbt? :-)

[rasbt]

Okay cool. I will setup the files tonight when I get hope. Should be pretty quick. But you need to do 1 more thing since you are the owner: give travis permission to access your repo for the testing. Just realized there is one little problem: this is a private repo. I am sure that you don't want to pay for travis pro, do you? :D https://travis-ci.com/plans But I see that there is a trial for "pro." Maybe we could use the free trial temporarily until the repo is public and then downgrade? alternatively we could just wait until it's public (but I can already set up the files tonight).

[rhiever]

Well, since the repo is probably going public tomorrow, maybe we'll just set it up then?

[rasbt]

jap okay! I think it's not that urgent anyway. As long as your local unittests pass there is actually no need for travis. It's just a convenience service for users to see if the current dev version is "passing" and if new contributions are "passing". Let's wait until tomorrow then.

[rasbt]

I think we can close this one after merging #19 , #20 and #21