Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Jubula Test Environment(inexplicable test suite failures)
Jubula Test Environment [message #1695796] Tue, 19 May 2015 11:22 Go to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Has anybody succeeded in establishing Jubula in a reliable Test Environment?

In our Test Environment the jubula tests succeed and fail with the same version of the AUT in a completely unforeseeable and inexplicable manner, which renders the whole procedure of using a test software rather pointless.

It is quite possible that I am too stupid to make correct test cases, but the fact that the tests seem to work and 5 minutes later they don't, makes us wonder why...

Does this sound familiar to anyone?

If I don't find out soon, the whole project will die.

[Updated on: Tue, 19 May 2015 11:29]

Report message to a moderator

Re: Jubula Test Environment [message #1695810 is a reply to message #1695796] Tue, 19 May 2015 13:04 Go to previous messageGo to next message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
Hi,

sorry to hear that you are experiencing problems with establishing a reliable testing environment.
But to answer your question: We have several projects which use Jubula for their automated regression tests and also lots of other users/customers which use Jubula without experiencing the troubles you have.
In order to help you it would be helpful if you could provide more details such as:
* testing environment
** OS
** VM
* AUT
** toolkit
* Log files
* Test Execution Reports

The more information you provide the easier it is to help you.
Regards
Oliver
Re: Jubula Test Environment [message #1695828 is a reply to message #1695810] Tue, 19 May 2015 15:03 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Hi Oliver,


This is the batch script:

"\\jubulasrv\c$\jubula\jubula\testexec" -project "ot349" -version "1.0" -autconfig "otcs@localhost" -testsuite "ot_suite" -resultdir "\\jubulasrv\c$\workspace\results" -language "en_US" -dburl "jdbc:oracle:thin:@jubulasrv:1521:xe" -dbuser system -dbpw opti -datadir "\\jubulasrv\c$\workspace" -server jubulasrv -port "60001" -data "\\jubulasrv\c$\workspace" -timeout "700"

I have attached a few Test Suite execution Logs. All from today and with different results that seem to have nothing to do with the AUT.

The AUT is a Java program.

Java version the AUT uses is
JAVA_VERSION="1.7.0"
OS_NAME="Windows"

Toolkit is unbound_modules_concrete_[6.1]

[Updated on: Tue, 19 May 2015 15:11]

Report message to a moderator

Re: Jubula Test Environment [message #1695890 is a reply to message #1695828] Wed, 20 May 2015 06:55 Go to previous messageGo to next message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
Hi,

first of all, thank you for the additional Information.
Some questions:

1. Why is the screen dark on the screenshot in executionLog-ot349-ot_suite-failed.htm ? Do you have a special kind of environment where there is no visual output configured?
2. Do you execute your tests in a VM or on a "real" machine?
3. What is the toolkit of your AUT? Swing, RCP, JavaFX...?
4. Do you have additional log files? You can find them in YourUsersFolder\.jubula\logs
5. Why do you use the unbound_modules_concrete in Version 6.1? Have you tried to execute your tests using the current Jubula version (8.1) which you can download from the Bredex website?

If you need help writing your tests, establishing a reliable environment etc. you can contact us via the Bredex website for an professional offer.

Regards
Oliver
Re: Jubula Test Environment [message #1695904 is a reply to message #1695890] Wed, 20 May 2015 08:36 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Hi Oliver!

1. No. that is also a mystery to me.
2. It's a Windows VM on HyperV.
3. The AUT uses SWT.
4. Yes, I do.
5. Most of the test cases where done in 6.1. I have the new version (8.0) installed.
I have yet to find out how to migrate those tests to the new toolkit. To make new ones would be a lot of work.

  • Attachment: aut_agent.log
    (Size: 261.56KB, Downloaded 0 times)
  • Attachment: rc_swt.log
    (Size: 2.87MB, Downloaded 0 times)
  • Attachment: client.log
    (Size: 1.32MB, Downloaded 0 times)
Re: Jubula Test Environment [message #1695907 is a reply to message #1695890] Wed, 20 May 2015 08:47 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Hi Oliver!

1. No. that is also a mystery to me.
2. It's a Windows VM on HyperV.
3. The AUT uses SWT.
4. Yes, I do.
5. Most of the test cases where done in 6.1. I have the new version (8.0) installed.
I have yet to find out how to migrate those tests to the new toolkit. To make new ones would be a lot of work.

I've just changed the toolkit to the new version.
It seems to work without modifying the test cases.
Is that correct?
  • Attachment: aut_agent.log
    (Size: 261.56KB, Downloaded 99 times)
  • Attachment: rc_swt.log
    (Size: 2.87MB, Downloaded 105 times)
  • Attachment: client.log
    (Size: 1.32MB, Downloaded 97 times)
  • Attachment: toolkit.jpg
    (Size: 29.40KB, Downloaded 100 times)

[Updated on: Wed, 20 May 2015 09:38]

Report message to a moderator

Re: Jubula Test Environment [message #1695910 is a reply to message #1695907] Wed, 20 May 2015 09:14 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
The same error occurs again with toolkit 8.0.

swt-log
2015-05-20 11:05:00.664 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49934,localport=53947]] ERROR o.e.j.r.c.c.InitTestExecutionCommand - error in activation of the AUT
org.eclipse.jubula.rc.common.exception.RobotException: Window activation failed.
at org.eclipse.jubula.rc.swt.driver.RobotSwtImpl.activateApplication(RobotSwtImpl.java:1127) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.InitTestExecutionCommand.execute(InitTestExecutionCommand.java:47) ~[org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:05:21.900 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49934,localport=53947]] WARN o.e.j.r.c.c.AbstractCapTestCommand - unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@969713[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
org.eclipse.jubula.rc.common.exception.ComponentNotFoundException: unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@969713[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
at org.eclipse.jubula.rc.swt.listener.ComponentHandler.findComponent(ComponentHandler.java:178) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.swt.commands.CAPTestCommand.findComponent(CAPTestCommand.java:43) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.getImplClass(AbstractCapTestCommand.java:133) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.execute(AbstractCapTestCommand.java:234) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:05:25.945 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49934,localport=53947]] WARN o.e.j.r.c.c.AbstractCapTestCommand - unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@f988aa[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
org.eclipse.jubula.rc.common.exception.ComponentNotFoundException: unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@f988aa[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
at org.eclipse.jubula.rc.swt.listener.ComponentHandler.findComponent(ComponentHandler.java:178) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.swt.commands.CAPTestCommand.findComponent(CAPTestCommand.java:43) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.getImplClass(AbstractCapTestCommand.java:133) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.execute(AbstractCapTestCommand.java:234) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:05:56.186 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49949,localport=53965]] ERROR o.e.j.r.c.c.InitTestExecutionCommand - error in activation of the AUT
org.eclipse.jubula.rc.common.exception.RobotException: Window activation failed.
at org.eclipse.jubula.rc.swt.driver.RobotSwtImpl.activateApplication(RobotSwtImpl.java:1127) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.InitTestExecutionCommand.execute(InitTestExecutionCommand.java:47) ~[org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:06:17.607 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49949,localport=53965]] WARN o.e.j.r.c.c.AbstractCapTestCommand - unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@1d54f63[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
org.eclipse.jubula.rc.common.exception.ComponentNotFoundException: unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@1d54f63[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
at org.eclipse.jubula.rc.swt.listener.ComponentHandler.findComponent(ComponentHandler.java:178) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.swt.commands.CAPTestCommand.findComponent(CAPTestCommand.java:43) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.getImplClass(AbstractCapTestCommand.java:133) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.execute(AbstractCapTestCommand.java:234) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:06:21.121 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=49949,localport=53965]] WARN o.e.j.r.c.c.AbstractCapTestCommand - unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@ba56d9[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
org.eclipse.jubula.rc.common.exception.ComponentNotFoundException: unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@ba56d9[component type=org.eclipse.swt.widgets.Button,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Button_1]]'.
at org.eclipse.jubula.rc.swt.listener.ComponentHandler.findComponent(ComponentHandler.java:178) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.swt.commands.CAPTestCommand.findComponent(CAPTestCommand.java:43) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.getImplClass(AbstractCapTestCommand.java:133) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.execute(AbstractCapTestCommand.java:234) [org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
2015-05-20 11:14:30.505 [Connection.ReaderThread:Socket[addr=ccsrv.ot.local/192.168.100.102,port=50103,localport=53993]] ERROR o.e.j.r.c.c.InitTestExecutionCommand - error in activation of the AUT
org.eclipse.jubula.rc.common.exception.RobotException: Window activation failed.
at org.eclipse.jubula.rc.swt.driver.RobotSwtImpl.activateApplication(RobotSwtImpl.java:1127) ~[org.eclipse.jubula.rc.swt_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.rc.common.commands.InitTestExecutionCommand.execute(InitTestExecutionCommand.java:47) ~[org.eclipse.jubula.rc.common_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]


client
2015-05-20 11:08:59.103 [Connection.ReaderThread:Socket[addr=/192.168.100.41,port=53869,localport=53868]] ERROR o.e.j.communication.Communicator - Connection reset by peer: socket write error
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.7.0_45]
at java.net.SocketOutputStream.socketWrite(Unknown Source) ~[na:1.7.0_45]
at java.net.SocketOutputStream.write(Unknown Source) ~[na:1.7.0_45]
at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) ~[na:1.7.0_45]
at sun.nio.cs.StreamEncoder.implFlushBuffer(Unknown Source) ~[na:1.7.0_45]
at sun.nio.cs.StreamEncoder.implFlush(Unknown Source) ~[na:1.7.0_45]
at sun.nio.cs.StreamEncoder.flush(Unknown Source) ~[na:1.7.0_45]
at java.io.OutputStreamWriter.flush(Unknown Source) ~[na:1.7.0_45]
at java.io.BufferedWriter.flush(Unknown Source) ~[na:1.7.0_45]
at org.eclipse.jubula.communication.connection.Connection.send(Connection.java:321) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator.send(Communicator.java:462) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.autagent.agent.AutAgent.removeAut(AutAgent.java:465) [org.eclipse.jubula.autagent_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.autagent.agent.AutAgent.access$2(AutAgent.java:456) [org.eclipse.jubula.autagent_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.autagent.agent.AutAgent$AutCommunicationErrorListener.shutDown(AutAgent.java:253) [org.eclipse.jubula.autagent_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator.fireShutDown(Communicator.java:634) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator.access$5(Communicator.java:627) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.Communicator$ErrorListener.shutDown(Communicator.java:857) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireShutDown(Connection.java:373) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$3(Connection.java:366) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.fireShutDownAndFinish(Connection.java:591) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:463) [org.eclipse.jubula.communication_2.3.0.201404150900.jar:na]

[Updated on: Wed, 20 May 2015 09:20]

Report message to a moderator

Re: Jubula Test Environment [message #1695922 is a reply to message #1695910] Wed, 20 May 2015 10:53 Go to previous messageGo to next message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
Hi,

are you sure that the problems you are experiencing are caused by an unreliable environment? Because after looking at the last execution log I get the feeling that the problems you mentioned are caused by missing synchronization steps. E.g. in the last execution you try to click on a button (OK_scenario_grc) although there is not button and the EH simply presses ENTER. Since I don´t know your AUT I cannot evaluate if this is the right way to handle this situation but from taking a first look at it I would assume that it is not. To synchronize your test steps you could use ub_grc_waitForComponent, ub_app_waitForWindow etc.
If you need help writing your test with Jubula or would like us to review your already existing tests don´t hesitate to contact us via the Bredex website.
Regards
Oliver

[Updated on: Wed, 20 May 2015 11:36]

Report message to a moderator

Re: Jubula Test Environment [message #1695930 is a reply to message #1695922] Wed, 20 May 2015 11:30 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Thanks for your input. The pressing on enter was used as a workaround because jubula missed the first click when started via batch which was unexplainable since it worked when started via the jubula client. I'll revise the test case and get back to you.

[Updated on: Wed, 20 May 2015 11:40]

Report message to a moderator

Re: Jubula Test Environment [message #1695938 is a reply to message #1695930] Wed, 20 May 2015 12:24 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
The window is there but the click is not performed.
I don't get it. Maybe you have an idea.

[Updated on: Wed, 20 May 2015 12:25]

Report message to a moderator

Re: Jubula Test Environment [message #1695946 is a reply to message #1695938] Wed, 20 May 2015 13:23 Go to previous messageGo to next message
Oliver Goetz is currently offline Oliver GoetzFriend
Messages: 219
Registered: May 2011
Senior Member
This time the test fails because the window with the title "Sitzung.*" is not found although it is there. Could you try to wait for ".*Sitzung.*"?
Re: Jubula Test Environment [message #1695947 is a reply to message #1695946] Wed, 20 May 2015 13:37 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Of course!
Re: Jubula Test Environment [message #1695950 is a reply to message #1695947] Wed, 20 May 2015 13:45 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
Same thing.
Re: Jubula Test Environment [message #1696021 is a reply to message #1695950] Thu, 21 May 2015 08:42 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
If the window appears too quickly, Jubula doesn't find the Window.

This means that an action which should be utilized to avoid a synchronization error seems to cause one.

I removed waitforwindow now.

[Updated on: Thu, 21 May 2015 08:46]

Report message to a moderator

Re: Jubula Test Environment [message #1696040 is a reply to message #1696021] Thu, 21 May 2015 10:37 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member

First it worked (see above).
Now failed again.

I just can't get my head around this. Makes no sense to me.
Re: Jubula Test Environment [message #1696066 is a reply to message #1696040] Thu, 21 May 2015 13:26 Go to previous messageGo to next message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi there,

The test that sometimes works and sometimes doesn't seems to:
* wait
* then click in the active window at 30% and 50%
* then wait for a button

My assumption is that the clik in active window isn't always having the effect you want it to. Have you watched the test running to see what happens when it fails?

Can you post some screenshots or mockups of the steps you are trying to automate? We can take a look at them to suggest what steps you might need to take.

Best regards,
Alex
Re: Jubula Test Environment [message #1696098 is a reply to message #1696066] Thu, 21 May 2015 17:54 Go to previous messageGo to next message
fab jubulator is currently offline fab jubulatorFriend
Messages: 30
Registered: November 2014
Member
The window is always in the same place. I've never seen any reason why it should not work.

Best regards

fabian

[Updated on: Thu, 21 May 2015 17:54]

Report message to a moderator

Re: Jubula Test Environment [message #1696436 is a reply to message #1696098] Tue, 26 May 2015 13:30 Go to previous message
Alexandra Schladebeck is currently offline Alexandra SchladebeckFriend
Messages: 1613
Registered: July 2009
Senior Member
Hi Fabian,

as I mentioned above, if you could post some screenshots or mockups of the steps you are trying to automate, then we can take a look at them to suggest what steps you might need to take.

Best regards,
Alex
Previous Topic: Jubula view bug
Next Topic:Object Mapping not propagated from reused project
Goto Forum:
  


Current Time: Tue Feb 27 03:09:18 GMT 2024

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

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

Back to the top