Open nus-se-script opened 1 year ago
First of all, the expected
part is just to help tester understand what behaviour they should expect from that action, they are never meant to define what the error message should be. These information should be based off the UG.
I do agree with the tester that the error message can be further specified. However, I believe that after reading through our UG, the user can easily understand that the optional field are missing from the error message given.
Thus, the priority of this change is significantly lower than the features we have implemented, and the effort of implementing this does not match the value it provides. This is my reasoning for putting it not in scope.
(Functionality Bug -> Feature flaw : There is no mismatch between the UG and product behaviour thus I changed it to feature flaw instead, as the tester focuses on the specificity of the error message)
--
The DG states that if
add n/Joshua
is entered, an error message 'error message is thrown indicating that compulsory field p/ and e/ are missing'However the error message just states that the format is invalid, and does not mention which fields are missing. It can be implied from reading the rest of the UG and seeing which commands are compulsory, however it would be beneficial to include in the error message!
[original: nus-cs2103-AY2324S1/pe-interim#5939] [original labels: severity.Low type.FunctionalityBug]