Differing behaviour despite same error

[Kobot7]

Problem

When entering a float as an answer, the program only detects the error when it is a small value. As shown in screenshot below, entering the float 24.0 presents the error message "Answer must be an integer" but 999999999999.0 does not yield the same error message.

Steps to replicate

1. Navigate to an enemy.
2. Enter e and fight.
3. Enter 10.0.
4. Enter 999999999999.0

Screenshot

[soc-se-bot]

Team's Response

Although it does not give you a message, you enter an incorrect answer and the program detects that.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: Hi team, thank you for your response. I am aware that the program correctly detects that the answer is wrong. However, I am concerned the potential unfairness of the game due to how the game handles the same "error in answer" differently.

The current behaviour of the program is as follows:

• The user is given a question (e.g. square root of 144).
• The user can now enter an answer. I would like to focus on 2 scenarios that could happen at this point.

Scenario 1

What happens: User inputs 12.5 as the answer. Result: Program correctly detects that the input is not an integer. Program will inform user of the error and provides another chance to enter their answer. Screenshot of Program:

Scenario 2

What happens: The user's keyboard was lagging, which results in the user inputting 12222.................... into the terminal. Result: Program does not detect that the input is not an integer. User does not get another chance, and the answer is considered wrong. Screenshot of Program:

Rationale behind reporting this bug

If the team's view holds that "enter(ing) an incorrect answer and the program detects that (by marking it wrong)", then it makes it unfair for someone who enters 12.5 to not be marked as wrong and even given another chance to enter their answer. The program should be consistent in it's decision on whether to consider a non-integer as an "invalid input" or "wrong answer".

Is it a flaw? Yes, albeit a minor one. Is it unlikely to affect normal operations of the product? Yes. Does it appear only in very rare situations? Yes. Is it a minor inconvenience only? Yes.

Hence, this bug fits what severity.Low bugs are meant to be: "A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only."

I hope that this gives you more insight as to why I find this inconsistent behaviour in the program an issue. Once again, thank you for your response.

---