X

Solaris serviceability and nifty tools

Test suite for netcat

In OpenSolaris world we very much care about correctness and hate regressions (of any kind).
If I loosely paraphrase Bryan Cantrill the degree
of devotion should be obvious:


"Have you tested your change in every way you know of ? If not, do not go any
further with the integration unless you do so."

This implies that ordinary bug fix should have a unit test accompanying it.
But, unit tests are cumbersome when performed by hand and do not mean much if they
are not accumulated over time.

For integration of Netcat into OpenSolaris I have developed number of unit tests
(basically at least one for each command line option) and couple more after spotting some bugs in nc(1).
This means that nc(1) is ripe for having a test suite so the tests
can be performed automatically. This is tracked by RFE 6646967. The test suite
will live in onnv-stc2
gate which is hosted and maintained by OpenSolaris
Testing community.

To create a test suite one can choose between two frameworks: STF and
CTI-TET.
I have chosen the latter because I wanted to try something new and also because
CTI-TET seems to be the recommended framework these days.

The work on nc test suite has started during Christmas break 2007 and after
recovery from lost data
it is now in pretty stable state and ready for code review.
This is actually somewhat exciting because nc test suite is supposed to be the first OpenSolaris test
suite developed in the open.

Fresh webrev is always stored on cr.opensolaris.org in
nc-tet.onnv-stc2 directory.
Everybody is invited to participate in the code review.

Code review should be performed via testing-discuss at opensolaris.org mailing list (subscribe via
Testing / Discussions).
It has web interface in the form of
testing-discuss forum.

So, if you're familiar with ksh scripting or CTI-TET framework (both not necessary)
you have unique chance to bash (not bash) my code ! Watch for official code review
announcement on the mailing list in the next couple of days.

Lastly, another philosophical food for thought:
Test suites are sets of programs and scripts which serve mainly one purpose - they should prevent bugs
from happening in the software they test. But, test suites are software too. Presence of bugs in test suites
is an annoying phenomenon. How to get rid of that one ?

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.