| /external/coreboot/Documentation/technotes/ |
| D | 2021-05-code-coverage.md | 1 # Unit Test Code Coverage
3 Code coverage for the coreboot unit tests allows us to see what lines of
5 author to see where they need to add test cases for additional coverage.
7 Code coverage requires `lcov`; install the tool if necessary by
10 Enable code coverage in your unit test build by setting the environment
12 `make` command, e.g. `COV=1 make unit-tests`.
14 The build output directory is either `build/tests` or `build/coverage`,
18 * `clean-unit-tests`
19 * `build-unit-tests`
20 * `run-unit-tests`
[all …]
|
| /external/cronet/stable/build/android/docs/ |
| D | coverage.md | 1 # Android code coverage instructions
3 These are instructions for collecting code coverage data for android
4 instrumentation and JUnit tests. For Clang(C++) code coverage refer to [clang coverage].
8 ## How JaCoCo coverage works
10 In order to use JaCoCo code coverage, we need to create build time pre-instrumented
14 ## How to collect coverage data
23 Now when building, pre-instrumented files will be created in the build directory.
25 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save
27 `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`.
29 3. The coverage results of JUnit and instrumentation tests will be merged
[all …]
|
| /external/cronet/tot/build/android/docs/ |
| D | coverage.md | 1 # Android code coverage instructions
3 These are instructions for collecting code coverage data for android
4 instrumentation and JUnit tests. For Clang(C++) code coverage refer to [clang coverage].
8 ## How JaCoCo coverage works
10 In order to use JaCoCo code coverage, we need to create build time pre-instrumented
14 ## How to collect coverage data
23 Now when building, pre-instrumented files will be created in the build directory.
25 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save
27 `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`.
29 3. The coverage results of JUnit and instrumentation tests will be merged
[all …]
|
| /external/angle/build/android/docs/ |
| D | coverage.md | 1 # Android code coverage instructions
3 These are instructions for collecting code coverage data for android
4 instrumentation and JUnit tests. For Clang(C++) code coverage refer to [clang coverage].
8 ## How JaCoCo coverage works
10 In order to use JaCoCo code coverage, we need to create build time pre-instrumented
14 ## How to collect coverage data
23 Now when building, pre-instrumented files will be created in the build directory.
25 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save
27 `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`.
29 3. The coverage results of JUnit and instrumentation tests will be merged
[all …]
|
| /external/emma/core/res/ |
| D | emma_default.properties | 1 # -------------------------------------------------------------
4 # for user-editable property overrides use one of these options:
6 # (1) option-specific command line overrides, e.g.
7 # -Dreport.txt.out.file=coverage.txt
9 # (2) '-p <options file>' command line option,
12 # (e.g., in <jre dir>\classes directory -- note that it does
15 # (4) '-Demma.*' JVM options, e.g.
16 # -Demma.report.txt.out.file=coverage.txt
19 # -Demma.properties=./myproperties.txt
20 # -------------------------------------------------------------
[all …]
|
| /external/mbedtls/scripts/ |
| D | lcov.sh | 5 Usage: $0 [-r]
6 Collect coverage statistics of library code into an HTML report.
9 1. Build the library with CFLAGS="--coverage -O0 -g3" and link the test
10 programs with LDFLAGS="--coverage".
11 This can be an out-of-tree build.
12 For example (in-tree):
13 make CFLAGS="--coverage -O0 -g3" LDFLAGS="--coverage"
14 Or (out-of-tree):
15 mkdir build-coverage && cd build-coverage &&
16 cmake -D CMAKE_BUILD_TYPE=Coverage .. && make
[all …]
|
| /external/coreboot/tests/ |
| D | Makefile.mk | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # built with code coverage never mixes with code built without code coverage.
6 testobj := $(obj)/coverage
18 TEST_CFLAGS += -g -Og
21 # Enable code coverage if requested
23 TEST_CFLAGS += --coverage
24 TEST_LDFLAGS += --coverage
36 define tests-handler
39 $(eval $(1)$(2)-$(attribute) += $($(2)-$(attribute))))
41 $(eval $(2)-$(attribute) := ))
[all …]
|
| /external/pytorch/tools/code_coverage/ |
| D | README.md | 1 # Code Coverage Tool for Pytorch
5 This tool is designed for calculating code coverage for Pytorch project.
6 …enerate both file-level and line-level report for C++ and Python tests. It will also be the tool w…
11 * *Argument `--clean` will do all the messy clean up things for you*
21 * *Final report:*
22 * File-Level: The coverage percentage for each file you are interested in
23 * Line-Level: The coverage details for each line in each file you are interested in
24 …* Html-Report (only for `gcc`): The beautiful HTML report supported by `lcov`, combine file-level …
26 * Use different stages like *--run, --export, --summary* to achieve more flexible functionality
33 The first step is to [build *Pytorch* from source](https://github.com/pytorch/pytorch#from-source) …
[all …]
|
| /external/pdfium/docs/ |
| D | code-coverage.md | 1 # Code Coverage Support for PDFium
5 This guide explains how to generate code coverage information for the PDFium
13 The tools used for code coverage are known to work on Ubuntu and Debian. They
17 Previously, the code coverage scripts required specific versions of `lcov` and
18 `llvm-cov` to be present. This is no longer true, so if you have no other need
22 ## Generating Code Coverage
29 Before generating code coverage information, you will need to have a build
30 directory with coverage enabled. This can be done by running the `gn args`
33 If not using the default directory, `out/Coverage`, then replace it with the
37 gn args out/Coverage
[all …]
|
| /external/libevent/cmake/ |
| D | CodeCoverage.cmake | 2 # Boost Software License - Version 1.0 - August 17th, 2003
8 # Software, and to permit third-parties to whom the Software is furnished to
15 # works are solely in the form of machine-executable object code generated by
20 # FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
26 # 2012-01-31, Lars Bilke
27 # - Enable Code Coverage
29 # 2013-09-17, Joakim Söderberg
30 # - Added support for Clang.
31 # - Some additional usage instructions.
33 # 2016-11-02, Azat Khuzhin
[all …]
|
| /external/pigweed/pw_build/ |
| D | coverage_report.gni | 7 # https://www.apache.org/licenses/LICENSE-2.0
21 # Expands to code coverage targets that can be used as dependencies to generate
22 # coverage reports at build time.
25 # - enable_if (optional): Conditionally activates coverage report generation
27 # - failure_mode (optional/unstable): Specify the failure mode for llvm-profdata
35 # - Coverage Settings
36 # - filter_paths (optional): List of file paths (using GN path helpers like
38 # being used. These filter source files so that the coverage report *ONLY*
42 # - ignore_filename_patterns (optional): List of file path regular expressions
43 # to ignore when generating the coverage report.
[all …]
|
| /external/openthread/third_party/mbedtls/repo/scripts/ |
| D | lcov.sh | 5 Usage: $0 [-r]
6 Collect coverage statistics of library code into an HTML report.
9 1. Build the library with CFLAGS="--coverage -O0 -g3" and link the test
10 programs with LDFLAGS="--coverage".
11 This can be an out-of-tree build.
12 For example (in-tree):
13 make CFLAGS="--coverage -O0 -g3" LDFLAGS="--coverage"
14 Or (out-of-tree):
15 mkdir build-coverage && cd build-coverage &&
16 cmake -D CMAKE_BUILD_TYPE=Coverage .. && make
[all …]
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-cov.rst | 1 llvm-cov - emit coverage information
5 --------
7 :program:`llvm-cov` *command* [*args...*]
10 -----------
12 The :program:`llvm-cov` tool shows code coverage information for
14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation
18 the :program:`llvm-cov gcov` command were called. Otherwise, a command should
22 --------
24 * :ref:`gcov <llvm-cov-gcov>`
25 * :ref:`show <llvm-cov-show>`
[all …]
|
| /external/jacoco/org.jacoco.doc/docroot/doc/ |
| D | faq.html | 1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
7 <link rel="shortcut icon" href="resources/report.gif" type="image/gif" />
8 <title>JaCoCo - FAQ</title>
40 <h3>Does JaCoCo have a plug-in for [Eclipse|Netbeans|Whatever...]?</h3>
56 For coverage report generation all classes within a group must have unique
57 names. You get this error during report generation if JaCoCo is supplied with
59 duplicate classes or create separate reports or report groups for each version.
[all …]
|
| D | ant.html | 1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
7 …<link rel="stylesheet" href="../coverage/jacoco-resources/prettify.css" charset="UTF-8" type="text…
8 <link rel="shortcut icon" href="resources/report.gif" type="image/gif" />
9 <script type="text/javascript" src="../coverage/jacoco-resources/prettify.js"></script>
10 <title>JaCoCo - Ant Tasks</title>
25 and for creating coverage reports from the recorded data. Execution data can
27 <a href="#coverage"><code>coverage</code></a>,
[all …]
|
| D | maven.html | 1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
7 …<link rel="stylesheet" href="../coverage/jacoco-resources/prettify.css" charset="UTF-8" type="text…
8 <link rel="shortcut icon" href="resources/report.gif" type="image/gif" />
9 <script type="text/javascript" src="../coverage/jacoco-resources/prettify.js"></script>
10 <title>JaCoCo - Maven Plug-in</title>
17 <span class="el_source">Maven Plug-in</span>
21 <h1>Maven Plug-in</h1>
[all …]
|
| /external/coreboot/payloads/libpayload/tests/ |
| D | Makefile.mk | 1 # SPDX-License-Identifier: GPL-2.0-only
6 # built with code coverage never mixes with code built without code coverage.
8 testobj := $(obj)/coverage
12 coverage-dir := $(testobj)/coverage_reports
20 TEST_DEFAULT_CONFIG := $(top)/configs/config.unit-tests
22 TEST_KCONFIG_AUTOHEADER := $(testobj)/libpayload-config.src.h
33 TEST_CFLAGS := -include include/kconfig.h
34 TEST_CFLAGS += -include $(coreboottop)/src/commonlib/bsd/include/commonlib/bsd/compiler.h
35 TEST_CFLAGS += -Iinclude -Iinclude/mock
36 TEST_CFLAGS += -I$(coreboottop)/src/commonlib/bsd/include
[all …]
|
| /external/pcre/ |
| D | Makefile.am | 3 AUTOMAKE_OPTIONS = subdir-objects
4 ACLOCAL_AMFLAGS = -I m4
6 ## This seems to have become necessary for building in non-source directory.
8 AM_CPPFLAGS="-I$(srcdir)/src"
20 doc/pcre2-config.txt \
25 doc/html/NON-AUTOTOOLS-BUILD.txt \
28 doc/html/pcre2-config.html \
127 doc/pcre2-config.1 \
230 # TESTS is for binary unit tests, check_SCRIPTS for script-based tests
237 # (non-user-visible) helper programs needed to build the libraries.
[all …]
|
| /external/openscreen/docs/ |
| D | code_coverage.md | 1 # Code Coverage
3 Code coverage can be checked using clang's source-based coverage tools. You
10 pre-built clang coverage tools, which are not downloaded by default. The
21 ([link](https://storage.googleapis.com/chromium-browser-clang-staging/)).
23 Once you have your GN directory (we'll call it `out/coverage`) and have
24 downloaded the tools, do the following to generate an HTML coverage report:
26 out/coverage/openscreen_unittests
27 third_party/llvm-build/Release+Asserts/bin/llvm-profdata merge -sparse default.profraw -o foo.profd…
28 …ird_party/llvm-build/Release+Asserts/bin/llvm-cov show out/coverage/openscreen_unittests -instr-pr…
31 - `default.profraw` is generated by running the instrumented code, but
[all …]
|
| /external/emma/core/java12/com/vladium/emma/report/txt/ |
| D | ReportGenerator.java | 5 * and is available at http://www.eclipse.org/legal/cpl-v10.html
9 package com.vladium.emma.report.txt;
30 import com.vladium.emma.report.AbstractReportGenerator;
31 import com.vladium.emma.report.AllItem;
32 import com.vladium.emma.report.ClassItem;
33 import com.vladium.emma.report.IItem;
34 import com.vladium.emma.report.IItemAttribute;
35 import com.vladium.emma.report.ItemComparator;
36 import com.vladium.emma.report.MethodItem;
37 import com.vladium.emma.report.PackageItem;
[all …]
|
| /external/jazzer-api/docs/ |
| D | advanced.md | 3 * [Passing JVM arguments](#passing-jvm-arguments)
4 * [Coverage instrumentation](#coverage-instrumentation)
5 * [Trace instrumentation](#trace-instrumentation)
6 * [Value profile](#value-profile)
7 * [Custom hooks](#custom-hooks)
8 * [Suppressing stack traces](#suppressing-stack-traces)
9 * [Export coverage information](#export-coverage-information)
10 * [Native libraries](#native-libraries)
11 * [Fuzzing mutators](#fuzzing-mutators)
13 <!-- Created by https://github.com/ekalinin/github-markdown-toc -->
[all …]
|
| /external/jacoco/org.jacoco.examples/build/ |
| D | build.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
3 <!--
7 http://www.eclipse.org/legal/epl-2.0
9 SPDX-License-Identifier: EPL-2.0
12 Marc R. Hoffmann - initial API and implementation
13 -->
18 Example Ant build file that demonstrates how a JaCoCo coverage report
25 <property name="result.report.dir" location="${result.dir}/site/jacoco" />
28 <!-- Step 1: Import JaCoCo Ant tasks -->
43 <!-- Step 2: Wrap test execution with the JaCoCo coverage task -->
[all …]
|
| /external/llvm/utils/lit/utils/ |
| D | check-coverage | 6 if [ ! -f setup.py ] || [ ! -d lit ]; then
12 if [ "$1" = "--generate-html" ]; then
19 set -- "tests"
22 # Check that the active python has been modified to enable coverage in its
24 if ! python -c \
25 'import sitecustomize, sys; sys.exit("coverage" not in dir(sitecustomize))' \
27 … printf 1>&2 "error: active python does not appear to enable coverage in its 'sitecustomize.py'\n"
31 # First, remove any existing coverage data files.
32 rm -f tests/.coverage
33 find tests -name .coverage.\* -exec rm {} \;
[all …]
|
| /external/python/parse_type/tasks/ |
| D | test.py | 1 # -*- coding: UTF-8 -*-
11 # -- TASK-LIBRARY:
15 # ---------------------------------------------------------------------------
17 # ---------------------------------------------------------------------------
21 # ---------------------------------------------------------------------------
23 # ---------------------------------------------------------------------------
76 behave_cmd = "{python} -m behave".format(python=sys.executable)
79 ctx.run("{behave} -f {format} {options} {args}".format(
85 "report": "Coverage report format to use (report, html, xml)",
87 def coverage(ctx, args="", report="report", append=False): function
[all …]
|
| /external/skia/tools/ |
| D | parse_llvm_coverage.py | 3 # Use of this source code is governed by a BSD-style license that can be
7 """Parse an LLVM coverage report to generate useable results."""
21 The file paths printed by llvm-cov take the form:
35 return filename.split('..')[-1].lstrip('./')
39 """Return the name of the checked-in file matching the given filename.
41 Use suffix matching to determine which checked-in files the given filename
57 def _get_per_file_per_line_coverage(report): argument
58 """Return a dict whose keys are file names and values are coverage data.
60 Values are lists which take the form (lineno, coverage, code).
72 lines = report.splitlines()
[all …]
|