Add missing unit tests
Closed this issue · 1 comments
A lot of the functionality is covered by intense usage by the project's originator. However, some things should be covered by tests:
(1) Behavior on other systems (missing runtime dependencies, file access rights etc.)
(2) Subtle issues which are not easy to catch, e.g. correctness of the sorting of the choices.
Owing to the small code size and good readability, the behavior can often be inferred "statically", that is, by simply examining the code. Also, the program is under constant usy be its originator. So bugs that are not discovered by the originator are likely to arise from different system configurations. Unit-testing those is very hard. In summary, there is no obvious set of test cases to start with. Only when errors occur, one may write a unit test to control the bug fix.