Update of /cvsroot/cppunit/cppunit2/doc
In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv6331/doc
Modified Files:
cpput.dox cpput_todo.dox
Log Message:
Added initial support for column fixture supported by fitness. Still missing
automatic type convertion and correct reporting of error with regard to
originating cell.
Index: cpput.dox
===================================================================
RCS file: /cvsroot/cppunit/cppunit2/doc/cpput.dox,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** cpput.dox 15 Aug 2007 17:35:39 -0000 1.8
--- cpput.dox 16 Aug 2007 15:51:04 -0000 1.9
***************
*** 255,258 ****
--- 255,274 ----
\see CPPUT_TEST_TABLE(), CPPUT_REGISTER_TEST_FUNCTION_TABLE_IN(), CPPUT_TEST_FUNCTION_TABLE_IN().
+ \subsection section_inputfixture Creating TestCase: input fixture
+
+ Input fixture are intended to run functional test cases with externalized input data.
+
+ They usually rely on a reflection mecanism for interaction between the input data and testing.
+
+ Currently, only column based fixture is implemented. Data takes the form of a table. The
+ header row indicates the role of each column. For each row, the same sequence of operation
+ will be done:
+ - if column name match an attribute name, then set the attribute value to the cell value
+ - if column name match a method name, then invoke the method and pass the cell value
+ - if column name ends with '?' then, if the column name match an attribute then get its value,
+ otherwise invoke the matching method name and retrieve its return value. Finally, compares the
+ retrieved value for equality with the cell value.
+
+ \see ColumnInputTest
<hr>
Index: cpput_todo.dox
===================================================================
RCS file: /cvsroot/cppunit/cppunit2/doc/cpput_todo.dox,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** cpput_todo.dox 15 Aug 2007 17:35:39 -0000 1.4
--- cpput_todo.dox 16 Aug 2007 15:51:04 -0000 1.5
***************
*** 2,6 ****
<hr>
! \section todo_input_driven_testing Input driven testing
Needs: provide testers with a way to add test cases without writing code.
--- 2,6 ----
<hr>
! \section todo_input_driven_testing Input driven testing [working but still drafty]
Needs: provide testers with a way to add test cases without writing code.
|
