Ethereal-dev: [Ethereal-dev] Better randpkt testing

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Gerald Combs <gerald@xxxxxxxxxxxx>
Date: Fri, 11 Mar 2005 16:25:34 -0600
We have a Buildbot step that runs tethereal on each output type
generated by randpkt (arp, dns, eth, fddi, icmp, ip, llc, nbns, syslog,
tcp, tr, udp, bvlc, ncp2222, giop, bgp, and tds).  This is great for
testing the few protocols in randpkt's type list, but not so great for
testing all of the other protocols we support.

In an effort to improve on this, I've added a section to the test script
that does the following:

LIST=`./tethereal -G decodes | grep ^tcp.port | cut -f3`
for PROTO in $LIST; do
    ./randpkt -t bgp $OUTFILE
    ./tethereal -nVr $OUTFILE -d tcp.port==179,$PROTO
done

There's a similar section for UDP-based protocols, using randpkt's DNS
output type.

The goal is to explicitly test as many dissectors as possible.  Is there
a better way to do this?