On the content, it seems that a large majority (70%+) of the code is
tested. However, there is still functionality and error paths that
remain untested. There are code paths such as TPM which cannot be
tested in an automated way (we would need some kind of TPM 1.2
emulator), and openpgp support will most likely never get any
improvement in testing since it is deprecated code. For the rest, I'd
appreciate help on increasing the existing's code test coverage.
The coverage pages are set to auto generate on every release of gnutls.
Nice! It looks like the Guile bindings are not built. Could you enable
Several years ago, running the test suite that comes with the Guile
bindings noticeably improved test coverage of GnuTLS. The situation has
probably changed since then, but it might still be a good thing to have.
> The coverage pages are set to auto generate on every release of gnutls.
There is a coverage build as part of the CI jobs, but it only updates
the coverage percentage number as shown in gitlab.com/gnutls/gnutls.
It does not update the web pages, because I haven't figured a way to
do that without overwriting the existing pages (which in that case are
the www.gnutls.org web site). I'm not a gitlab power user, so any
suggestion is welcome.