Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » Testing of AUT launched from another AUT
Testing of AUT launched from another AUT [message #1815720] Tue, 08 October 2019 20:17
Bhushan nadkarni is currently offline Bhushan nadkarniFriend
Messages: 1
Registered: October 2019
Junior Member
We test an AUT which is opened by another AUT.

The parent AUT works fine and can be tested.

But the child AUT shows up as connected in the left window. But when we try to perform the Object Modelling for this AUT we are getting the error as shown below

Both AUTs are swing based. Has anyone done this with Jubula?

I have also started the AUT agent in "lenient" mode does not work.

2019-10-08 15:44:05.035 [Connection.ReaderThread:Socket[addr=/127.0.0.1,port=64530,localport=60001]] ERROR o.e.j.c.internal.Communicator - caught exception from 'org.eclipse.jubula.autagent.common.commands.ConnectToAutCommand.execute()'
java.lang.NullPointerException: null
at org.eclipse.jubula.autagent.common.agent.AutAgent.sendConnectToClientMessage(AutAgent.java:709) ~[na:na]
at org.eclipse.jubula.autagent.common.commands.ConnectToAutCommand.execute(ConnectToAutCommand.java:46) ~[na:na]
at org.eclipse.jubula.communication.internal.Communicator$ConnectionListener.received(Communicator.java:921) ~[org.eclipse.jubula.communication_4.0.0.201902270829.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection.fireMessageReceived(Connection.java:402) [org.eclipse.jubula.communication_4.0.0.201902270829.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection.access$2(Connection.java:391) [org.eclipse.jubula.communication_4.0.0.201902270829.jar:na]
at org.eclipse.jubula.communication.internal.connection.Connection$ReaderThread.run(Connection.java:454) [org.eclipse.jubula.communication_4.0.0.201902270829.jar:na]
2019-10-08 15:44:15.061 [Awaiting command: class org.eclipse.jubula.client.internal.commands.ConnectToAutResponseCommand] WARN o.e.j.c.i.c.ConnectToAutResponseCommand - org.eclipse.jubula.client.internal.commands.ConnectToAutResponseCommandtimeout() called
2019-10-08 15:44:25.062 [Worker-54: Start Object Mapping Mode] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
Previous Topic:Autagent does not clean temp files
Next Topic:Unable to select and click on a row in a table for an RCP application
Goto Forum:
  


Current Time: Sat Nov 23 03:28:01 GMT 2019

Powered by FUDForum. Page generated in 0.02036 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top