It would be easy to create code coverage reports such as this one for libssh2:
http://www.gnu.org/software/libidn/coverage/ However, right now the self-tests are pretty minimal, so it may look rather embarrassing. I'm thinking that the self-tests could start 'sshd' with appropriate parameters that would work for ordinary users, with a dummy host key, and then invoke some libssh2 self-test against that ssh server. Do you think this would be useful? I have some sketchy ideas how it would work (using a TESTS_ENVIRONMENT script that wraps the libssh2 self-tests), and could propose some patches if I find time, so you can see more in detail what I mean. /Simon - your QA assistance :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
