Re: [Tcllib-devel] test suite for tcllib

[Andreas K. <and...@ac...>]

> A bug item was opened yesterday regarding the fact that the tar module
> is missing a test suite. Today, I decided to run the cvs head tcllib's
> test suite interactively. So far, what I am seeing is that the
> following modules are missing test suites:
>
> bench
> ftp
> ftpd
> grammar_peg
> http
> irc
> javascript
> jpeg
> nmea
> nntp
> page
> pluginmgr

Yes, that looks about right.

> (I also see that there were failures in cmdline , grammar_me, and didn't
> get through the test suite - things just sort of "stopped" at
> sha1 (probably
> just didn't wait long enough)

sha1 in pure Tcl is slow. It is especially slow when it tests the higher
orders, i.e. sha256.

> I'm still not certain where to look for the results of the test suite -
> sure would be nice if the output was logged somewhere... there is that
> log module in tcllib ...).

./sak.tcl test run -l LOG_stem

	=> LOG.stem.log
	   LOG_stem.summary
	...

Or

./sak.tcl test run -v | tee LOG

Still, thanks for the reminder that I want to work on the test output for
make files, etc.

> Anyways, there are a number of modules which need test suites. If someone
> on this mailing list feels motivated (if you live on the east coast,
> you probably are snowed in today and have plenty of time on your hands
> ;-)

Heh.

> then perhaps you can code up a test or two and submit it.  Don't
> feel that you have to figure out every test. Just begin testing the
> basics, and more tests can be added in as time goes by.

I agree with the sentiment, very much so. Testsuites are one of the best
examples of things we can add incrementally to our packages.

--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com
	Tel: +1 778-786-1122