All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Marcin Zapolski <marcinx.a.zapolski@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: add code coverage report generation guide
Date: Sun, 24 May 2020 23:22:57 +0200	[thread overview]
Message-ID: <5114883.9lh0I85yue@thomas> (raw)
In-Reply-To: <20190923121533.1191-1-marcinx.a.zapolski@intel.com>

What is the status of this patch?
There was no review.


23/09/2019 14:15, Marcin Zapolski:
> Add unit tests and code coverage reports generation guides to Meson
> build documentation.
> 
> Signed-off-by: Marcin Zapolski <marcinx.a.zapolski@intel.com>
> ---
> v2: fix trailing whitespaces
> ---
>  doc/build-sdk-meson.txt | 40 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
> 
> diff --git a/doc/build-sdk-meson.txt b/doc/build-sdk-meson.txt
> index fc7fe37b5..691950a62 100644
> --- a/doc/build-sdk-meson.txt
> +++ b/doc/build-sdk-meson.txt
> @@ -192,3 +192,43 @@ From examples/helloworld/Makefile::
>  
>  	build:
>  		@mkdir -p $@
> +
> +Running DPDK unit-tests
> +-----------------------
> +
> +To run all defined unit tests we can use the command::
> +
> +	meson test -C build
> +
> +from DPDK root direcotry, where build is the project build directory. It is the
> +equivalent to running::
> +
> +	ninja test
> +
> +in ``build`` directory.
> +To run a set of tests belonging to a specific test suite, we can use::
> +
> +	meson test -C build --suite <test-suite>
> +
> +where <test-suite> can be ``fast-tests``, ``perf-tests``, ``driver-tests`` or
> +``debug-tests``.
> +
> +Generating code coverage reports
> +--------------------------------
> +
> +To gather code coverage data, we need to give meson the  ``-Db_coverage=true``
> +command line flag::
> +
> +	meson configure -Db_coverage=true
> +
> +To generate code coverage reports, the ``gcovr`` tool needs to be installed. On
> +most linux distributions it is available through the package manager, eg.
> +``sudo apt-get install gcovr``.
> +Then, after running the tests, we can generate the reports simply by running::
> +
> +	ninja coverage
> +
> +in project build directory. The reports will be generated in
> +``build/meson-logs`` directory, in ``html``, ``xml`` and ``txt`` formats.
> +To generate the coverage reports in only one format, we can use one of
> +``coverage-html``, ``coverage-xml`` or ``coverage-txt`` meson targets.





  reply	other threads:[~2020-05-24 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23  8:52 [dpdk-dev] [PATCH] doc: add code coverage report generation guide Marcin Zapolski
2019-09-23 12:15 ` [dpdk-dev] [PATCH v2] " Marcin Zapolski
2020-05-24 21:22   ` Thomas Monjalon [this message]
2023-06-12 16:07     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5114883.9lh0I85yue@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marcinx.a.zapolski@intel.com \
    --cc=marko.kovacevic@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.