Coverage below 75%

[plusparth]

This means that only 17% of the code written is being tested by nosetests. The unit tests should be written so that every possibility of input (going into each possible if statement, etc) is covered.

[plusparth]

Apparently that's only for the files that actually have unit tests (there are only 6). This doesn't even cover the files that don't have unit tests written. We need more unit tests.

[plusparth]

Will mark issue as resolved after repository coverage goes above 50% 60% 75% (to set a definite goal for the end of summer)

[physikerwelt]

@DRMF/developers I was skiing two weeks ago, thus I think the milestone "End of summer" should be reached by now;-)
However, as far as I can see the coverage is not increasing anymore
https://coveralls.io/github/DRMF/DRMF-Seeding-Project?branch=master
Can we do something to increase the coverage again.

Given the experience that code had to be rewritten "from the ground up", I think we should focus on high quality code rather than on many lines.

I would like to advocate for the idea of atomic commits. If you have problems to break down the change into small changes (you should try to make at least one commit every time you are in the office) you should probably go back to the drawing board and discuss with others what you want to achieve and how you can break it down to small changes. During this process, you should also define how you can test that the code you added or changed does what it is supposed to do.

While this might seem to be more effort in the first place, it will certainly pay off in the future.