Eclipse Community Forums: Jubula » Jubula throws Component not found exception before launching AUT

Home » Eclipse Projects » Jubula » Jubula throws Component not found exception before launching AUT(Jubula throws Component not found exception and after that AUT is launched.)

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

Jubula throws Component not found exception before launching AUT [message #1810281]

Tue, 06 August 2019 13:16

rupayan nath

Messages: 8
Registered: July 2019

Junior Member

I am using Jubula 8.7.1. I have written a test script using Jubula client API. I need a way for Jubula to wait for the AUT to launch before throwing component not found exception. My test executes fine when the AUT launch happens before the exception is thrown. The AUT is a Swing based application.

Following is my code to start AUT:

public String pomsOrder() throws Exception{
AUTAgent autagent = null;
AUTConfiguration autconfiguration = null;
AUTIdentifier autidentifier = null;
AUT aut = null;
// Connect AUT agent
autagent = MakeR.createAUTAgent("localhost", 60001);
autagent.connect();
// Launch AUT
autconfiguration = new SwingAUTConfiguration("Autidentifier",
"Autidentifier", "FXall Trading.exe",
"D:\\Development_Avecto\\ALTAIR\\7.3.0.35", null);
autidentifier = autagent.startAUT(autconfiguration);
aut = autagent.getAUT(autidentifier,
SwingComponents.getToolkitInformation());
Robot robot = new Robot();
aut.connect();

Report message to a moderator

Re: Jubula throws Component not found exception before launching AUT [message #1810458 is a reply to message #1810281]

Mon, 12 August 2019 11:58

rupayan nath

Messages: 8
Registered: July 2019

Junior Member

Is there any solution to this?

Report message to a moderator

Re: Jubula throws Component not found exception before launching AUT [message #1810537 is a reply to message #1810458]

Tue, 13 August 2019 09:47

Marvin Mueller

Messages: 255
Registered: March 2012

Senior Member

There are multiple Solutions for this problem. Mostly it is useful to wait for a specific window(Application waitForWindow) or component (waitForComponent Action) with a reasonable timeout. If this is not possible sometimes a static wait is the only solution, maybe you can also use some external applications started via java to check if the Application did start(but i have not used something like this).

best regards
Marvin Mueller

Report message to a moderator