Test coverage & fuzzing

[krizhanovsky]

Functional tests coverage

Need to deploy a gcov in https://github.com/tempesta-tech/tempesta-test . A test coverage report must be generated (preferably for each CI build or at least by a separate test run). gcov(1) show percentage coverage, so the output can be used directly in the report. Maybe it makes sense to use lcov(1) to get HTML output for all the files at once.

The task is crucial since high (as close to 100% as possible) statement coverage is the minimal requirement for GA (high branch and predicate coverages are also wished).

Fuzzing

Kcov with AFL can should be used for fuzzing, see A gentle introduction to Linux Kernel fuzzing.

This must be done at least for TLS handshakes and the HTTP parser - the most security sensitive pieces of code. Different functions should be called by the fuzzer to reveal issues like #1683 , i.e. there should be unit tests using fuzzing.

Open source tools to consider:

• https://github.com/OpenRCE/sulley

References

• linux/kernel/gcov.
• Writing Better Function Tests with GCOV

[krizhanovsky]

We need to know our test coverage to release Beta: 80% is absolute minimum, 95% is the desired value.