https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692019-10-07T12:14:41ZOpen-Source ProjectsKlever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369282019-10-07T12:14:41ZIlja Zakharovilja.zakharov@ispras.ru
<ul><li><strong>Category</strong> changed from <i>Results processing</i> to <i>Bridge</i></li><li><strong>Assignee</strong> set to <i>Vladimir Gratinskiy</i></li></ul><p>Seems that reason of this issue is a bug in Bridge. Bridge at error trace visualization should not highlight with the red color any files which are not referred in coverage report. But it does it both for header files and outside C files which are not included into the verification task.</p> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369292019-10-07T12:51:29ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Yes, we agreed that Bridge should show empty code coverage just for those source files that are presented in coverage statistics and for which there are zeroes. Other source files, that are reachable through cross references, should not be shown as non-covered. Otherwise, users do not understand code coverage semantics easily.</p> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369302019-10-07T13:50:51ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Moreover, I suggest to show an explicit warning when users will reach source files without code coverage. This warning may be the following: "You can try another code coverage type to get code coverage for a given source file".</p> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369702019-10-12T11:51:48ZVladimir Gratinskiygratinskiy@ispras.ru
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul><p>Implemented in klever-3.0, but without an explicit warning.</p> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369712019-10-13T07:09:57ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul><p>Okay, let's think about warnings one day later. There are many other places where some help for users is strictly necessary as well.</p> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=369732019-10-13T07:12:09ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-4 status-5 priority-5 priority-high3 closed behind-schedule" href="/issues/9866">Feature #9866</a>: Show warning when users will reach source files without code coverage</i> added</li></ul> Klever - Bug #9847: Klever incorrectly shows coverage in libraries at visualization of error traceshttps://forge.ispras.ru/issues/9847?journal_id=377522020-01-16T14:25:11ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>In master.</p>