wireshark

osmith

History

Evan Huus 0a396007fe Use -Y instead of -R to filter tshark in decryption tests. We're not doing 2-pass analysis so -Y makes more sense and doesn't print deprecation warnings. svn path=/trunk/; revision=48808		2013-04-10 14:27:24 +00:00
..
captures	Add a test for Zigbee. Compress the 802.11 capture. Fix an error message.	2012-04-02 18:48:56 +00:00
config	Add a test for DTLS decryption.	2012-04-02 16:37:40 +00:00
keys	Add a test for DTLS decryption.	2012-04-02 16:37:40 +00:00
README.test	Minor updates.	2013-03-12 20:23:23 +00:00
config.sh	Update Free Software Foundation address.	2012-06-28 22:56:06 +00:00
suite-capture.sh	Disable software updates in a blind attempt to fix the recent test	2013-03-18 15:39:12 +00:00
suite-clopts.sh	Whitespace changes: Convert spaces to tabs. Add modelines.	2013-03-01 16:13:44 +00:00
suite-decryption.sh	Use -Y instead of -R to filter tshark in decryption tests. We're not doing	2013-04-10 14:27:24 +00:00
suite-fileformats.sh	Whitespace changes: Convert spaces to tabs. Add modelines.	2013-03-01 16:13:44 +00:00
suite-io.sh	Whitespace changes: Convert spaces to tabs. Add modelines.	2013-03-01 16:13:44 +00:00
suite-unittests.sh	Run the wmem unit tests with --verbose (provided by glib) so that if	2013-03-27 02:35:32 +00:00
test-backend.sh	Whitespace changes: Convert spaces to tabs. Add modelines.	2013-03-01 16:13:44 +00:00
test.sh	Update Free Software Foundation address.	2012-06-28 22:56:06 +00:00

README.test

$Id$

What is it?
-----------
This is a collection of bash scripts which test the features of:

 - Wireshark
 - TShark
 - Dumpcap 

Motivation
----------

The command line options of Wireshark and the companion command line tools are 
numerous. This makes it hard to find newly introduced bugs doing manual testing 
(try and error) with source code changes.

The current way is to do some changes, testing some scenarios by hand and 
commit the code so other users will complain about new problems. This obviously 
is far from being optimal.

Limitations
-----------

The test set currently provided will only do some basic tests, but even that 
is far better than nothing. This may involve in time as new tests can be added
to fix problems reported by users. This will hopefully lead to a "complete" 
and reliable testset in the future.

The tests are limited to command line tests, other things like unit tests or 
GUI test are not included.

Prerequisites
-------------

What you'll need (to do):

 - edit the file config.sh to suit your configuration
 - obviously, compile the programs (wireshark, ...) to be tested
 - have a bash (cygwin should do well)
 - have tput (e.g. in the cygwin ncurses package)
 - you'll need a network interface with some network traffic 
   (so you can run the capture tests)
 
A Test Ride
-----------

Start test.sh which should provide a basic menu. Just press Enter to start 
all tests.

It should start all the available tests. Each test will throw out a line 
which should end with a green "Ok". If one of the tests fail, the script
will report it and stop at this test step.

PLEASE REMEMBER TO HAVE SOME TRAFFIC ON YOUR NETWORK INTERFACE!!!