Team's Response

As a typical user, if we wish to search for "4.99", it would not make sense for one to specify "4.00", but a "4" instead so this case is extremely rare and unlikely to happen.

Moreover, this should not be considered as a functionality bug since it was already specified that only strings starting from the given parameter would be matched.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement:

It's unclear from the UG that find for Rating is based on string matching. Users would expect ratings to be numeric, not in the form of a String.

As a typical user, if we wish to search for "4.99", it would not make sense for one to specify "4.00", but a "4" instead so this case is extremely rare and unlikely to happen.

This line is not relevant to the bug discussed here. It's about the expectation that 4, 4.0 and 4.00 all be treated the same way when they are not being treated as so.

❓ Issue type

Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: The behaviour of the app differs from the common-sense interpretation of the UG, and as such should be a functionality bug.

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: [replace this with your explanation]

from pe.