[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708048#comment-13708048 ]
ASF subversion and git services commented on ISIS-463: ------------------------------------------------------ Commit 3d271d24ca5fedbdbf796fd069a061920ba2e7fa in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=3d271d2 ] ISIS-463: can now intermix @unit and @integration level specs. * renamed ScenarioExecution's get and put to getVar and putVar * added a removeVar * updated corresponding convenience methods in IntegationTestAbstract and CukeStepDefsAbstract * added supportsMocks into CukeStepDefsAbstract * refactored todo specs with guards (necessary, unfortunately) - InMemoryDB utility class refactorings - fixed license header comments. > 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