|Jubula Client API - Require Help! [message #1853513]
||Wed, 06 July 2022 08:31
| Sachin Upadhyay
Registered: January 2022
I wanted to reach out to the team related to an issue I am facing w.r.t Jubula Client API.|
Before that, Some background.
I started exploring Jubula as an automation tool for one of our RCP based application.
when I came across Jubula, I wondered why not so many people know about it or use it!
I did some research and was able to do an automation POC using Jubula Standalone.
The tool is excellent! It does it job perfectly, even though there are lot of improvement areas.
Now, we want to increase the automation coverage which requires some complex flows.
For this reason, I started looking at Jubula Client API.
I managed to get started with the client API part, (had some difficulty because there's not much documentation on the same)
I wanted to reach out regarding an issue I have been stuck on past 3 days.
Issue is, I am not able to correctly locate button elements on my application using Client API.
Now, this works perfectly fine with the Jubula StandAlone Installer, but when I try to perform any task on Button components, whose OM identifier I have pulled from Jubula Object Mapping itself, The click happens somewhere else.
And its not consistent - in some runs, it will click on element-A, and on another, it will click element-B.
Now it seems an issue with the element Identifier since API is not able to correctly locate the element.
I tried to look around this but failed to find any successful solution.
Here is what I have tried -
I was not able to force an Object Recognition Profile for my application, hence created a custom profile as follows
However, this does not help. It does click once correctly but after the next run, it failed to click the desired element.
I am seeking help in this direction !!
- Do I need to use some specific profile parameters?
- will the object identifier copied from Standalone Jubula not work for Client API correctly?
- I am not able to start the AUT Object Mapping tool which we get from the Start AUT context menu. Will that help? How to start it from client API?
- Is there some other tool/way to capture the component which will work for Client API?
I am relying on the information on this thread, so Request to help me out with this.
Powered by FUDForum
. Page generated in 0.01500 seconds