Revision history [back]

Wireshark development is largely driven by volunteers, most of them focus only on a narrow area. There are many open issues on the bug tracker (https://bugs.wireshark.org/), but many of them might not be relevant when you use Wireshark to test your product. As others have said, there is code review, automated tests (a small test suite, fuzzing, build tests).

As for how some organizations approach the problem of using a "certified" tool, the Thread Group have developed Wireshark dissectors and use it for in their certification process. For this purpose, they record a specific version of Wireshark that was used for testing to ensure that the results are reproducible. This approach seems reasonable for their needs where they want to ensure that implementations adhere to the standard.