More in-depth testing

[weiseng18]

As mentioned in the meeting, our unit tests tend to focus on the correctness of the results, but we do not check what the GUI shows for the corresponding CommandResult or error.

When doing testing for a specific command, try to exhaust the equivalence partitions (either based on the existing unit tests, or from your own creativity), and if you happen to find some new cases, do add them to the unit tests.

Ideally we should test every single command, but I have listed here the non-trivial ones that should definitely get tested:

• [ ] AddCommand
• [ ] DeleteCommand
• [ ] EditCommand
• [ ] FindCommand
• [ ] HelpCommand (somewhat trivial but it accepts params so there is still something to test)
• [ ] Saving and loading (try to be an adversarial user and manually edit the data file)

Others that we may want to add issues for are listed below. These are probably trivial enough

• [ ] ClearCommand
• [ ] ExitCommand
• [ ] ListCommand

[weiseng18]

Possible points for discussion:

• Should we test for the value of the CommandResult inside our unit tests?