Application does not fail gracefully when save file is read-only

[Chang-CH]

Steps to reproduce

1. Set save file to read only
2. Use any command that edits the save file, such as add

Expected

• App shows an error message indicating why the error occurred, or how to fix the error

Actual

This could happen to users who either log in as a user with no write permissions, or when a parent directory has been set to read only. While this should not happen often, the user will not be able to use the app when it does, and no troubleshooting help is provided.

[nus-pe-bot]

Team's Response

This situation, as mentioned by the tester, is rare, and additionally, the error message is more than enough for the user to debug the issue. (that the file cannot be written to)

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: - NotInScope relates to features that are not yet implemented. File saving is an already implemented feature.

• As per PE guidelines, having error messages, or faq sections for files not being able to save should be trivial.

• Dev team states that the error message is more than enough for the user to debug. There can be various reasons why the file could not be saved, relying on a Java exception should not be enough, even CS students sometime have trouble debugging exceptions, much less F&B managers.

---

:question: Issue severity

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

• [x] I disagree

Reason for disagreement: - If the user is unable to troubleshoot the software they will not be able to make any modifications to the data (add, delete, edit, ...). This seems more than a minor inconvenience only per the requirements for severity Low.

---