8921 2016-01-13 22:54:53 +0000 Code coverage: add ability to create missing 'coverage area' reports 2020-01-09 16:45:21 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 5.99 x86 Multiple RESOLVED OBSOLETE QA REVIEW Medium enhancement Future 1 benjamin.esquivel unassigned joshuagloe leonardo.sandoval.gonzalez mhalstead richard.purdie ross.burton --- --- Don't know oldest_to_newest 57800 0 benjamin.esquivel 2016-01-13 22:54:53 +0000 Let's start by saying that a testing coverage area is a defined code section that can be executed by a test. In the source code, a coverage area can be measured by function then by branch(if/else/case/etc). A given function can present 3 testing coverage statuses: - The function is completely un-exercised (zero coverage) - The function is partially exercised (Some branches covered, some coverage) - Completely executed (all branches covered, 100% coverage) The objective of this bug is to obtain this information in an automated fashion along with the code coverage report to be able to identify which functions have zero coverage which in turn means that it should be analyzed why tests are missing to exercise that part of the code. 59230 1 leonardo.sandoval.gonzalez 2016-02-18 21:26:08 +0000 Currently, python coverage module is being used to measure code execution. The code granularity AFAIK is a module (a complete file) and not a function. With this in mind, we should do some post-processing on annotated code (coverage's annotated code) to get the functions and then the counting of executed, excluded and missing lines. 68869 2 leonardo.sandoval.gonzalez 2016-12-06 17:29:40 +0000 This is low priority for 2.3 and there is no window time to work on this area during current release. 68894 3 eduard.bartosh 2016-12-07 10:58:09 +0000 As this issue got assigned to me I'd like to know why do we need this and is this functionality can be implemented using python-coverage? 68898 4 leonardo.sandoval.gonzalez 2016-12-07 14:37:02 +0000 (In reply to comment #3) > As this issue got assigned to me I'd like to know why do we need this and is > this functionality can be implemented using python-coverage? I moved to 2.4 and for some reason it got assigned to you. For your question, oe-selftest is already using python-coverage (version 4.x), so we can produce data. The main task here is the analysis of this data. No plans to do the later during 2.3 85911 5 akuster 2019-12-22 19:32:09 +0000 I believe we are doing this via the resulttool. 86013 6 richard.purdie 2020-01-09 16:45:21 +0000 I don't believe we ever figured out correct tools for code coverage or that they are practical with the system. If anyone ever does want to do this that is fine however we have other areas QA work would likely be focused on, marking as obsolete, can be reopened if anyone is willing to progress this.