Is there a way to change the time it takes to click trough 4 buttons on a numeric custom keyboard?
I have an app where I need to enter a pin code (4 digits) and the images I user a basically 0-9.
Lets say I click 0 0 0 0 that I would like to be as fast as 1-2 seconds in total. However when I replay the recording it take 1.5 seconds pr click. I've tried to change all kinds of keypress delays on both the step to 10ms and also frin within the setting of the recording module.
Is there anywhere I can set the time so it does not take 5-8seconds to press 4 buttons?
Looking forward to hearing the answer.
Clicking the numeric keyborad takes too long
Re: Clicking the numeric keyborad takes too long
Hi,
It would be helpful if you could post some more details about your app under test and system.
Please let us know the following details:
- OS?
- Ranorex version? - latest version is 5.3.3. If you are using older version, try the latest one (even in trial mode)
- desktop, web or mobile app?
- GUI technology behind your app (HTML, Java, WPF, QT, etc...)?
- most importantly, please post the Ranorex snapshot and xpath behind the buttons.
Typically, if it takes too long to press something, the path behind the element is not unique enough or there is too much "optional" (?) elements in the path. So Ranorex is not able to quickly identify the element. Unfortunately, it's next to impossible to suggest something without the above details or even better, without analyzing a sample project. Let's start with missing details
It would be helpful if you could post some more details about your app under test and system.
Please let us know the following details:
- OS?
- Ranorex version? - latest version is 5.3.3. If you are using older version, try the latest one (even in trial mode)
- desktop, web or mobile app?
- GUI technology behind your app (HTML, Java, WPF, QT, etc...)?
- most importantly, please post the Ranorex snapshot and xpath behind the buttons.
Typically, if it takes too long to press something, the path behind the element is not unique enough or there is too much "optional" (?) elements in the path. So Ranorex is not able to quickly identify the element. Unfortunately, it's next to impossible to suggest something without the above details or even better, without analyzing a sample project. Let's start with missing details

Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Clicking the numeric keyborad takes too long
Well the 3 first ones I can give you but the rest I'm not allowed to give you.
- Windows 7 and Android 4.4
- Renorex version 5.3.3
- Mobile App
- ???
- .//button[@text='0'], .//button[@text='1'] and so on up to 9
- Windows 7 and Android 4.4
- Renorex version 5.3.3
- Mobile App
- ???
- .//button[@text='0'], .//button[@text='1'] and so on up to 9
Re: Clicking the numeric keyborad takes too long
Thanks for the additional details. Unfortunately, I have no experience with mobile testing, so I can't help you here. However the path to buttons seems to be very simplified. So if the buttons are buried deep down in the application GUI structure, such short/generic path might be a reason of the slowdown. But it's hard to say without seeing the GUI structure (snapshot).
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
- Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: Clicking the numeric keyborad takes too long
Hi AQLIVE,
I'd like to ask you two additional questions which can help us analyzing the issue in more detail.
Is your device connected via USB or WiFi?
Have you already tried to set the following instrumentation options to false
Please let me know if this solves your issue. Otherwise, we would need at least a snapshot of your application under test in order to check the GUI structure on our side.
Thank you.
Regards,
Markus (S)
I'd like to ask you two additional questions which can help us analyzing the issue in more detail.
Is your device connected via USB or WiFi?
Have you already tried to set the following instrumentation options to false
- Enable Web Testing
Full image comparison
Please let me know if this solves your issue. Otherwise, we would need at least a snapshot of your application under test in order to check the GUI structure on our side.
Thank you.
Regards,
Markus (S)