Subj : Re: tools to build design of application
To   : comp.programming
From : Phlip
Date : Fri Jul 29 2005 10:48 pm

Roman Mashak wrote:

>  P> TEST_(TestCase, term)
>  P> {
>  P>     CPPUNIT_ASSERT_CLOSE( 3.0, parse("3") );
>  P>     CPPUNIT_ASSERT_CLOSE( 2.0, parse("2") );
>  P>     CPPUNIT_ASSERT_CLOSE( 2.8, parse("2.8") );
>  P>     CPPUNIT_ASSERT_CLOSE( 2.8, parse("  2.8") );
>  P>     CPPUNIT_ASSERT_CLOSE(-2.8, parse("-2.8") );
>  P>     ASSERT_BEEF( parse(".q")   , "syntax error" );
>  P>     ASSERT_BEEF( parse("- 1.0"), "syntax error" );
>  P> }

> so, if I understand right, these macros are part of some, let it call 'test
> application', the purpose of which is only to test(=validate) every
> function?

Yup. And you run all of them after every few edits.

This is one of the most important ideas in programming, and I apologize
for all the introductory tutorials that ignore it or treat it as
advanced.

> It sounds a bit tangled for me by now, are there any books or documents
> describing this feature more thoroughly?

Google JUnit or CppUnit to start on the technology.

-- 
  Phlip

.