nus-se-bot
commented
2 years ago Team's Response
The OS-related issues are out of scope for us, and there could potentially be hundreds to take note.
In this case, the application did open upon the user clicking twice, however it is his/her own OS which disabled the application from starting up - due to certain security or firewalls in place. And hence our team deems this bug to be rejected or even not in scope as this issue would be out of the user guide's scope.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I agree that this is an OS-related issue, however, if I were to put myself in the perspective of the user and follow the user guide, I would expect that I would be able to run the application by double-clicking on the JAR file which was not the case. Additionally the screenshot provided was from a Mac environment and I would start to wonder why it seems like the application is able to run on a Mac machine but not mine. This issue should have been caught during internal testing of the JAR release, and if it wasn't, maybe due to the lack of access to a Mac (ignoring how the screenshot was obtained), then it still would count as a documentation bug and I would still reject this on the grounds that the instructions were not clear.
Even if the users are tech-savvy and know that you need to run a JAR file through the terminal, this should have been addressed in this section.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: Based on the user guide alone, if I were on Mac environment, I would not be able to run the application as no explanations or workarounds were mentioned.
Currently on MacOS and it isn't possible to double-click to run by default. There is a way to allow this behaviour but the users would need to tinker their own system.
Suggestion:
java -jar [file.jar]