skipoleschris / cucumber-sbt-plugin Goto Github PK

Cucumber has been updated to release 0.10.0 and cuke4duke has been updated to 0.4.3.
The cucumber sbt plugin should support these versions

When working with a multi-module project, the cucumber tasks are only available on the sub-projects. This therefore requires that you select the project first with the: project command before you can run cucumber.

It is also not possible to run cucumber across all projects in a single test run.

When running a multi-module SBT project, all output reports from cucumber-html and cucumber-pdf tasks are written to the target directory of the parent project, not to the target directory of the project they relate to.

When running the sbt clean-lib task, the .gem and gems directory under lib_managed is not removed. It should be.

It is not possible to override the output location of the cucumber html and pdf reports. They always go to target/cucumber.html and target/cucumber.pdf respectively. It should be possible to override properties to control the directory location and the report name.

The parameterised tasks are currently called cucumberp cucumber-devp cucumber-htmlp and cucumber-pdfp. This seems quite messy, prone to typing errors and excessively long. As they are here to stay can they be renamed to something simpler.

Due to a defect in SBT we currently require non-parameterised tasks that can be run from the parent project and parameterised tasks that can be run from the child projects only. This is not nice.

When SBT is fixed, remove the non-parameterised tasks to that there is just a single set of tasks that can be run from both parent and child projects.