From abba672fd9d4a6adadb40f80194a985acd104e87 Mon Sep 17 00:00:00 2001
From: tsntsumi <tsntsumi@users.sourceforge.jp>
Date: Wed, 18 Aug 2010 16:29:00 +0000
Subject: [PATCH] add figures

---
 doc/cookbook.dox | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 72 insertions(+), 1 deletion(-)

diff --git a/doc/cookbook.dox b/doc/cookbook.dox
index 7729efd..2e1919b 100644
--- a/doc/cookbook.dox
+++ b/doc/cookbook.dox
@@ -343,6 +343,25 @@ One may create and run objects for each test case like this:
 @endcode
 
 @english
+Calling sequence of test cases in a fixture is following:
+@japanese
+¤Ò¤È¤Ä¤Î¥Õ¥£¥¯¥¹¥Á¥ã¤ÎÃæ¤Î¥Æ¥¹¥È¥±¡¼¥¹¤Î¼Â¹Ô¥·¡¼¥±¥ó¥¹¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
+@endif
+
+@dot
+digraph FixtureCallingSequence {
+  node [ fontsize=9, fontname=Helvetica ]
+  edge [ fontsize=9 ]
+  rankdir = LR;
+  setUp -> "TestCase 1" -> tearDown;
+  setUp2 [ label="setUp" ];
+  tearDown2 [ label="tearDown" ];
+  setUp2 ->  "TestCase n" -> tearDown2;
+  tearDown -> setUp2 [ style=dotted ];
+}
+@enddot
+
+@english
 The sample code made in the above is in the directory <code>examples/complex</code>,
 the files <code>testComplex.c</code> and <code>runTestFixture.c</code>.
 @japanese
@@ -386,6 +405,20 @@ Once you have several tests, organize them into a suite.
 @section suite ¥¹¡¼¥Ä
 @endif
 
+@dot
+digraph TestStructure {
+  node [ fontsize=9, fontname=Helvetica ];
+  edge [ dir=back, fontsize=9 ];
+  TestSuite -> TestSuite [ label="1..n" ];
+  TestFixture;
+  TestSuite -> TestFixture [ label="1..n" ];
+  TestFixture -> setUp [ label="1..1" ];
+  TestCase;
+  TestFixture -> TestCase [ label="1..n" ];
+  TestFixture -> tearDown [ label="1..1" ];
+}
+@enddot
+
 @~english
 How do you set up your tests so that you can run them all at once?
 @~japanese
@@ -500,10 +533,29 @@ $ ./runTestSuite
 
 @~english
 How do you run your tests and collect their results?
+The fixtures store result of own tests into
+the @link CCUnitTestResult TestResult @endlink.
 @~japanese
 ¤É¤¦¤ä¤Ã¤Æ¥Æ¥¹¥È¤ò¼Â¹Ô¤·¡¢¤½¤Î·ë²Ì¤ò½¸¤á¤¿¤éÎɤ¤¤Ç¤·¤ç¤¦¤«¡£
+¥Õ¥£¥¯¥¹¥Á¥ã¤Ï¥Æ¥¹¥È¥±¡¼¥¹¤Î¼Â¹Ô·ë²Ì¤ò
+@link CCUnitTestResult TestResult @endlink ¤Ë³ÊǼ¤·¤Þ¤¹¡£
 @~
 
+@dot
+digraph TestResult {
+  node [ fontsize=9, fontname=Helvetica ]
+  { rank=same;
+    edge [ fontsize=9, fontname=Courier ]
+    TestFixture -> TestResult [ label="TestFailure", style=dotted, arrowhead=vee ];
+  }
+  edge [ fontsize=9, dir=back ]
+  TestFixture -> setUp;
+  TestFixture -> "TestCase 1..n";
+  TestFixture -> tearDown;
+  TestResult -> "TestFailure 0..m";
+}
+@enddot
+
 @~english
 Once you have a test suite, you'll want to run it. %CCUnit
 provides @link ExecutingTest TestRunner @endlink
