Hi Harri,

This looks helpful for those writing unit tests.

It would be cool to have a similar thing for the unit test coverage.

(https://wiki.openssl.org/index.php/Unit_Testing)

- Andrejs

> On 30.04.2015, at 17:50, Harri Porten <[email protected]> wrote:
> 
> Hi!
> 
> In case you are interested in seeing the condition/decision source code 
> coverage as achieved through the OpenSSL test suite:
> 
> http://www.opencoverage.net/projects/openssl/index_html/sources.html
> 
> We now regularly generate the reports from the tip of the master branch. In 
> the hope that it'll be useful for those touching and wanting to know how well 
> it is tested.
> 
> Condition/decision coverage uncovers test combinations normally hidden in 
> line or statement coverage. Hence the much lower result of 29.6%. A long way 
> to go still :}
> 
> Please let us know if you notice that we should extend the build or test 
> configuration to enable or run more components of the code.
> 
> Some of the dead code findings may be harmless. Still, changes like the 
> attached one for b_sock.c will fix cases like
> http://www.opencoverage.net/projects/openssl/index_html/source_565.html#line688
>  and make the code more understandable at the same time. Maybe it's even an 
> unwanted leftover?
> 
> Harri.
> <b_sock.diff>_______________________________________________
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Reply via email to