[RELENG-23] Use Case-level code coverage Created: 03/Dec/15 Updated: 10/Dec/20 |
|
| Status: | Open |
| Project: | releng |
| Component/s: | Autorelease |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Thanh Ha (zxiiro) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
We need a way to gather information on feature level code coverage. Sonar may have an API we can query to get that information. |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 03/Dec/15 ] |
|
Colin, Tony, feel free to add more details to this bug as I've forgotten the full details of what this was. |
| Comment by Thanh Ha (zxiiro) [ 03/Dec/15 ] |
|
Also not sure if this is the best place to open the bug against but there's project that comes to mind that this would fit under. |
| Comment by Colin Dixon [ 07/Jan/16 ] |
|
As we aren't going to have "stable" features or "stable" distribution in Beryllium, this work can be pushed out to boron. |
| Comment by Robert Varga [ 10/Dec/20 ] |
|
'feature' these days means something different (we have a ton of Karaf features) and we do not want to confuse the two. If this refers to code coverage from one of the feature-parents, that just shows activation code, which I do not think is that interesting. What we need though, is measure of 'use case' code coverage, i.e. take a pre-packaged feature (static karaf, odmicro, whatever), spin it up, run its CSIT and report that coverage. It would be super neat if that showed up in sonarcloud, but that's probably a wish which may never come true. |