Create unit tests to verify code coverage

[mpourmpoulis]

the previous days I have finally gotten around to setting up Travis CI for the project starting with pylint and the next step is to include unit tests in the integration. Unfortunately, because the Python interpreter is embedded in sublime and I outsource a couple of things to the sublime, setting up of those unit tests requires solving various technicalities so it will happen gradually.

As a start, I should probably start with unit tests for the library folder, is it these essentially sublime free, and in particular tests regarding the ability (of the repair module) to recover from errors and parse code. For the purpose, I think I should try to collect samples of code for three different tasks

• Code that contains errors, that it is essential to be able to recover from, and failure to do so would imply there is a bug in the code and the travis build should fail

• Code with errors, it would be nice to support but not really hard line for the moment. Failure should be reported but should not cause the Travis build to fail

• Correct Code, that the repair module should not break