You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UG mentions the ability to double-click the app to open the application, however a Java Exception error message appears when this occurs.
Although, the UG does mention an alternative if this occurs, if the functionality to double click to open is not working in the first place, it should not be mentioned as a step to "Getting Started" as this would confuse new users greatly.
Technically, the inability to open the app should warrant a severity.High, however the FAQ to an alternative of launching the app can helps lessen the severity as the user will be able to figure out the solution if they continue reading the UG.
The text was updated successfully, but these errors were encountered:
First, we have mentioned a remedy to this issue in our FAQ section, by running java -jar networkbook.jar command in the terminal.
Second, it is stated in the PE instructions not to launch the jar file with double-click. We included it in the UG because we have tried out on our local Windows systems that it works. We have confirmed that the Java version used to launch with double-clicking on our side is Java 11. It might be different on your system, which could be why it did not work, as stated in the instruction from the course website below.
Items for the Tester to Verify
❓ Issue response
Team chose [response.Rejected]
I disagree
Reason for disagreement: While it is stated in the PE instructions not to launch by double-clicking, it was given as an instruction in the UG hence, from a typical user perspective the user would likely double-click to open the jar file.
I do acknowledge that an FAQ was given which helps remedy the problem hence did not put severity.High. However there is no link to the FAQ or a mention of such a possible error in the Getting Started section which could cause users to not be able to use the app if they do not view the FAQ. I believe that with the possibility of such an error occuring, the team should not have even put the double-clicking as a method unless it was fixed and extensive testing was done to ensure it worked on all systems. To add on, the java version I had installed was 11 as well so I am not sure what was the issue preventing the double-clicking.
Hence, I feel this bug should not be Rejected as the product is providing an instruction that could lead to an error in the usage. A possible remedy would be to have the command terminal method be the default method and the double-clicking an additional method for users whose systems allow it or to fix the issue with double clicking to allow it to work on all systems.
UG mentions the ability to double-click the app to open the application, however a Java Exception error message appears when this occurs.
Although, the UG does mention an alternative if this occurs, if the functionality to double click to open is not working in the first place, it should not be mentioned as a step to "Getting Started" as this would confuse new users greatly.
Technically, the inability to open the app should warrant a
severity.High
, however the FAQ to an alternative of launching the app can helps lessen the severity as the user will be able to figure out the solution if they continue reading the UG.The text was updated successfully, but these errors were encountered: