[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718065#comment-13718065 ] ASF subversion and git services commented on ISIS-463: -- Commit 1b8f71a52c927f628abfbb38318c24a5a2617f35 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1b8f71a ] ISIS-463: making the compare tables functionality a little less strict 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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712058#comment-13712058 ] ASF subversion and git services commented on ISIS-463: -- Commit 4c472637f5918f4c718384bb84302e68f7d753ae in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=4c47263 ] ISIS-463: wasn't correctly setting up beginTran for subsequent scenarios. * also just need a single spec runner (RunSpecs) * configure to use json * added (commented out) configuration for enhanced cucumber-jvm reporting. 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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709626#comment-13709626 ] ASF subversion and git services commented on ISIS-463: -- Commit a9bea733e3c1bd6392b4493128b8119d3f61a015 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a9bea73 ] ISIS-463: adding nextTransaction() to CukeStepDefsAbstract... ... and IntegrationTestAbstract 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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708051#comment-13708051 ] ASF subversion and git services commented on ISIS-463: -- Commit 36f1d1d3a630337813df12203f71467f438a0eef in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=36f1d1d ] ISIS-463: updating comment only. 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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707691#comment-13707691 ] ASF subversion and git services commented on ISIS-463: -- Commit 880644265fa29a659f6a47e04b0324c81ea9ec0c in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=8806442 ] ISIS-463: todo spec can now also run at unit-level scope. (still missing... ability to interleave unit- vs integration-level tests) 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
[jira] [Commented] (ISIS-463) Enhance unittestsupport and integtestsupport to enable Cucumber-JVM specs to be written (at unit- or integration-scope, respectively)
[ https://issues.apache.org/jira/browse/ISIS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707088#comment-13707088 ] ASF subversion and git services commented on ISIS-463: -- Commit 1e6070f345324ffbf6be0ea2e4b8f48358613e70 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1e6070f ] ISIS-463: simplifying and improving example app integ tests. * using new framewor * using IsisJdoSupport to teardown fixtures * different fixtures used in different tests. 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
