On Fri, 29 Jun 2007, Dan Fandrich wrote:

> So creating three new test servers to handle three remaining protocols gains
> less than 3% additional code coverage. That implies that the remaining 28%
> of the code is spread throughout the library and is going to take lots of
> effort to create exactly the right test conditions to exercise. Some code
> is going to be impossible to exercise using the public libcurl API because
> it's error handling code that won't ever be called upon.
>
> So, I think we're close the point of diminishing returns when it comes to
> code coverage. But that's not intended to dissuade anyone from adding those
> three new test servers, of course!

Thanks agin for an exellent code coverage report!

Would it be possible to get to see a report about what specific lines that
weren't involved (in any tests), to use as basis for adding new tests?

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html