13-03-24 12:05 PM
Hello all !
What's the suggested methodology to attach to chrome in the following scenario
I'm using Process Name "chrome" and Child Index 0
13-03-24 05:40 PM
Process name and child index should be fine. Once you're attached to chrome, you'll find you can spy any tab anyway.
14-03-24 04:31 PM
I seem to be having issues , when I attach to child index 0 , the spied elements cannot be found on the page in the wait for stage , but can be highlighted in the Application Modeller.
If I instead attach to Child Index 1 , the Wait For stage is successful.
I have put a window title of "*" as it fails on attach with just the child index and process name.
15-03-24 02:44 PM
Hi Stephen,
Hope this help!
15-03-24 02:57 PM
I have done some testing around the issue. I was initially passing the Tracking ID out from the attach action and using this Tracking ID as an input into the Wait stage.
I have taken the Tracking ID out of the Wait stage and it now can be found by the action.