First a little background info.
These UI test failures occurring due to timeout interact with a perspective that is not built off the Workbench type. The AUT has a perspective to interact with the various servers and so there are numerous tests that need to login & logout various users to test certain conditions.
A similar test failure due to timeout involving this perspective occurred before and was documented in the Xored support ticket #1537
A special SNAPSHOT (v2.1.0) build was created with the patch and upon testing with the AUT the problem was resolved.
Ever since that version of RCPTT has been used to run these particular AUT UI tests.
I was told by the support representative that the patch would eventually be rolled into the next release of RCPTT. It would seem that may not have happened.
So now the AUT is having its Eclipse version updated for an upcoming release and thus the RCPTT version must be updated to even successfully launch the AUT and run tests. Unfortunately these UI tests for this unique perspective are not running successfully 100% of the time and the failure referred to does not always happen but it happens enough that results are unreliable.
Below is an example of the failure being hit by the tests:
Failed to execute org.eclipse.rcptt.ecl.gen.ast.impl.AstExecImpl@4bb9e791 (host: null) (namespace: null, name: login-user) (column: 1, line: 2, length: 36, resourceID: _1VHY0EsIEeSdwfyTRl42CA)
Execution has timed out after 179.998 seconds
org.eclipse.core.runtime.CoreException: Execution has timed out after 179.998 seconds
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch$TimeoutInterruption.checkInterruption(BaseAutLaunch.java:245)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.computeInNewSession(BaseAutLaunch.java:277)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.internalExecute(BaseAutLaunch.java:931)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.doExecute(BaseAutLaunch.java:749)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execTestOrEclContext(BaseAutLaunch.java:668)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execElement(BaseAutLaunch.java:582)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.run(BaseAutLaunch.java:560)
at org.eclipse.rcptt.internal.launching.ecl.EclContextExecutable.doExecuteContext(EclContextExecutable.java:45)
at org.eclipse.rcptt.internal.launching.ecl.EclContextExecutable.doExecute(EclContextExecutable.java:78)
at org.eclipse.rcptt.internal.launching.DataExecutable.execute(DataExecutable.java:98)
at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:127)
at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:138)
at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:138)
at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:138)
at org.eclipse.rcptt.internal.launching.Q7LaunchManager$SessionRunnable.run(Q7LaunchManager.java:147)
at org.eclipse.rcptt.internal.launching.Q7LaunchManager$ExecThread$1.run(Q7LaunchManager.java:723)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.TimeoutException
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.createTimeoutStatus(BaseAutLaunch.java:298)
at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.access$1(BaseAutLaunch.java:296)
... 17 more
What is more useful is the following from the report details:
Result: ERROR, message: try {get-button Login \n | click} { echo "Tool cannot execute command on required control due to active modal dialog 'Login'!"\n echo "The Server must have activated the Login dialog prior to the button click."\n echo "Not doing anything to recover b/c calling procedure should continue with next step successfully."\n} -times 5 -delay 1000 result is not set
get-button Login time: 0.009 s
click time: 2 m 53 s
Result: ERROR, message: click result is not set
--> Wait details <--
Method name Time
job: com.extol.ebi.admin.ui.server.handlers.LoginHandler.execute:21 173441
For whatever reason RCPTT has not ignored the job com.extol.ebi.admin.ui.server.handlers.LoginHandler.execute that was invoked after clicking the button that activates the login prompt. The SNAPSHOT build of RCPTT referenced earlier was able to do this.
For reference I have attached the full report details for the one test script to hit this problem using the IDE in playback. In addition to the studio & IDE logs.
Assistance to resolve this playback issue would be greatly appreciated.
] 
Search
Help
Register
Login
Home
