You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2014/12/11 13:59:31 UTC
svn commit: r1644619 -
/isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md
Author: danhaywood
Date: Thu Dec 11 12:59:30 2014
New Revision: 1644619
URL: http://svn.apache.org/r1644619
Log:
fixture scripts
Modified:
isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md
Modified: isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md?rev=1644619&r1=1644618&r2=1644619&view=diff
==============================================================================
--- isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md (original)
+++ isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md Thu Dec 11 12:59:30 2014
@@ -365,7 +365,7 @@ Second, the scenario script is made avai
This tells the fixture script framework that the fixture script should be listed as a choice in the UI:
-<img src="images/fixture-scenarios.png" width="500"></img>
+<img src="images/fixture-scenarios.png" width="400"></img>
## Using Deeper Hierarchies
@@ -373,15 +373,15 @@ While we suggest that you organize fixtu
The [todo app](../intro/getting-started/todoapp-archetype.html)'s fixture hierarchy as implemented is quite flat:
-<img src="images/fixture-script-hierarchies-1.PNG" width="600"></img>
+<img src="images/fixture-script-hierarchies-1.PNG" width="400"></img>
where each dependency represents one fixture script using `ExecutionContext#executeChild(...)` to execute another.
-However, it could easily be refactored, for example as:
+However, it would be possible to refactor it to use a deeper hierarchy, for example as:
-<img src="images/fixture-script-hierarchies-2.PNG" width="600"></img>
+<img src="images/fixture-script-hierarchies-2.PNG" width="400"></img>
-With this design there each fixture script takes responsibility for setting up its prerequisites, up to and including
+With this design each fixture script takes responsibility for setting up its prerequisites, up to and including
running the `ToDoItemsDelete` teardown script.
To support this design, by default the fixture script framework (specifically, `ExecutionContext`) will only ever run