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
http://192.168.5.105/venomweb/clear.cache.gif"; border="0"> http://192.168.5.105/venomweb/clear.cache.gif"; border="0">
On 8 October 2013 15:24, Joe Fleck wrote:
> Hi Luis,
>
> Can you provide the relevant html for the progress bar?
>
> Joe
>
> On Tue, Oct 8, 2013 at 9:18 AM, Luis Espla wrot
Hi Luis,
Can you provide the relevant html for the progress bar?
Joe
On Tue, Oct 8, 2013 at 9:18 AM, Luis Espla wrote:
> Hello,
> I'm testing video recorded application and I want to test progress bar
> video recorded, How can I click on specific place of the progress bar video
> recorded. I
Hello,
I'm testing video recorded application and I want to test progress bar
video recorded, How can I click on specific place of the progress bar video
recorded. I attach a image for you can view progress bar. This bar has a 24
hours of the day if you click on 5 o'clock you watch video of 5,o'cl
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 u
