Our application used an additional feature “EUI 13” with Angular: there are additional components with EUI.
For instance we have euiinputnumber components: an example with the html generated:
I’m trying to test with Katalon our form by sending values in the different fields and I get a strange behaviour with the input-number (only with Katalon Recorder - when filling manually a value in the field, this behaviour is not present).
Here my test:
After executing the step, the value is not sent to the form: the test failed because the application considered that the form is going to be left:: the native popo-up as for closing the browser appeared (and it should not appear):
When clicking the ok button, the error appears:
TypeError: Cannot read properties of undefined (reading 'length')
at EuiInputNumberComponent.onKeyDown (http://localhost:4200/vendor.js:203125:15)
at EuiInputNumberComponent_keydown_HostBindingHandler (http://localhost:4200/vendor.js:203380:20)
at executeListenerWithErrorHandling (http://localhost:4200/vendor.js:128880:16)
at wrapListenerIn_markDirtyAndPreventDefault (http://localhost:4200/vendor.js:128918:22)
at HTMLInputElement.<anonymous> (http://localhost:4200/vendor.js:177366:34)
at ZoneDelegate.invokeTask (http://localhost:4200/polyfills.js:3562:35)
at Object.onInvokeTask (http://localhost:4200/vendor.js:139379:33)
at ZoneDelegate.invokeTask (http://localhost:4200/polyfills.js:3561:40)
at Zone.runTask (http://localhost:4200/polyfills.js:3329:51)
at ZoneTask.invokeTask [as invoke] (http://localhost:4200/polyfills.js:3644:38)
Could you please help me with that and understand why the system considers the action to leave the form when typing value in the input number field with Katalon ?
Thanks for the response, I tried with setText, the step is correctly passing: the value is properly set in the form (without trying to leave the form), but it seems that when saving the form, the value is not taken in account in the validation of the form and sent to the backend, as it was previously. The formcontrolname is not updated with the value.
Could you please provide me more information about the blockage, I will forward it to the team managing EUI in order to solve this issue (if possible) ?
Unfortunately we’re not currently supporting numeric values with those commands, only characters or string. The only way for you to get that to work is change your numeric value to string value.
With the standard input text field, all was correctly working (set the number value in the field with Katalon with sendKeys or type).
From now I understand that it’s not possible to set the number with the eui input number field with type or sendKeys.
When I’m using setText the value is correctly set in the eui input field, but when submitting the form, the value is not taken in account (0 is sent to the backend). When I did the action without Katalon, it’s correctly working and the value is correctly sent.
Dear @uyen.do Could you tell me please when setText will support numeric values like we want ? It will be great to have that because for the moment we are still blocking with our tests.
Someone could tell me please when setText will support numeric values like we want ? It will be great to have that because for the moment we are still blocking with our tests.
Dear @uyen.do , Dear @ThanhTo , Do you have news about this topic ? Could you tell me please when setText will support numeric values like we want ? It will be great to have that because for the moment we are still blocking with our tests.
In other words, uyen.do suggested that you, @amadese, should be able to modify your test script in Katalon Recorder so that it converts a numeric value of ${budget} to a string. Then the test will run. Why not you try it?
@kazurayam Thakns for your response. The problem is that the field in backend (when saving) should be a number and not a string. That’s why it must be a number.
This issue (form is leaving) is still appearing when using type or sendKeys with a string or a number. It’s only appearing when using Katalon. As explained by the eui iteam, it seems that it’s an issue coming from the tool and the incorrect management of the event (see my previous comments). But I’m not an expert with that…
When using settext, the value is setted in the field but not saving after clicking the save button (backend is properly working because if we don’t use Katalon, it’s working properly).
The old value is sent to the backend even if the value is inserted in the form by using settext. I don’t understand why this behaviour is present when using Katalon…
Furthermore I would like to know if there will have a new update of the tool as @uyen.do suggests that above.
this makes no sense. when a user type something, the keyboard sends keycodes. which are received as chars by any sane desktop application.
a string is just a bunch of chars.
how this is converted into number or something else, it is at the latitude of the application in use when is sending data to the backend
somebody is lying to you…
@bionel, ok perhaps the eui team has not the good response, but could you please explain me why the value setted with settext is not passed to the backend when pushing the save button (with a number or a text, the issue is the same).
Indeed before to use settext here the value in the form (coming from the database):