|How to manage control of Jubula test execution [message #1804205]
|Wed, 20 March 2019 11:04
| Kairus Chris Denoy
Registered: March 2019
Hi, I have a custom tool to test an application using the Jubula API. I have test environments on 2 PCs. On one PC, the execution goes smoothly, however, on the other, the execution is very fast. Too fast to a point where the clicking/inputting event gets mixed up before the mouse could finish moving over the component.
I have attached a sample image on my login below. It starts with "window-001.png" then before the mouse focuses on the password, the first character of the password is appended on the username. Sometimes it would screw up the cursor that it'd highlight the input of the username. Sometimes it would end up successfully clicking the login button but the button was not actually clicked.
It is a seriously weird case, but is there a way to manage this??
If anyone asks for specs, both are virtual machines with 4GB RAM with around 2GHz processor. The difference is that, one is QEMU and the other is KVM. Using Jubula 220.127.116.112
Powered by FUDForum
. Page generated in 0.02446 seconds