Felix Moessbauer <felix.moessba...@siemens.com> writes: > This patch has been developed as part of the DPDK Userspace Summit Hackathon. > It provides a PoC for code-coverage analysis for the DPDK project. > > To generate the report, a developer simply follows the official > meson coverage workflow, described in [1]. > In doing so, both an HTML report, as well as an XML version is generated > for further processing. > > In short, the following steps are required: > > - install gcovr > - meson -Db_coverage=true build-cov > - meson compile -C build-cov > - meson test -C build-cov --suite fast-tests > - ninja coverage -C build-cov > > [1] https://mesonbuild.com/howtox.html#producing-a-coverage-report
+1 for this effort, I also think that would be a great addition so show our current coverage via a service or something like coveralls.io and possibly the dashboard. I don't know if coveralls would support the series branches we create, so I will spend a bit of time looking into it. BTW, can you also include information on the current coverage % of code base? Last I recall, some of the libraries were quite low (bpf and bbdev stick in my mind as having very low coverage). > Best regards, > Felix Moessbauer > Siemens AG > > Felix Moessbauer (1): > Add basic support for code coverage analysis > > gcovr.cfg | 8 ++++++++ > 1 file changed, 8 insertions(+) > create mode 100644 gcovr.cfg
