bdthanh / pe Goto Github PK

Instructions for Manual Testing need to
demonstrate some commands that cause errors, so that developers could manually test the exception handling

The class diagram could be better reformat:

The message should be more specific why it is invalid (e.g: contain ;). This error makes user confuse and they wouldn'e know how to fix it

Should have a line to separate after error messages and the next input

Should explain why the timing is invalid for user to fix

Because it is too complicated, user will be hard to read and get any information from that diagram. Shoud use ref to simplify the diagrams and make a sub-diagram for reference:

There are over 2000 entries so list all of modules in one go is not easy for user to find the module the want. Suggestion: Could do some pagination e.g: 50 or 100 module in one page

The Ui diagram is unnecessary since it doesn't show any relation with other classes, it just shows the methods

User incorrectly edit a file and cause error, and you delete all data of that university then, user have to input all again, which is time-comsuming. You can ask user to edit it again until it is correct or delete only that line and other line that related to that corrupted line instead of force-deleting all data of that university.

Instead of inputing the whole university name (there are some univerities with very long names), user should be able to use the index of that university in the list

If there is no favourite uni, you should print a difference message

Since the add comment command need to use {. You can't say that user should not use invalid character {

Storage should detect the error line and delete it

CommandType should have enum notation:

UG should mention that command is case-sensitive and which part requires to input in capita letters

I did all steps from 1-8 in Instructions for Manual Testing and run add comment in step 9 but it is not working