CVS: fixed tests; minor manual editing
bernhard at intevation.de
Mon Aug 15 13:13:42 CEST 2005
Am 14. Aug 2005 um 09:48:51 schrieb Jakson Aquino:
> Em Sex 12 Ago 2005 10:10, Bernhard Reiter escreveu:
> > Cool, you could even write some tests for your new
> > code.
> I ran the tests, and I found very nice that check unit
> allow us to test specific funtions. I can try to use
> it latter.
The idea is, to write the test for a funcationality or procedure first
and then implement it. This way it helps designing good interfaces,
because you start thinking about this first.
> I'm using valgrind to hunt memory leaks, uninitialized
> variables, buffer overflows, etc... I'll write a test
> for --xcols, including the recodification with awk,
> and merging files with join. (I'll use your
> "test_4_1.sh" as a guide.)
Do you call "join" or "awk" directly from statist?
Usually this would be done by the user.
I am unshure if we should add tests for this as statist
does not do it. But it would be interesting to have example
scripts for people to use.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://intevation.de/pipermail/statist-list/attachments/20050815/36a3f80c/attachment.bin
More information about the Statist-list