Hi Oscar, I haven't looked at this code for a while, but those are reasonable ideas.
Over the next few months I'm going to spend some time backfilling some missing Estatio tests, so will look to see if there are ways we can do a lightweight teardown/setup rather than the rather heavyweight approach we currently do. I've raised a ticket as a handle for this [2] and added it to the list of things we might discuss at our mini-conf [3]. Thx Dan [2] https://issues.apache.org/jira/browse/ISIS-767 [3] https://cwiki.apache.org/confluence/display/ISIS/IsisCon+2014 On 14 April 2014 12:42, GESCONSULTOR - Óscar Bou <[email protected]>wrote: > > 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 > > >
