|
|
Re: Jubula test from Jenkins fails [message #1755431 is a reply to message #1755295] |
Fri, 03 March 2017 10:43 |
Kev James Messages: 22 Registered: November 2014 |
Junior Member |
|
|
Thanks, Marvin
The step I was missing was specifying the ID for AUT in the project under 'AUT IDs for AUTs started with the autrun option'
The reason I'm using autrun is that I want to be able to test on three different applications; Eclipse Luna, Eclipse Mars, and Eclipse Neon. I want Jenkins to create a brand new environment each time; unpack eclipse from a zip file, copy my plugin (and the Jubula plugin) over, modify config.ini then start it up. This way I can guarantee an untainted environment every time I run the test.
I'm not quite doing that right now, because even when I copy the Jubula plugin over and modify config.ini, Eclipse still needs to be start twice to get the Jubula plugin to work correctly (the documentation states this too, so it's not a surprise). But this is what I want to get to. I'll start up a new thread for this.
As I mentioned before, I'm very new to Jubula and Jenkins so apologies if these are all basic questions
Cheers,
Kev.
|
|
|
Powered by
FUDForum. Page generated in 0.05136 seconds