Eclipse Community Forums: Jubula » Execute Extermal Command

Home » Archived » Jubula » Execute Extermal Command - run Sikuli script -> wrong exit code(Execute Extermal Command - run Sikuli script -> wrong exit code)

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

Execute Extermal Command - run Sikuli script -> wrong exit code [message #1701610]

Tue, 14 July 2015 12:36

Robert Unknown

Messages: 4
Registered: July 2015

Junior Member

Hey,

i wrote a teststep which execute an external commad:

im using this parameters:
COMMAND [String]: "C:\\Sikuli\\runsikulix.cmd" -r "C:\\Sikuli\\Test_1.sikuli"
EXPECTED_EXIT_CODE[Integer]: 0
LOCAL[Boolean]: true
TIMEOUT_IN_MILISECS[Integer]: 10000

When i just run the test case the sikuli script is executed well, but the exit code is ever 0.

When i say exit(99) in my Sikuli script. Jubula still receive the exit code 0 and marked the teststep as successfull.

What i'm doing wrong?

Report message to a moderator

Re: Execute Extermal Command - run Sikuli script -> wrong exit code [message #1701618 is a reply to message #1701610]

Tue, 14 July 2015 13:13

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

Hi,

this may be connected to [1] and [2].
Please keep in mind that the ub_app_executeExternalCommand action is not really designed to deal with parameters when executing an external command.
A workaround can be to have different files which include the actual command + the parameter.
Regards
Oliver

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=470982
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=470983

Report message to a moderator

Previous Topic:	GEF support in Eclipse 4.x
Next Topic:	Build Jubula - Some required artifacts could not be downloaded

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 05:44:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter