Sort Keys exceeding maximum value are saved as max value (no validation indication)

UNCONFIRMED
Assigned to

Status

Testopia
Fields
UNCONFIRMED
8 years ago
8 years ago

People

(Reporter: B.R., Assigned: Greg Hendricks)

Tracking

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)
Build Identifier: 

Test case sort keys exceeding a maximum value of 2147483647 are saved as the maxiumum value. The invalidity of entered value is not indicated to the user, and ramifications are not observable until the content is refreshed.

Reproducible: Always

Steps to Reproduce:
1. Edit a test case sort key to any value greater than 2147483647, (e.g. from the Test Cases tab of tr_show_plan.cgi , double-click in the sort key column of a test case's row, enter the value "3000000000" (three billion), and click 'Update').
Actual Results:  
The edited test case's sort key appears to be a value greater than 2147483647, (e.g. 3000000000).

Expected Results:  
An error message, or some indication if value invalidity is displayed. The invalid, unsaved value does *not* appear in the sort key field. (Alternately, the value exceeding 2147483647 could be saved?)
You need to log in before you can comment on or make changes to this bug.