[
https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709668#comment-13709668
]
ASF subversion and git services commented on ISIS-463:
------------------------------------------------------
Commit 789022471d873d576f4f075850205e6f5f90e14b in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7890224 ]
ISIS-463: sorting out ToDo app specs and integ tests.
* the pom configuration was incorrect
* mandating a consistent naming convention
* adding some simple unit tests in the dom package
> 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
