chydarren / pe

0 stars 0 forks source link

File entry not loaded into application but user is not informed of the issue #5

Open chydarren opened 2 years ago

chydarren commented 2 years ago

I corrupted the third line of the file by adding an extra flight number. Thankfully, the application managed to handle this error by not allowing the input totally into the application so that there is no crash. However, they did not mention that the line is not loaded into the application, and the user may not be aware of this issue.

2022-11-11 (9).png

nus-pe-script commented 2 years ago

Team's Response

Corrupted data is deleted.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: As the team has considered to delete the file entry if it is corrupted, and is caught as shown above, the correct message should be displayed to inform the user of the error that has been caught, and that the file entry has been deleted.

As per the below module guideline, I believe that the above is a feature that they have included in v2.1 (i.e. to delete incorrect file entries), and hence they should inform the user that the file entry has been deleted. If the user is not informed, that means there is a compromise of integrity on the data within the application.

2022-11-15 (4).png