[ds6-devel] merged i18n & testing

[Chris Leishman]

On Sunday, January 19, 2003, at 03:00 PM, Simone Piunno wrote:
<snip>
> I strongly believe in "unit testing" e.g. testing each C source
> file (or each C object, cause fortunately nc6 is OO) separately.

I strongly concur.

> This is much work and I think it's not needed for 0.3 release
> (therefore your simple expect script is ok!), but long term I
> believe testing from stdin/stdout point of view (regardless of
> the expect/dejagnu choice) could be not enough.

I think both are necessary, and complement each other.  Unit testing on 
it's own cannot test the actual program operation, and system testing 
cannot test internal semantics.  And in reality, unit testing is 
typically easier to implement than system testing.

What I was wondering is what sort of test harness we should use.  
There's dejagnu, which is mostly for system testing, but can also do 
unit tests - and provides the framework for managing the test results, 
but it's really heavy and not very well documented.  Otherwise we just 
roll our own simple version, or use something like perl Test::Harness.  
But your right - it can wait till a later release.

Regards,
Chris