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:58:17 UTC

svn commit: r1644618 - /isis/site/trunk/content/more-advanced-topics/Fixture-Scripts.md

Author: danhaywood
Date: Thu Dec 11 12:58:16 2014
New Revision: 1644618

URL: http://svn.apache.org/r1644618
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=1644618&r1=1644617&r2=1644618&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:58:16 2014
@@ -373,13 +373,13 @@ 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="600"></img>
 
 where each dependency represents one fixture script using `ExecutionContext#executeChild(...)` to execute another.
 
 However, it could easily be refactored, for example as:
 
-<img src="images/fixture-script-hierarchies-2.png" width="600"></img>
+<img src="images/fixture-script-hierarchies-2.PNG" width="600"></img>
 
 With this design there each fixture script takes responsibility for setting up its prerequisites, up to and including
 running the `ToDoItemsDelete` teardown script.