I guess Test::Unit is doing that. I think you could parse for that last summary line, Jenkins can do that. Or wrap the call to the Ruby script with another script (even another Ruby script) that parses the test output and returns exit code 1.
I'm wondering if something else is eating up exit 1 and returning 0 to Jenkins (some intermediate thing like Rake). It might be a good idea to look at the exit code when you run it outside of Jenkins if you haven't already tried that ________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Tuesday, October 8, 2013 4:22 AM Subject: [wtr-general] Watir exits with 0 on failure Hello, I am running Watir scripts as part of a Jenkins job. I can see from my logs that although the script encounters errors, it's exit code (which I also echo after the script terminates) is 0 (aka success). I know from testing it on my local machine that Ruby's exit-code when watir fails is usually (# of failures + # number of errors). Any idea why my Ruby script exits with 0 although Watir fails? The log can be seen here: http://pastebin.com/WqMN3YL6 -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
