search

nus-cs2103-AY1819S1 / forum

A repo to hold the issue tracker for module discussions
1 stars 1 forks source link

Bugs caused by tampering the XML file directly #193

Open ghost opened 5 years ago

ghost commented 5 years ago

As the title suggests, how do we handle this cases? My group received a couple of bugs where the user tampered with the XML file directly. Example:

image

The tester goes to the XML file to change the completion rate to an invalid value. This is not possible to do through the CLI, as our group provide such no command to directly tamper with completion rate value (it auto updates).

Yes, my group have more mind-blowing bug reports at changing XML other than this.

Refer: nus-cs2103-AY1819S1/pe-results#934

damithc commented 5 years ago

Can the app recover from an incorrect data file? If not, you can accept it as a severity.Low bug and mark all similar bug reports as duplicates. Note: The data file is supposed to be human-editable and this kind of testing is within the scope of system testing