Bugzilla – Full Text Bug Listing
| Summary: | Running external command always exits with code '1' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Anders Forsell <aforsell1971> | ||||
| Component: | Core | Assignee: | Project Inbox <jubula.core-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | blocker | ||||||
| Priority: | P3 | CC: | alexandra.schladebeck | ||||
| Version: | 1.1.0 | ||||||
| Target Milestone: | Indigo SR2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Having looked at the screenshots, I believe this is a problem with the space in the command. You will have to use double quotes as well as the single quotes to make the space in the command be interpreted properly (single quotes on the outside, double on the inside). The documentation for white spaces in commands is here: http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/reference/node13.html (Search for "Execute external command") The single quotes are necessary to mask the backslash, the double quotes to mask the space. I tested this on my system with the following: 1. Single quotes and no spaces in the path: successful 2. Single quotes and spaces in the path: failure 3. Single and double quotes with spaces in the path: successful. I'm going to close the ticket as works for me, but if you continue to have problems, please reopen it with the additional information. |
Created attachment 206847 [details] Screenshots showing the problem We have a problem when running an external command in that it always returns with exit code '1' according to Jubula. We have verified this by creating a simple CMD script with a single line "EXIT 0". See also the attached screenshots.