[ 
https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712015#comment-13712015
 ] 

ASF subversion and git services commented on ISIS-463:
------------------------------------------------------

Commit ab83b26002e4ca7aecba7709bd29ec0f0bb312d3 in branch refs/heads/master 
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ab83b26 ]

ISIS-463: ensuring StepDefs reusable across features

* renamed "StepDefs" to "Glue" throughout (Cukes uses this term in its runner, 
the word "Specs" and "StepDefs" are too similar to each other)
* moved glue to separate directories to specs
* updated Specs runner to pick up glue from that package (and any subpackages)
* changed CukeGlueAbstract so that it doesn't hold the ScenarioExecution as a 
field, instead gets from the ThreadLocal
  - needed so can do bootstrapping glue separately from other glue steps
* created separate glue for a "catalog of fixtures", selected using a tag

                
> Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to 
> be written (at  unit- or integration-scope, respectively)
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-463
>                 URL: https://issues.apache.org/jira/browse/ISIS-463
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: core-1.3.0
>
>
> Provide the concept of a ScenarioExecution... to provide access to 
> domainservices and "enlisted" objects; applicable to both unit- and 
> integration-scoped specs/step definitions.
> Extend to be ScenarioExecutionForIntegration... for integration-scoped specs, 
> but also for reuse by integration tests (access to domain services in 
> particular are important here).
> Also provide @XStreamConverters for built-in value types, for step 
> definitions.
> ~~~
> As result of this, should also retire the BDD viewer, update the site 
> accordingly, and remove the BDD/JUnit example.
> Should also update to the example/application to use this capability.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to