@@ -513,7 +565,7 @@ its results.
 °ì¤Ä¥Æ¥¹¥È¥¹¡¼¥Ä¤ò½ñ¤¤¤¿¤é¡¢
 ¤½¤ì¤ò¼Â¹Ô¤·¤¿¤¤¤Ç¤·¤ç¤¦¡£
 CCUnit ¤Ï¥¹¡¼¥Ä¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤ËÄêµÁ¤·¡¢
-·ë²Ì¤òɽ¼¨¤¹¤ë¤¿¤á¤Î@link ExecutingTest TestRunner @endlink¤òÄ󶡤·¤Þ¤¹¡£
+·ë²Ì¤òɽ¼¨¤¹¤ë¤¿¤á¤Î @link ExecutingTest TestRunner @endlink ¤òÄ󶡤·¤Þ¤¹¡£
 @~
 
 @~english
@@ -583,6 +635,11 @@ If any fail, you'll get the following information:
 @~japanese
 @link ExecutingTest TestRunner @endlink ¤Ï¥Æ¥¹¥È¤ò¼Â¹Ô¤·¤Þ¤¹¡£
 ¤â¤·¤¹¤Ù¤Æ¤Î¥Æ¥¹¥È¤¬¥Ñ¥¹¤¹¤ì¤Ð¡¢¤½¤Î¾ðÊó¤Î¥á¥Ã¥»¡¼¥¸¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£
+¾å¤ÎÎã¤Ç¤Ï¡¢ºÇ½é¤Î¡Ö<code>.....</code>¡×¤Ï¼Â¹Ô¤·¤¿¥Æ¥¹¥È¥±¡¼¥¹¤Ç¤¹¡£
+¼Â¹Ô¤¹¤ëľÁ°¤Ë¡Ö<code>.</code>¡×¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£
+Á´¤Æ¤Î¥Æ¥¹¥È¥±¡¼¥¹¤Î¼Â¹Ô¤¬½ªÎ»¤¹¤ë¤È¡¢
+¼Â¹Ô¤Ë¤«¤«¤Ã¤¿»þ´Ö¤È¼Â¹Ô¤·¤¿¥Æ¥¹¥È¥±¡¼¥¹¤Î¿ô¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£
+
 ¤É¤ì¤«¤¬¼ºÇÔ¤¹¤ì¤Ð¡¢¤½¤ì¤Ë¤Ä¤¤¤Æ°Ê²¼¤Î¤è¤¦¤Ê¾ðÊó¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£
 @~
 
@@ -647,6 +704,20 @@ testComplex.c:53: complex equals test:
 	actual: 1+1i
 @endcode
 
+@english
+@japanese
+¤³¤ÎÎã¤Ç¤Ï¥Æ¥¹¥È¥±¡¼¥¹¤ò 5 ¸Ä¼Â¹Ô¤·¤Æ¡¢
+¤Ò¤È¤Ä¤Î¥Æ¥¹¥È¥±¡¼¥¹¤Ç¼ºÇÔ¤·¤Æ¤¤¤ë¤³¤È¤¬¤ï¤«¤ê¤Þ¤¹¡£
+ºÇ½é¤Î¡Ö<code>.F....</code>¡×¤Ç¤Ï¡¢
+¤Ò¤È¤ÄÌܤΥƥ¹¥È¥±¡¼¥¹¤¬¼ºÇÔ¤·¤Æ¤¤¤ë¤³¤È¤ò¤¢¤é¤ï¤·¤Æ¤¤¤Þ¤¹¡£
+
+¤Þ¤¿¾å½Ò¤Î¤è¤¦¤Ë¡¢
+¼ºÇÔ¤·¤¿¥Õ¥¡¥¤¥ë̾¡¢¹ÔÈֹ桢¥Æ¥¹¥È¥±¡¼¥¹¤Î̾Á° (<code>complex equals test</code>)¡¢
+ɽÌÀ¤·¤¿¾ò·ï¤Îʸ»úÎó (<code>complex_equals (s10_1, s1_1)</code>)¡¢
+´üÂÔ¤·¤¿ÃÍ (<code>10+1i</code>)¡¢
+¼ÂºÝ¤ÎÃÍ (<code>1+1i</code>)
+¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£
+@endif
 
 @english
 @section helper_macros Helper Tool
-- 
2.11.0