Manual Integration Test: Test Validation.Minimum on Edm.Decimal
DESCRIPTION
Test the behavior when you enter incorrect values.
PREPARATION
To check console errors, open the developer tools before you start the application. Check
with each step that there are no errors and warnings.
Testing With Mock Data
Start the OData Types application with one of the following URLs; adjust host and port if
necessary:
Testing Against back end System
Configure your Web IDE to execute the OData Types application against an ABAP back end
system.
Start the OData Types application with the following URL; adjust host and port if necessary:
REALIZE AND CHECK
Enter an invalid value for Validation.Minimum on Edm.Decimal
- Start the application.
- Enter a value less than or equal to 100 in the
sap.ui.model.odata.type.Decimal
(minimum: 100 (exclusive), maximum: 1000)
field.
- Check: You get a validation error.
- Press
Reset Model
.
- Check: The validation error is gone and the old value is displayed.
- Enter a value less than or equal to 100 in the
sap.ui.model.odata.type.Decimal
(minimum: 100 (exclusive), maximum: 1000)
field.
- Check: You get a validation error.
- Correct errors by entering valid values.
- Check: The validation error is gone and the old value is displayed.
OData V4 Model tests
- Press
V4
Button.
- Enter invalid values in one or more of the data fields.
- Check: You get validation errors with appropriate error messages.
- Check: The data state of the related control is erroneous, this means that
the control now is displayed with a red border and if it gets the foccus, you see
the same error message highlighted beside the control.
- Press
Reset Model
or Reset ContextBinding
.
- Check: The validation errors are gone and the old values are displayed.
- Enter again invalid values in one or more of the data fields.
- Check: You get validation errors with appropriate error messages.
- Correct errors by entering valid values.
- Check: The validation errors are gone.
- Enter 100 in the field labeled
precision: 10, scale: 3, minimum: 100
(exclusive), maximum: 1000
.
- Check: You get an error with the message "Enter a number greater than
100.000".
- Correct the error by entering a valid value, e.g. 101
- Check: The validation error is gone.
- Enter 102 in the field labeled
stepInput: min: 0 max: 99 scale: 0
.
- Check: You get an invalid data state "Enter a number with a maximum value of
99".
- Correct the error by entering a valid value, e.g. 99
- Enter 1.234 in the field labeled
stepInput: min: 0 max: 99 scale: 0
.
- Check: You get an invalid data state "Enter a number with no decimal places".
- Correct the error by entering a valid value, e.g. 98
- Check: The validation error is gone.
- Enter any value in the field labeled
Duration
.
- Check: You get an error with the message "Type
'sap.ui.model.odata.type.Raw' does not support formatting".
- Press
Reset Model
or Reset ContextBinding
.
- Check: The error is gone.
- Enter "Apr 19, 2029" in the date date picker labeled with
Date, bound property dateValue
.
- Check: There is no error displayed.
- Enter "Apr 19, 2029, 8:25:21 AM" in the date time picker labeled with
DateTimeOffset, bound property dateValue
.
- Check: There is no error displayed.
- Enter "Europe/Berlin" in the field labeled with
TimezoneID
in the
section com.sap.vocabularies.UI.v1.Identification
.
- Check: The field labeled with
DateTimeOffset
in the same section
has the value "Apr 19, 2029, 8:25:21 AM Europe/Berlin".
Real OData tests
- Start the app with URL parameter "realOData=true".
- Enter valid values in the input fields.
- Press
Save
.
- Reload the application and Check whether the before saved values appear.
- Clear the field labeled
String40
- Check: The input field is empty.
- Press
Save
.
- Check: No error occurs.
- Reload the application and Check whether the field is still empty.
- Press
Reset
.
- Check whether the default values provided by the service appear.
- Reload the application and Check whether the default values still appear.
- Press
V4
button and test the same within for OData v4 model.