Delete feutre has different error messages for the same problem

[yleeyilin]

Steps to reproduce:

• As per the UG, I have inputted delete 0.

Expected:

• I was expecting to get the same error message for both since they are both problems with the fomatting.

Actual:

• However, I got different error message instead and both are worded very differently.
• This is problematic as it might confuse the user as to how they are supposed to fix their input. I think it will be better if both follow the error messages thrown by the delete 0 command since it is more comprehensive.

Screenshots:

[nus-pe-script]

Team's Response

The error messages for delete 0 and delete 100 are correct.

The command delete 0 provides an index of value 0 that does not follow the command format specified in the error message or the user guide that the index has to be a positive integer.

Error message: User guide:

On the other hand, the command delete 100 is following the command format as 100 is a positive integer. Therefore, delete 100 returns an error specifying the invalid index rather than a command format error in delete 0.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: What I meant was that the command error message should be similar. For example, for delete 100:

Invalid index provided! 
delete: Deletes....
Parameters: INDEX (must be a positive integer) 
Example: delete 1 

Consistency in error message handling is key to ensuring user understanding and usability.

Consider the scenario where a user mistypes a command or provides incorrect parameters. If the error message varies significantly from what they're accustomed to, it introduces unnecessary cognitive load as they attempt to decipher the meaning and implications of the error. This not only disrupts the user experience but also undermines the efficiency and effectiveness of the system.

By standardising error messages across commands, users can rely on familiar patterns and structures to interpret and address errors consistently. This not only streamlines the troubleshooting process but also empowers users to navigate the system with confidence and clarity.

By adopting a uniform approach to error messaging, users are better equipped to understand and troubleshoot issues they encounter. Inconsistencies in error messages, such as drastically different formats or levels of detail, can lead to confusion and frustration for users, ultimately hindering their ability to effectively interact with the system.

---