Author:halw

Date:2012-05-12T15:19:41.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1100 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/eiffelstudio/_images/AutoTest_extracted_01.png.data

@@ -0,0 +1,3 @@
+title=AutoTest extracted 01
+author=halw
+path=content/autotest-extracted-01

documentation/current/eiffelstudio/_images/AutoTest_extracted_02.png.data

@@ -0,0 +1,3 @@
+title=AutoTest extracted 02
+author=halw
+path=content/autotest-extracted-02

documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-extracted-tests.wiki

@@ -18,13 +18,14 @@ Extracted tests are intended to supplement the suite of manual tests that you ha
 
 Let's use the same test system we used for manual tests to demonstrate the creation of an extracted test. The example will be slightly contrived because it will find a problem that certainly we would already have discovered had we written a comprehensive set of manual tests against the <code>BANK_ACCOUNT</code> class. Still, the simplicity should help keep things clear.
 
-If you remember, the root class for the example application contained no instructions, just a root procedure with no instructions and a declaration <code>my_account</code> of type <code>BANK_ACCOUNT</code>:
+If you remember, the root class for the example application was not very interesting, just a root procedure with a single instruction and a declaration <code>my_account</code> of type <code>BANK_ACCOUNT</code>:
 
 
 <code>
     make
             -- Run application.
         do
+            create my_account
         end
 
     my_account: BANK_ACCOUNT