Community
Participate
Working Groups
While executing a "wait for locator" test step, a NumberFormatException occurs [1]. The test apparently does not get influenced by that, i.e. whether a component can be found or not behaves as expected. A test suite triggering this behavior can be found in the "caa_html" project under "Ticket". [1] [Connection.ReaderThread:Socket[addr=g8.dev.bredex.local/10.54.50.36,port=53344,localport=60074]] WARN o.e.j.r.c.commands.CapTestCommand - Error while parsing timeout parameter. Using default value. java.lang.NumberFormatException: For input string: "css=html body table button" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[na:1.7.0_72] at java.lang.Integer.parseInt(Integer.java:492) ~[na:1.7.0_72] at java.lang.Integer.parseInt(Integer.java:527) ~[na:1.7.0_72] at org.eclipse.jubula.rc.common.commands.CapTestCommand.getImplClass(CapTestCommand.java:126) [org.eclipse.jubula.rc.common_3.0.0.201503201343.jar:na] at org.eclipse.jubula.rc.common.commands.CapTestCommand.execute(CapTestCommand.java:222) [org.eclipse.jubula.rc.common_3.0.0.201503201343.jar:na] at org.eclipse.jubula.communication.internal.Communicator$ConnectionListener.received(Communicator.java:841) [org.eclipse.jubula.communication_3.0.0.201503201343.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection.fireMessageReceived(Connection.java:402) [org.eclipse.jubula.communication_3.0.0.201503201343.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection.access$2(Connection.java:391) [org.eclipse.jubula.communication_3.0.0.201503201343.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection$ReaderThread.run(Connection.java:454) [org.eclipse.jubula.communication_3.0.0.201503201343.jar:na]
Good catch!
This should be fixed with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=715cb2f6729b1d4a3d86afdd70fbb1e2790e9f7c However - we need a new / modified HTML UBM for this change: - delete the CAP within the current one - re-specify the CAP (this should now use the timeout as a first parameter) - re-order the parameters of the UBM to match the sequence within the CAP We currently have a hard dependency that extended response timeouts due to dynamically specified timeout parameters have to be exactly the first parameter of a CAP - see [1] for further information. [1] http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/tree/org.eclipse.jubula.rc.common/src/org/eclipse/jubula/rc/common/commands/CapTestCommand.java#n122
I adjusted the unbound module. All should work now.
The fix seems to have caused a different problem. Executing this test step now gives the message "Invalid input: Delay after Visibility must be a non-negative integer." [1] [1] 2015-03-31 17:49:54.444 [Connection.ReaderThread:Socket[addr=g8.dev.bredex.local/10.54.50.36,port=55791,localport=55996]] ERROR o.e.j.r.c.commands.CapTestCommand - Invalid input: Delay after Visibility must be a non-negative integer. org.eclipse.jubula.rc.common.exception.StepExecutionException: Invalid input: Delay after Visibility must be a non-negative integer. at org.eclipse.jubula.rc.common.commands.CapTestCommand.handleInvalidInput(CapTestCommand.java:96) [org.eclipse.jubula.rc.common_3.1.0.201503301542.jar:na] at org.eclipse.jubula.rc.common.commands.CapTestCommand.getImplClass(CapTestCommand.java:150) [org.eclipse.jubula.rc.common_3.1.0.201503301542.jar:na] at org.eclipse.jubula.rc.common.commands.CapTestCommand.execute(CapTestCommand.java:222) [org.eclipse.jubula.rc.common_3.1.0.201503301542.jar:na] at org.eclipse.jubula.communication.internal.Communicator$ConnectionListener.received(Communicator.java:841) [org.eclipse.jubula.communication_3.1.0.201503301542.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection.fireMessageReceived(Connection.java:402) [org.eclipse.jubula.communication_3.1.0.201503301542.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection.access$2(Connection.java:391) [org.eclipse.jubula.communication_3.1.0.201503301542.jar:na] at org.eclipse.jubula.communication.internal.connection.Connection$ReaderThread.run(Connection.java:454) [org.eclipse.jubula.communication_3.1.0.201503301542.jar:na]
Should (again) be fixed with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=8a50bb423684e56d1da5e6d5b04deb77ad276ebd Same post-processing as in comment 2 is required (again - sry) - the delay after visibility is also a parameter expected at a very specific parameter position (1). Unfortunately we can't change this at the moment as there is nothing else than the (fixed known) index of the parameter this dynamic value(s) are located at.
Test is executed successfully
Created attachment 252117 [details] test results - successful