nus-se-script
commented
9 months ago Team's Response
In the normal use of the application, there is little to no situation where a user will open more than one application. Hence we believe that it is not in scope
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: From the website for notinscope: In addition, the following (at least one) need to be satisfied: The UG specifies it as not supported or coming in a future version. The user cannot attempt to use the missing feature or when the user does so, the software fails gracefully, possibly with a suitable error message i.e., the software should not crash.
This issue was not supported anywhere in the UG. This feature can be easily used by the user like how I demoed it and it causes the software's data storage to not work at all and give erroneous data which is not failing gracefully.
Furthermore, I already gave a lower severity even though it could be higher as many times when a user uses an app, they might forget they already have one instance open and open a 2nd instance of the app. This is a relatively common occurance as a user might open a 2nd instance unknowingly (forgot they have one open) or knowingly (they want to work on 2 sessions) and your app should either disallow it explicitly and not cause issues when this happens. Just think about apps on your computer, have you never opened a 2nd session unintentionally before? What would happen if all your data is corrupted when you do so?
When I open 2 sessions of the app, and I clear the app in the 1st session. If I type ls in the 2nd session, it does not show the cleared version. Then when I open a 3rd session, it does not show the cleared version either which is confusing on how your app handles multiple sessions and stores the data.