search

ArtemiszenN / pe

1 stars 0 forks source link

UG does not specify range for RUNTIME variables #4

Open ArtemiszenN opened 1 year ago

ArtemiszenN commented 1 year ago

image.png

image.png

UG only specifies that positive integers should be used

soc-se-bot commented 1 year ago

Team's Response

While I agree that the UG can be more specific to the constraints, the input tested is rather unreasonable and illogical. (As time cannot exceed 60 minutes/ 60 seconds?)

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The Not In Scope response implies that this should be done in the next iteration, I think.

image.png

However, as seen in the image, the team is already showing limits in the UG (for the same function too). It is just incomplete.

In the second command, seconds is under 60. Time can exceed 60 minutes when there is no hours to input (If I can't input 1h 10min, I have to input 70 min). You might be asking who in the world would need more than 60 minutes to complete a 2.4 run. Unfortunately, as someone who is severely asthmatic, I can assure you that that scenario is possible.