Dear OpenSHH developers, in case this helps with your testing efforts: At http://www.opencoverage.net/projects/openssh/index_html/sources.html you'll find an overview of the condition/decision code coverage as achieved through a run of the test suite. The state last used is from the git master branch commit 70860b6. You might find the total coverage 27.8% to be much lower than what you've seen before. Main reason is the use of the condition/decision metric which is more ambitious than plain branch or line coverage. It requires testing of more input combinations to achieve a higher level. On the positive side chances of missing out a bug decrease. Known and potential issues: - Some statements are flagged as dead (unreachable) code which might be fine according to the project's coding style. Like a 'break' after a 'goto'. - The code configuration or test execution setup might be non-optimal and have some features or tests disabled. Todos: - Improve the test execution name to be more meaningful than just 'ssh (33)'. - Filter out false negatives like above cases of dead code. If you have any questions about the results, see a problem, or have a suggestion just let me know. While the analysis of Open Source projects started as an internal dogfooding project for our company's tool Squish Coco we also hope to contribute something back to the quality of software we all rely on. Harri.
On 24/04/15 13:06, Harri Porten wrote:> Dear OpenSHH developers, > > in case this helps with your testing efforts: > > At > > http://www.opencoverage.net/projects/openssh/index_html/sources.html > > you'll find an overview of the condition/decision code coverage as > achieved through a run of the test suite. The state last used is from > the git master branch commit 70860b6.The pages for openssh and libressl coverage are missing (fail with 404).
On Mon, 4 May 2015, ?ngel Gonz?lez wrote:> The pages for openssh and libressl coverage are missing (fail with 404).Thanks for the hint, ?ngel. There were problems with the build and test run for these projects in our infrastructure yesterday. Sorry. We'll switch to keeping old results around if current builds fail. http://www.opencoverage.net/openssh http://www.opencoverage.net/libressl If of interest, we can add a "diff" against the last public release btw. This would show whether added or changed code has any test coverage. Harri.