search

nimiew / pe

0 stars 0 forks source link

Jar file doesnt open on double-click after using 'tester' and closing #9

Open nimiew opened 4 years ago

nimiew commented 4 years ago

To replicate.

  1. Delete src
  2. Open jar
  3. Use 'tester' command
  4. Close the app
  5. Try opening the jar - doesnt work on windows 10
nus-pe-bot commented 4 years ago

Team's Response

Ok, we realised that the "tester" command on its own is buggy. Somehow, it configured the software into an undefined state or introduced illegal data that shouldn't be processed in the first place. Under normal circumstances, the user would not be using this command and would not be experiencing any issues with reopeining the jar.

Nonetheless, this could be a symptom to something else that our code failed to catch so we will look into the "tester" command further. Thanks for catching this.

I would also like to argue that this should be not in scope as all the main features of Chronologer are not dependent on this command. This command could be removed entirely and none of the features of Chronologer would be affected and the value the user would get from Chronologer would remain unchanged.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I disagree. This is in scope if it is in your UG.