Migration to Cucumber and Gradle

[Stephen de Vries]

Following feedback and feature requests from users we're migrating the framework to Cucumber JVM and Gradle for the build system, more details about the changes on our blog post: http://www.continuumsecurity.net/2016/02/14/BDD-Security-Cucumber.html

The code can be found in the cukesecure branch of the project as is very much a work in progress, i.e. some tests are broken.

[Fraser Scott]

Very cool news! Cucumber is awesome.

[Iain Macdonald]

Good News and a really positive thing that will make Security Testing much more accessible.

Can I ask what the thoughts behind using Gradle over Maven is? 

The reason I ask is there are some really nice Maven plugins already written for Cucumber which don't seem to be available in the gradle world.

This builds a really nice report based around the feature file logic, Pass and Fail

http://mvnrepository.com/artifact/net.masterthought/cucumber-reporting 

I'm sure we could build something, but I prefer not to reinvent the wheel all the time unless there is a specific reason for gradle?

On Wednesday, 2 March 2016 08:25:16 UTC, Stephen de Vries wrote:

[Stephen de Vries]

Gradle seems more flexible than maven and I thought that since the BDD-Sec project is on the fringes of an acceptance testing framework and a security scanner that we might need that flexibility down the road.  

There are some options for non-maven reporting, e.g.: https://github.com/damianszczepanik/cucumber-reporting

and http://mkolisnyk.blogspot.com.es/2015/05/cucumber-jvm-advanced-reporting.html

But I'm happy to convinced that gradle isn't the answer!  If you'd like to fork and setup a PoC with maven we could explore that.  My maven-foo is sorely lacking though.

[Stephen de Vries]

BTW, the latest version on the cukesecure branch now has the pretty cucumber reporting enabled from masterthought.

On Wednesday, March 2, 2016 at 11:23:03 AM UTC+1, Iain Macdonald wrote: