Open imanamirshah opened 7 months ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
No checks for corrupted file, exception is not caught
I corrupted the data file as seen above by removing the
f
from type and a+
from the table. It results in a thrown exception as seen above. File corruption is not handled upon starting of the app.
[original: nus-cs2113-AY2324S2/pe-interim#2375] [original labels: type.FunctionalityBug severity.High]
[This is the team's response to the above 'original' bug]
Dealing with corrupted files is not in the scope of our user task, thus implementing this feature was not part of the task to accomplish. Purposely corrupting the file of course will create a bug if corrupted file detection is not implemented.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
Data file for User A
Data file for User B (corrupted)
Data file for User C
It says here that the active user is A before the exception was thrown and the app crashes. However as seen above, data file for A is not corrupted. Out of all users, only data file for user B is corrupted. However, the app still crashes and is not usable for user A or C.