Eclipse Community Forums: Jubula » Testexec cannot run AUT with relative path

Help

Home

Home » Archived » Jubula » Testexec cannot run AUT with relative path

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

Testexec cannot run AUT with relative path [message #1698564]

Tue, 16 June 2015 12:32

sara mel

Messages: 22
Registered: April 2015

Junior Member

I have a strange problem , Im using testexec to run my tests ...in configuration I have put a relative path for my AUT directory, when I start the AUT from ITE it works with relative path but when I do the same with testexec it tells me " aut could not be started, because no valid JAVA JRE was specified"
I tried to investigate more so I put an absolute path and I ran textexec , it works normally , I really can't see what's the matter !!

Help please Sad

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698666 is a reply to message #1698564]

Wed, 17 June 2015 07:21

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

Hi,

hmm, that´s strange. I just tried to start the Simple Adder AUT using a relative path in the AUT configuration and I was able to start it via the ITE, Testexec with parameters and Testexec with config file. I used the embedded AUT Agent for the ITE as well as for Testexec. Do you want to start the AUT on the same machine where Testexec runs or do you connect to an AUT Agent which is running on another machine?
Regards
Oliver

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698667 is a reply to message #1698666]

Wed, 17 June 2015 07:28

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

This is how my config file looks like:

<configuration>
<project>SA</project>
<version>1.0</version>
<autconfig>SA@localhost</autconfig>


<dburl>jdbc:oracle:DATABASEDATABASE:1521:DButf</dburl>


<dbuser>oliver</dbuser>
<dbpw>XxXxXxX</dbpw>
<language>en_US</language>
<testsuite>1</testsuite>

and this is what my AUT config looks like

Exec File Name: SimpleAdder.cmd
AUT Working Directory: ..\examples\AUTs\SimpleAdder\swing

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698675 is a reply to message #1698667]

Wed, 17 June 2015 08:32

sara mel

Messages: 22
Registered: April 2015

Junior Member

I was working with relative path for long time , I can't understand where is the problem , I tried with another path and it works but not with the one I want .
the directory I want to use is named temp , I don't know if this is linked to my problem ... !
the goal is to execute the AUT from temp repository that will be removed after execution , this one is copied from another server ( with ant script ) every time we want to execute tests.
this is my testexec config:

<configuration>
<project>W4_BPMNPlus_Composer</project>
<version>1.0</version>
<autconfig>W4_Composer@localhost</autconfig>
<autid>W4_Composer</autid>
<dbscheme>Default Embedded (H2)</dbscheme>
<dbuser>sa</dbuser>
<dbpw>XXX</dbpw>
<language>en_US</language>
<testsuite>Scenario_1</testsuite>
<datadir>C:\w4ComposerAutomatedTesting\accept\data</datadir>
<resultdir>C:\w4ComposerAutomatedTesting\accept\result</resultdir>
<server>localhost</server>
<port>60000</port>
</configuration>

AUT working directory : ..\..\..\W4\W4 BPMN plus Composer
I'm using Jubula x32 since 3 days , before I was working with jubula x64 and everything was ok

[Updated on: Wed, 17 June 2015 09:04]

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698687 is a reply to message #1698675]

Wed, 17 June 2015 09:33

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

Are you sure that the AUT already exists in your temp folder when you try to execute the test?

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698689 is a reply to message #1698687]

Wed, 17 June 2015 09:40

sara mel

Messages: 22
Registered: April 2015

Junior Member

yes , actually I'm using testexec without any other script ...
the question is : why it works with the ITE and not with testexec if i'm using the same aut configuration !!?

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698699 is a reply to message #1698689]

Wed, 17 June 2015 10:45

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

Could you add more Information:

* OS
* Jubula Version
* AUT toolkit
* embedded or external AUT Agent
* Log files (you can find them in your users Folder/.jubula)
* Can you reproduce this behavior when using another AUT?
* Is the AUT Agent installed on the same machine as the ITE/Testexec?

Report message to a moderator

Re: Testexec cannot run AUT with relative path [message #1698708 is a reply to message #1698699]

Wed, 17 June 2015 11:39

sara mel

Messages: 22
Registered: April 2015

Junior Member

*OS : win7 x64
*jubula version : 8.1.00294
*external AUT Agent
* log content =
[i]2015-06-17 11:53:46.623 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=57891]] ERROR o.e.j.c.i.c.StartAUTServerStateCommand - No Java found: Cannot run program "W4 BPMN plus Composer.exe": CreateProcess error=2, Le fichier spécifié est introuvable
2015-06-17 11:53:46.625 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=57891]] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: AUT could not be started, because no valid Java JRE was specified
2015-06-17 13:15:38.522 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=59213]] ERROR o.e.j.c.i.c.StartAUTServerStateCommand - No Java found: Cannot run program "W4 BPMN plus Composer.exe": CreateProcess error=2, Le fichier spécifié est introuvable
2015-06-17 13:28:07.586 [main] WARN o.e.j.client.core.ClientTestImpl - connecting the AUT Agent failed
2015-06-17 13:28:07.648 [main] ERROR o.e.j.app.testexec.TestexecClient - Connection to AUT Agent could not be established.
org.eclipse.jubula.tools.internal.exception.CommunicationException: Connection to AUT Agent could not be established.
at org.eclipse.jubula.app.testexec.batch.ExecutionController.prepareAUTAgentConnection(ExecutionController.java:650) ~[na:na]
at org.eclipse.jubula.app.testexec.batch.ExecutionController.executeJob(ExecutionController.java:411) ~[na:na]
at org.eclipse.jubula.app.testexec.TestexecClient.doRun(TestexecClient.java:79) ~[na:na]
at org.eclipse.jubula.client.cmd.AbstractCmdlineClient.run(AbstractCmdlineClient.java:416) [org.eclipse.jubula.client.cmd_3.0.0.201501191443.jar:na]
at org.eclipse.jubula.client.cmd.AbstractLauncher.start(AbstractLauncher.java:24) [org.eclipse.jubula.client.cmd_3.0.0.201501191443.jar:na]
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.200.v20130910-1609.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) [org.eclipse.osgi_3.10.1.v20140909-1633.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) [org.eclipse.osgi_3.10.1.v20140909-1633.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) [org.eclipse.osgi_3.10.1.v20140909-1633.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) [org.eclipse.osgi_3.10.1.v20140909-1633.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_72]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_72]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_72]
at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_72]
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
at org.eclipse.equinox.launcher.Main.run(Main.java:1465) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
at org.eclipse.equinox.launcher.Main.main(Main.java:1438) [org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_72]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_72]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_72]
at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_72]
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) [i4jruntime.jar:na]
at com.exe4j.runtime.WinLauncher.main(Unknown Source) [i4jruntime.jar:na]
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source) [i4jruntime.jar:na]
2015-06-17 13:28:07.648 [main] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Connection to AUT Agent could not be established.
2015-06-17 13:28:07.649 [main] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Connection to AUT Agent has been unexpectedly lost during test execution
2015-06-17 13:28:52.191 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=59729]] ERROR o.e.j.c.i.c.StartAUTServerStateCommand - No Java found: Cannot run program "W4 BPMN plus Composer.exe": CreateProcess error=2, Le fichier spécifié est introuvable
2015-06-17 13:28:52.193 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=59729]] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: AUT could not be started, because no valid Java JRE was specified[/i]

I think it iss linked to directory name
I tried 3 directories with different names at the same place
1 - W4-temp
2- W4.temp
3- W4
the first and second didn't work , but the last one worked !!!
The AUT agent is in the same machine as ITE and testexec

Report message to a moderator