+1 for Cucumber.

For a while now I've been looking for something that would output simple 
HTML reports with embedded screenshots for failures.  Crucially, I wanted 
something simple and quick to implement.
I had previously read the article that Chuck linked, and it deterred me for 
a long time, but I caved in yesterday and decided to give Cucumber a go.  I 
have to be honest, I really like it.  Once you get your head around it, 
it's very easy to use and the reports it outputs are very easy for anybody 
to understand.

I have scripted mine so that it only includes screenshots of failed steps.

I'm no expert but feel free to PM me if you need a hand.

On Tuesday, 17 February 2015 07:07:37 UTC, Chuck van der Linden wrote:
>
> On Monday, February 16, 2015 at 6:38:47 PM UTC-8, Joe Fl wrote:
>>
>> Hi,
>>
>> Here is a discussion about using CLReport which is disguised here in the 
>> group.
>>
>>
>> https://groups.google.com/forum/#!searchin/watir-general/Clreport/watir-general/TYJzYeLmC2c/36vWuMQ5WHMJ
>>
>> you can build a nice report and then launch in a browser when the tests 
>> are done.
>>
>> You guys might look into Cucumber or rspec with Jenkins which will 
>> provide a nice automation test result page in a browser.
>>
>> Joe
>>
>>
> The main reason to use Cucumber is as a collaboration tool to insure that 
> everyone on the team has a clear understanding of how what you are building 
> is supposed to behave.  (see 
> https://cukes.info/blog/2014/03/03/the-worlds-most-misunderstood-collaboration-tool.html
>  
> )
>
> That said, things like nice pretty HTML reports (which can even feature 
> embedded screenshots) are a really nice 'side benefit' of the tool.  Those 
> benefits (along with not having to create your own framework, re-usable 
> steps, running various selections of scenarios according to 'tags' and a 
> host of other things are large enough that I think you can justify using 
> Cukes even if you don't have full buy in at the collaboration tool level. 
>  However, if you do that, IMHO you really need to work hard to avoid some 
> of the traps mentioned in the link above.  I can go on at some length about 
> that, but that would be a thread-jacking, so I will reframe. 
>

-- 
-- 
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/d/optout.

Reply via email to