search

shaunlxw / pe

0 stars 0 forks source link

UG undo command: make solution to error more accurate #16

Open shaunlxw opened 4 months ago

shaunlxw commented 4 months ago

For this error "Unable to undo since there were no previously issued commands.", the solution was "Ensure that at least 1 command was previously used before using the undo command". Should be "Ensure that at least 1 command that changed data was previously used before using the undo command", since list and help are counted commands before an undo but will still generate the error.

image.png

nus-se-bot commented 4 months ago

Team's Response

Severity: VeryLow since it is a DG bug and does not affect usage of our app at all.

Items for the Tester to Verify

:question: Issue severity

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

Reason for disagreement: Disagree with the Very Low severity since this issue isn't purely cosmetic and does affect usage of the app. However, can accept severity.Low as it might happen rarely, but usage of app is still affected.

How usage of app is affected:

  1. User inputs find alex
  2. User inputs find john
  3. User attempts undo to try to revert to the find alex view
  4. Error message shown: "Unable to undo since there were no previously issued commands".
  5. User is now unclear of the usage of the undo command since there were previously issued commands (just that they were not commands that changed data).