Add unitests

[gianpaj]

Big goal, but if this project will continue to grow, which I hope it will, we'll need to have tests in place so we don't brake anything. And also be more confident to try things and don't be scared to break stuff

[rueckstiess]

I know, I know :-)

Do you know a good testing framework? I have used doctests (http://docs.python.org/2/library/doctest.html) before and nose (http://pythontesting.net/framework/nose-introduction/) is popular too.

I imagine we'd have fixed logfiles for a number of versions (1.8, 2.0, 2.2, 2.4 for now) and run the tools over them and compare outputs for each of the arguments.

For tools like mplotqueries and mlaunch we'd actually have to unittest individual methods I suppose?

[rueckstiess]

started adding tests, using nose framework. once I have some more I'll push them into the develop branch.

[gianpaj]

Cool stuff.
Are you keeping track of tasks somewhere? Are you using a Jira project or something?
Or can you simply create a Github issue for example for "Add tests to mlaunch" and then assign it to me/you.

PS: I'll try tomorrow to come in early so we can do 10/15 min video chat ( i'll send you a calendar invite )

[rueckstiess]

The current tests are in the feature-39-tests branch. mlaunch is tested pretty well already (still a few things missing), the other tools also need tests.

[rueckstiess]

I think we can close this issue. All new features should get tests. I will open individual new issues for the tools that are not tested yet.