Community
Participate
Working Groups
Sometimes Test Suites stop by the first Test Step, cause the 'Application' component couldn't be found. This problem does not occur permanently. It has already occurred for Windows and CentOS in Swing, SWT and RCP AUTs. Relevant text from the gdTestCentOS Console: Mon Jan 24 22:18:53 CET 2011 AUT: Starting AUT: GUIdancer ... ... Mon Jan 24 22:19:10 CET 2011 Start Test Suite: GUIdancer-FULLTEST-gdcentos5(1/1) ... ... Jan 24, 2011 10:19:22 PM org.eclipse.jubula.client.core.businessprocess.TestExecution processCap SEVERE: The logic component '8ab6b08d1a4d08f3011a4d09a4920021' is not managed. org.eclipse.jubula.client.core.model.LogicComponentNotManagedException: The logic component '8ab6b08d1a4d08f3011a4d09a4920021' is not managed. ... ... Jan 24, 2011 10:19:48 PM org.eclipse.jubula.communication.Communicator$ConnectionListener received WARNING: Received response org.eclipse.jubula.client.core.commands.AUTStartedCommand@1ef96dc *after* timeout expired. The Timestamp-formatting for Client and AUT are different, but one can see that it takes to long to start the AUT completely. We should rethink our AUT-Start-Synchronization. Enhancement created after closing this Ticket: https://cgi-int.bredex.de/bredex/trac/p21306/ticket/3566
I don't think that this has happened in the meantime, and I know that we've done work on the connection. Marking as worksforme.
Closed due to comment 1.