Plus 1 Chuck van der Linden. I am only interested in errors as well. *I have scripted mine so that it only includes screenshots of failed steps.*
Even then consider screen shots may only provide limited value on understanding failure cause. A well versed failed message should lead you to the cause just as quickly. -- Regards On Friday, February 20, 2015 at 2:35:36 AM UTC-6, Chuck van der Linden wrote: > > On Tuesday, February 17, 2015 at 4:18:31 AM UTC-8, Hopper wrote: >> >> +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. >> >> For anyone using cucumber, I strongly recommend two things. > > 1) READ "The Cucumber Book" it's good stuff and really will get you off > onto the right foot. > > 2) See if you can get your product owner to read "Specification by > Example" and maybe get on board with using cucumber as it is intended > > 3) (ok, three things) Be aware that the most common traps for testers to > fall into and avoid them > > - Do Not create cucumber features that have way too much > implementation detail in them google 'you're cuking it wrong' > - Keep the actual details of what gets clicked etc inside the step > code, not in the step names and feature files. > - DO NOT try to cram keyword driven automation into cucumber steps, > - Do Not make step reuse your holy grail. That way lies the madnexx > of coding steps that end up with like 4 capture groups and 5 case > statements.and fill two screens "one step to rule them all' is evil. > - DO use abstraction layers. I really happen to like the Test-Factory > gem for implementing a simple light weight page object pattern. > > -- -- 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.
