wireshark/test
Gerald Combs 46e68bab2b Add a missing file.
svn path=/trunk/; revision=41855
2012-03-30 17:59:27 +00:00
..
captures Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
config Add a missing file. 2012-03-30 17:59:27 +00:00
keys Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
README.test
config.sh Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
suite-capture.sh Replace "-Q" with "WIRESHARK_QUIT_AFTER_CAPTURE" as discussed in bug 6256. 2011-08-29 21:16:29 +00:00
suite-clopts.sh Undo the checking of command line interfaces. It might the a pipe... 2011-07-21 17:30:42 +00:00
suite-decryption.sh Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
suite-fileformats.sh Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
suite-io.sh test.sh: revise tests to handle revised capinfos output. 2009-05-11 18:57:08 +00:00
suite-unittests.sh
test-backend.sh Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00
test.sh Add a decryption test suite along with an SSL decryption test. Move our 2012-03-30 17:51:54 +00:00

README.test

$Id$

WARNING: these tests are in beta state!

What is it?
-----------
This is basically a collection of bash scripts to test the command line options 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!!!