Starting RCP with workspace: autrun.exe and -data option [message #934034] |
Fri, 05 October 2012 11:36  |
Eclipse User |
|
|
|
Hi, I'm having trouble starting my RCP so as it does not prompt for a workspace. I managed to do this from the ITE but now i'm trying to make things happen in a CI environment and i'm trying to start the AUT with autrun.exe.
This is the command i'm executing:
START ./target/jubula/server/autrun.exe -rcp --workingdir c:\Mule-Tooling\org.mule.tooling.jubula.test/target/MuleStudio --autid "AUT MuleStudio" --kblayout en_US --autagenthost localhost --autagentport 60000 --exec c:\Mule-Tooling\org.mule.tooling.jubula.test/target/MuleStudio/MuleStudio.exe -data c:\Mule-Tooling\org.mule.tooling.jubula.test/target/studioworkspace
I've tried several variations on that last part (-data"C:...", -data "C:...", all the --exec param wrapped in "...", etc), but I can't seem to solve this on my own. The RCP starts but prompts for a workspace all the same.
Any clues?
Thanks!
|
|
|
|
|
Re: Starting RCP with workspace: autrun.exe and -data option [message #939138 is a reply to message #934034] |
Wed, 10 October 2012 09:11  |
Eclipse User |
|
|
|
Hi Felix, I'm starting the AUT via autrun in order to decouple the test execution configuration from the environment it will be deployed in.
In more concrete terms: if I don't use autrun, I have to pre-establish the AUT configuration (executable path, workspace path) in the database and pass along it's ID to testexec.
Using autrun, I can determine these parameters dynamically on my maven build. I extract my RCP on a /target folder relative to the maven project that is executing the tests. This way I could even register different agents to run the build, and not worry about where it will be deployed, as long as it is a Windows machine. I could manage profiles to the maven configuration add specific directives for each OS though, and have a truly OS-independent maven project that runs the integration tests.
|
|
|
Powered by
FUDForum. Page generated in 0.03532 seconds