Invalid input during list command

[b1inmeister]

When I input a String when the program asks for the numbers of transactions to show during the list command, I expected the program to respond with an error message, and then allow me to try inputting the number of transactions again. However, from the screenshot below, the execution of the list command terminates instead and I am back to the beginning, when I input the command. I feel this is inefficient, as I need to go through the process of typing list and inputting all the different fields needed for the list command.

[nus-pe-script]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for raising this issue and for providing a clear explanation along with a helpful screenshot.

We acknowledge that the current implementation of the list command does not allow the user to re-enter a valid input if a non-numeric string is entered when prompted for the number of transactions. Instead, the command terminates and returns to the main command prompt. We understand how this may feel unintuitive and disrupt the user flow slightly.

Severity Classification

We have accepted this as a valid functionality bug and classified it as severity.Low based on the following considerations:

• The issue does not impact core functionality. Users can still execute the list command again without loss of data.
• There is no crash, corruption, or irreversible behavior.
• The inconvenience is minor and only affects the flow of interaction rather than functionality itself.

Low severity: A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.

Future Considerations

We agree that improving input validation and allowing users to correct their input in-line would improve usability. This will be considered for future refinements to enhance the overall user experience.

Conclusion

We appreciate your feedback and the effort taken to document this behavior. Your input helps us improve the quality and robustness of our application.

Items for the Tester to Verify

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: [replace this with your explanation]

---