Project

General

Profile

Actions

Feature #8352

closed

Calculate and visualize total code coverage

Added by Evgeny Novikov over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Urgent
Category:
-
Target version:
Start date:
08/15/2017
Due date:
10/09/2017
% Done:

100%

Estimated time:
(Total: 0.00 h)
Published in build:

Description

Recently code coverage was supported for individual verification tasks. But most likely users would like to see total code coverage. I suppose to calculate and to visualize total code coverage for each sub-job and rule specification independently.


Subtasks 2 (0 open2 closed)

Feature #8353: Calculate total code coverageClosedAlexey Polushkin08/15/2017

Actions
Feature #8354: Visualize total code coverageClosedVladimir Gratinskiy08/15/201710/09/2017

Actions

Related issues 3 (0 open3 closed)

Related to Klever - Feature #6739: Keep and visualize coverageClosedVladimir Gratinskiy02/03/2016

Actions
Related to Klever - Feature #6738: Upload coverage if soClosedAlexey Polushkin02/03/2016

Actions
Related to Klever - Feature #6737: Get coverage from static verifiers if corresponding option is setClosedAlexey Polushkin02/03/2016

Actions
Actions #1

Updated by Evgeny Novikov over 6 years ago

  • Assignee set to Ilja Zakharov
  • Target version set to 0.2

Let's do all major tasks related with coverage.

Actions #2

Updated by Evgeny Novikov over 6 years ago

  • Assignee changed from Ilja Zakharov to Evgeny Novikov

I drive this feature myself.

Actions #3

Updated by Evgeny Novikov over 6 years ago

  • Status changed from New to Resolved

It seems that most of issues were eventually fixed in bc4248a. So, by default coverage will be collected and reported for both verification tasks and totally for all rule specifications except sync:race for which Pavel wouldn't like to have cheating coverage.

Actions #4

Updated by Evgeny Novikov over 6 years ago

  • Status changed from Resolved to Closed

I merged the branch that has this feature (multicoverage) to master in 37f0c082.

Don't forget to migrate your databases and populate new preset jobs and unknown marks after update!

Actions

Also available in: Atom PDF