soc-se-bot
commented
2 months ago Team's Response
Under QnA for what can be fixed for PED bugs: [Q5] Can we tweak validity checks for a user input, or error/exception handling? A: • Can be allowed only if the current behavior causes the software to misbehave (i.e., crash, give incorrect results, store inconsistent data, or make it unusable for typical users). • Accepting seemingly 'unsuitable' values for an input (e.g., accepting numbers for a person name, empty value as a parameter): This is not considered 'incorrect' (giving more freedom to the user is not necessarily incorrect) unless those unsuitable values causes the application to misbehave. • Accepting supposedly invalid values (e.g., end date is earlier than start date; February 30th) is, while not ideal, not necessarily incorrect either (i.e., adopting a garbage-in garbage-out approach to input validation). However, if such data can make other things go haywire (e.g., crash the app, corrupt the data file), accepting them can be considered a bug, and fixed.
Although the suggestion is valid, the specified invalid input does not cause the product to misbehave, and should not be considered a bug.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
As Prabhat Kumar and Prabhat Kumar are essentially the same thing in terms of name for a person , the Application doesn't enforces such a constraint.
it can potentially affect other features as well , although the internally find is implemented to ignore the whitespaces but its not intuitive for the user , how Prabhat Kumar and Prabhat Kumar are same within this context
Suggestion - disallow inputs with multiple whitespaces or automatically trim the whitespaces and just leave a single white space
Command executed - edit 1 /n Prabhat Kumar