[
https://issues.apache.org/jira/browse/ISIS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-767:
-----------------------------
Fix Version/s: (was: core-1.7.0)
core-2.0.0
> Enable integration and BDD tests to do a lightweight teardown (eg zap
> contents of tables) rather than tear down entire system.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-767
> URL: https://issues.apache.org/jira/browse/ISIS-767
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.4.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-2.0.0
>
>
> Background to this is email from Oscar to dev list:
> We have implemented some BDD tests as Scenario Outlines [1].
> But just for one execution, is spending aprox. 15 min in completing a
> Scenario Outline with aprox. 20 scenarios.
> The problem is that they become really slow, as the whole Isis system is
> recreated for each example.
> Following best practices, Scenarios should be independent, but I think there
> should be ways to guarantee it without sacrificing speed.
> - Isis System does not need to be recreated (introspected) for each Scenario,
> as the source code has not changed.
> - Database can be recreated, or perhaps there's an "abstraction" on
> DataNucleus or JDBC to empty a DataStore without re-creating the table
> structure from the JDO annotations.
> Perhaps are other alternatives to improve their speed that does not require
> refactoring the Isis BDD integrations tests implementation?
> Regards,
> Oscar
> [1]
> http://jnye.co/Posts/11/repeating-bdd-tests-using-scenario-outlines-and-an-examples-table-with-specflow
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
