nus-se-bot
commented
2 years ago Team's Response
Since the input data is provided by the user, this would mean they already have a copy of it somewhere (perhaps from the CTF website) and therefore, it does not make sense for Decodex to keep a copy of it.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: Even though the input data is input by the user, it would still be useful to have the input data be saved such that when the user reenters the application, to continue working on the data, that they need not reenter the data again. Thus saving the user the hassle of reentering data and making the user experience more fluid and smooth. If a user were to be working on the same piece of data on and off, having the data be saved within the application itself would save the user much trouble and not cause him or her this occasional inconvenience.
In fact, the User Guide itself has this feature in the User Stories, where it was supposed to be in the version 2.0 release and was stated to have a 2 Star ** priority. I have reported this as a bug and the team has accepted it as such with the response being "The feature was not implemented and was planned for future iterations". Since the feature was meant to be implemented in the future, the statement "it does not make sense for Decodex to keep a copy of it" fundamentally goes against what you have said in a separate bug report, and there seems to be conflicting opinions even within the team itself.
The input data that is currently in the app will not be saved and loaded upon rebooting Decodex. The data should be saved so that if the app crashes or if we need the data again we do not need to keep reentering the input data.