Write a testing plan

[mauigna06]

Define a testing plan. For example:

• a normal use case will be tested and expected outputs will be achieved (e.g. using the released test data)
• have more than one valid test case (e.g. at least two more are needed)
• parameter domains are limited to real, expected and valid values (e.g. parameters on the VSP or on the boxes creation)
• flow diagram with returns to previous parts of the module (e.g. using different vertical sections)
• if possible test all different behaviors (e.g. all checkboxes combinations on the VSP work well)
• guess user errors to find bad GUI

The earlier list most probably is not complete and needs more thought but it's a good place to start