SP13-item01 - code robustification
Milestone ID: 2728
We need to robustify the software for several reasons:
-
R1: be resistant on user's input (user input can easily crash the software for now)
-
R2: be resistant to detectable failures/errors (filesystem problem, network problem, etc..) and either fix the pb or raise it to the caller as an exception. On the top level, exception should provide a usefull error to the user. The goal is "no python backtrace at all"
-
R3: more unitest, the goal is to be close of 100% and maintain the score during time
-
R4: more integration tests on ci.inria.fr
-
R5: early detection with static tools (such as mypy)