Eclipse Community Forums: Jubula » Easiest way to debug an AUTAgent?

Help

Home

Home » Archived » Jubula » Easiest way to debug an AUTAgent?

Show: Today's Messages :: Show Polls :: Message Navigator

Easiest way to debug an AUTAgent? [message #1478237]

Tue, 18 November 2014 14:05

Dave Ball

Messages: 11
Registered: November 2014

Junior Member

I'm having trouble getting the HTML agent to behave as I need (see this), so I'd like to debug and try to get this working for my app.

I thought the easiest way to debug this would be debuging app.uatagent containing my modified som.bredexsw.jubula.rc.html. However I've just noticed that the AUTServer execs another process for the actual AUTAgent.

Is there a simpler way to start/debug the AUTAgent itself? And then attach a jubula instance to run some test steps?

Many thanks,
Dave

ps - would this be more appropriate on the dev mailing list?

Report message to a moderator

Re: Easiest way to debug an AUTAgent? [message #1478367 is a reply to message #1478237]

Tue, 18 November 2014 16:23

Dave Ball

Messages: 11
Registered: November 2014

Junior Member

For anyone else that is trying this (or for me when I next forget) you can launch e.g. com.bredexsw.jubula.rc.html.WebAUTServer directly, with 8 appropriate arguments. So if Jubula is connected to the integrated AUT agent, something like the following:

43740
h t t p s://localhost:8080/
*firefox
AUT
localhost
60001
my_aut_ID
id
true

For com.bredexsw.jubula.rc.html, I needed to do some minor gymnastics to get the /lib/gen-js/ munged javascript accessible as a classpath resource.

Dave

Report message to a moderator

Previous Topic:	com.bredexsw.jubula.rc.html.web source?
Next Topic:	possible to define / use conditions?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 14:11:03 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter