wireshark/test
Nardi Ivan 3cb302f05b HTTP2, QUIC: fix "Follow Stream"
"Follow Stream" functionality assumes that all data in a single packet
belongs to the same stream. That is not true for HTTP2 and QUIC, where
we end up having data from unrelated streams.

Filter out the unwanted data directly in the protocol dissector code with
a custom `tap_handler` (as TCP already does).

Close #16093
2021-09-13 15:13:10 +00:00
..
baseline
captures HTTP2, QUIC: fix "Follow Stream" 2021-09-13 15:13:10 +00:00
config
keys
lua Carry drop count/packet ID/queue ID as options on packet block 2021-07-19 21:25:40 +00:00
protobuf_lang_files
suite_dfilter
suite_dissectors
README.test
conftest.py
fixtures.py
fixtures_ws.py
hosts.custom
hosts.global
hosts.personal
matchers.py
sampleif.py
subprocesstest.py
suite_capture.py wslog: Update test suite 2021-06-14 13:13:12 +01:00
suite_clopts.py
suite_decryption.py
suite_dissection.py git: Add test cases 2021-08-30 06:34:52 +00:00
suite_extcaps.py
suite_fileformats.py
suite_follow.py
suite_follow_dccp.py
suite_follow_multistream.py HTTP2, QUIC: fix "Follow Stream" 2021-09-13 15:13:10 +00:00
suite_io.py
suite_mergecap.py
suite_nameres.py
suite_netperfmeter.py Using col_append_sep_fstr() instead of prepending "NetPerfMeter" label. 2021-06-28 14:39:04 +00:00
suite_outputformats.py
suite_release.py
suite_sharkd.py Use wtap_blocks for packet comments 2021-07-07 18:40:24 +00:00
suite_text2pcap.py [#17517] capinfos: machine-readable filetype/encap 2021-09-10 04:25:13 +00:00
suite_unittests.py wsutil: Start adding a test suite 2021-07-11 14:39:13 +00:00
suite_wslua.py
test.py
travis-upload-artifacts.sh
util_dump_dhcp_pcap.py

README.test

Wireshark Tests

The recommended steps to prepare for and to run tests:

* Install two Python packages, pytest: `pip install pytest pytest-xdist`
* Build programs (“wireshark”, “tshark”, etc.): `ninja`
* Build additional programs for the “unittests” suite: `ninja test-programs`
* Run tests in the build directory: `pytest`

Replace `ninja test-programs` by `make test-programs` as needed.

See the “Wireshark Tests” chapter of the Developer's Guide for details:
https://www.wireshark.org/docs/wsdg_html_chunked/ChapterTests.html

If you need to update the baseline files use the following commands (on a Linux system)
mkdir ~/.config/wireshark/profiles/ctest
TZ=UTC WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 build/run/tshark -C ctest -T ek -r test/captures/dhcp.pcap > test/baseline/dhcp.ek
TZ=UTC WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 build/run/tshark -C ctest -T json -r test/captures/dhcp.pcap > test/baseline/dhcp.json
TZ=UTC WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 build/run/tshark -C ctest -T jsonraw -r test/captures/dhcp.pcap > test/baseline/dhcp.jsonraw
TZ=UTC WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 build/run/tshark -C ctest -T ek -r test/captures/dhcp.pcap -x > test/baseline/dhcp-raw.ek