[Cucumber] Publishing Cukes

[Tim Walker]

Hi All, 

Like a lot of y'all, we need to publish our cukes for consumption by business and product owners in a secure project. I seek guidance or experiential reports from the group. The alternatives I see are:

1) Relish

I really like what Matt has done and think that's probably the way to go but I need a version of Relish that can run on our own servers, AWS or similar. Does anyone have experience, guidance and an idea of the cost of what's involved getting that set up? 

2) Cucumber-JVM-Reports

The reports generated from this awesome tool are gorgeous. Not sure if users would then need access to the jenkins/hudson server to view them, or if they can be exported to another server or similar. Any experience doing this?

3) Cucumber Reports or HTML Formatters (or roll-our own formatter)

Seems like the built in reports are pretty nice, embedded screenshots, roll your own or ? 

4) ???

*WWAAMD?

Appreciate any feedback! 

Thank you, 

Tim

*What Would Aslak and Matt Do?

[Rick Beyer]

Hi Tim,

I setup my company with Cucumber-JVM reports and it has been great for daily consumption.  I use the HTML formatter for any tests that use Scenario Outlines and then publish them via a Jenkins plug-in.  You can attach the HTML files to an email for anyone to open (or inline them in an HTML email) after a build.  The Cucumber-JVM reports can be run outside of Jenkins, you just need to copy over the directory that is generated after a job completes.

We looked into using Relish but it seemed more documentation focused and not individual Jenkins build focused.  We wanted to know if a scenario failed on our nightly runs and why.

I also wrote my own rails app that processes the json dump after each Jenkins job completes and I store that information for performance metric tracking.  So we have a detailed history of every suite, feature, scenario and step.  I calculate the duration at all levels and log failures and store the images generated (base64).  I also created my own graphs with google visualizations to track the performance visually on a suite, feature, scenario and step level.

[Tim Walker]

Thanks very much for the feedback. It is appreciated in the extreme. I love the Cucumber-JVM reports too, they're beautiful and I've implemented them on the last project where they were extremely well received. We are looking for more the "documentation" aspect of Cucumber as a single source of truth, the audience isn't all that interested in the daily pass/fail as much as a the "what and how the software behaves". I like the embedded screenshots available in the Cucumber Reports so you see the steps and the UI as user/system documentation, so I'm torn on the best way to proceed. Relish appears to be the best candidate, especially with the markup and the delegation of features *by release*. Love this whole aspect of BDD and Cucumber and truly want to continue to advance this grail. 

Thanks again Rick.

Tim 

--
-- Rules --
 
1) Please prefix the subject with [Ruby], [JVM] or [JS].
2) Please use interleaved answers http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
3) If you have a question, don't reply to an existing message. Start a new topic instead.
 
You received this message because you are subscribed to the Google Groups Cukes group. To post to this group, send email to cu...@googlegroups.com. To unsubscribe from this group, send email to cukes+un...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/cukes?hl=en
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rick Beyer]

Hi Tim,

You might want to check out this gem then.  https://github.com/twcamper/cuporter

We currently use it in the following manner:

Feature Report - generates html output showing all scenarios currently defined in Cucumber feature files. Gives Count as well.

Tag Report - generates html output showing all the tags currently used in the Cucumber feature files)

These are two different Jenkins jobs we have setup to run manually, the Feature report requires a parameter which passes in one of our "suite names".  Our suites are like a SmokeTest, a BuildVerificationTest, etc.