Home
last modified time | relevance | path

Searched full:coverage (Results 1 – 25 of 145) sorted by relevance

123456

/Zephyr-latest/scripts/tests/twister_blackbox/
Dtest_coverage.py28 'coverage.log', 'coverage.json',
29 'coverage'
47 'coverage.log', 'coverage.json',
48 'coverage'
57 'coverage.log', 'coverage.json',
58 'coverage', os.path.join('coverage','coverage.xml')
65 'coverage.log', 'coverage.json',
66 'coverage', os.path.join('coverage','coverage.sonarqube.xml')
73 'coverage.log', 'coverage.json',
74 'coverage', os.path.join('coverage','coverage.txt')
[all …]
/Zephyr-latest/.github/workflows/
Dcodecov.yaml1 name: Code Coverage with codecov
103 mkdir -p coverage/reports
108 -i --force-color -N -v --filter runnable -p ${{ matrix.platform }} --coverage \
109 -T tests --coverage-tool gcovr -xCONFIG_TEST_EXTRA_STACK_SIZE=4096 -e nano \
117 - name: Rename coverage files
120 mv twister-out/coverage.json coverage/reports/${{matrix.normalized}}.json
122 - name: Upload Coverage Results
126 name: Coverage Data (Subset ${{ matrix.normalized }})
128 coverage/reports/${{ matrix.normalized }}.json
132 name: "Publish Coverage Results"
[all …]
Ddoc-publish.yml35 if [ -f api-coverage/api-coverage.tar.xz ]; then
36 tar xf api-coverage/api-coverage.tar.xz -C api-coverage
58 if [ -d api-coverage/coverage-report ]; then
59 …aws s3 sync --quiet api-coverage/coverage-report/ s3://docs.zephyrproject.org/api-coverage/${VERSI…
Ddoc-publish-pr.yml60 if [ -f api-coverage/api-coverage.tar.xz ]; then
61 tar xf api-coverage/api-coverage.tar.xz -C api-coverage
80 if [ -d api-coverage/coverage-report ]; then
81 aws s3 sync --quiet api-coverage/coverage-report/ \
82 … s3://builds.zephyrproject.org/${{ github.event.repository.name }}/pr/${PR_NUM}/api-coverage \
Ddoc-build.yml100 # API documentation coverage
101 …-m coverxygen --xml-dir doc/_build/html/doxygen/xml/ --src-dir include/ --output doc-coverage.info
103 lcov --remove doc-coverage.info \*/deprecated > new.info
104 genhtml --no-function-coverage --no-branch-coverage new.info -o coverage-report
111 tar --use-compress-program="xz -T0" -cf api-coverage.tar.xz coverage-report
119 - name: upload-api-coverage
122 name: api-coverage
123 path: zephyr/api-coverage.tar.xz
132 API_COVERAGE_URL="https://builds.zephyrproject.io/${REPO_NAME}/pr/${PR_NUM}/api-coverage/"
137 …echo "API Coverage Report will be available shortly at: ${API_COVERAGE_URL}" >> $GITHUB_STEP_SUMMA…
/Zephyr-latest/subsys/testsuite/
DKconfig30 The code coverage report generation is only available on boards
31 with enough spare RAM to buffer the coverage data, or on boards
34 config COVERAGE config
35 bool "Create coverage data"
38 This option will build your application with the -coverage option
39 which will generate data that can be used to create coverage reports.
41 https://docs.zephyrproject.org/latest/guides/coverage.html
44 prompt "Coverage mode"
47 depends on COVERAGE
50 bool "Host compiler gcov based code coverage"
[all …]
DCMakeLists.txt8 add_subdirectory_ifdef(CONFIG_COVERAGE_GCOV coverage)
9 zephyr_include_directories_ifdef(CONFIG_COVERAGE_GCOV ${ZEPHYR_BASE}/subsys/testsuite/coverage)
/Zephyr-latest/scripts/tests/twister/
DREADME.md23 ## Twister Coverage
25 The coverage for all the tests can be run using the command below. This will collect all the tests …
28 coverage run -m pytest $ZEPHYR_BASE/scripts/tests/twister/
31 Then we can generate the coverage report for just twister script using
34 coverage report -m $ZEPHYR_BASE/scripts/pylib/twister/
37 To generate the coverage report for twister script use below command
40 coverage report -m $ZEPHYR_BASE/scripts/twister
43 The html coverage report for twister can be generated using
46 coverage html twister
49 If needed,the full coverage html report can be generated in every run of "pytest" in the tests dire…
/Zephyr-latest/tests/bsim/
Dgenerate_coverage_report.sh10 Generate an html coverage report for BabbleSim tests
15 Coverage files will be searched for in the folder pointed by
22 By default it takes all coverage information generated by all run tests
25 You can also merge in the twister coverage report by setting
27 TWISTER_COVERAGE_FILE=\${ZEPHYR_BASE}/twister-out/coverage.info
29 twister -p nrf52_bsim -T tests/bluetooth/ --coverage
31 Note: Generating a coverage report for many tests is a lengthy process
47 lcov --capture --directory ${WORK_DIR} --output-file ${OUTPUT_DIR}/coverage.pre.info \
49 lcov --remove ${OUTPUT_DIR}/coverage.pre.info *generated* \
50 --output-file ${OUTPUT_DIR}/coverage.info -q --rc lcov_branch_coverage=1
[all …]
/Zephyr-latest/doc/develop/test/
Dcoverage.rst3 Generating coverage reports
6 With Zephyr, you can generate code coverage reports to analyze which parts of
15 Test coverage reports in embedded devices or QEMU
20 `GCC GCOV <gcov_>`_ is a test coverage program
21 used together with the GCC compiler to analyze and create test coverage reports
25 In Zephyr, gcov collects coverage profiling data in RAM (and not to a file
32 There are 2 parts to enable this feature. The first is to enable the coverage for the
34 code coverage with gcov is a function of RAM available. Therefore ensure that the
35 device has enough RAM when enabling the coverage for it. For example a small device
37 cases which consume more RAM will crash when coverage is enabled.
[all …]
Dindex.rst14 coverage
/Zephyr-latest/tests/benchmarks/sys_kernel/
DREADME.txt19 TEST COVERAGE:
29 TEST COVERAGE:
40 TEST COVERAGE:
52 TEST COVERAGE:
62 TEST COVERAGE:
74 TEST COVERAGE:
86 TEST COVERAGE:
96 TEST COVERAGE:
108 TEST COVERAGE:
120 TEST COVERAGE:
[all …]
/Zephyr-latest/cmake/linker/ld/clang/
Dlinker_flags.cmake1 # The coverage linker flag is specific for clang.
3 set_property(TARGET linker PROPERTY coverage --coverage)
5 set_property(TARGET linker PROPERTY coverage -fprofile-instr-generate -fcoverage-mapping)
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dcoverage.py27 """ Base class for every supported coverage tool
46 logger.error(f"Unsupported coverage tool specified: {tool}")
49 logger.debug(f"Select {tool} as the coverage tool...")
67 # Loop until the coverage data is found.
118 # if kobject_hash is given for coverage gcovr fails
165 with open(os.path.join(outdir, "coverage.log"), "a") as coveragelog:
170 os.path.join(outdir, "coverage", "index.html")
173 os.path.join(outdir, "coverage.info")
176 os.path.join(outdir, "coverage", "coverage.xml")
179 os.path.join(outdir, "coverage", "coverage.csv")
[all …]
Denvironment.py25 from twisterlib.coverage import supported_coverage_formats
118 title="Code coverage",
119 description="Build with code coverage support, collect code coverage statistics "
120 "executing tests, compose code coverage report at the end.\n"
360 coverage_group.add_argument("--enable-coverage", action="store_true",
361 help="Enable code coverage collection using gcov.")
363 coverage_group.add_argument("-C", "--coverage", action="store_true",
364 help="Generate coverage reports. Implies "
365 "--enable-coverage to collect the coverage data first.")
368 help="Path to the 'gcov' tool to use for code coverage reports. "
[all …]
Dtwister_main.py15 from twisterlib.coverage import run_coverage
187 if options.coverage and not options.disable_coverage_aggregation:
189 report.coverage_status, report.coverage = run_coverage(options, tplan)
191 logger.info("Skipping coverage report generation due to --build-only.")
214 or (options.coverage and not report.coverage_status)
/Zephyr-latest/scripts/pylib/pytest-twister-harness/
D.gitignore27 # Unit test / coverage reports
31 .coverage
32 .coverage.*
35 coverage.xml
/Zephyr-latest/scripts/
Drequirements-build-test.txt3 # things used by twister or other things like code coverage or python
12 # used for code coverage
14 coverage
D.gitignore7 tests/twister/.coverage
/Zephyr-latest/tests/lib/cpp/cxx/
Dprj.conf11 # coverage in some areas. But: 1. combinatorial explosion, 2. it does
20 # Enable more features and C++ coverage in device.h, pm/device.h, pm.h...
/Zephyr-latest/cmake/linker/ld/gcc/
Dlinker_flags.cmake1 # The coverage linker flag is specific for gcc.
7 set_property(TARGET linker PROPERTY coverage -lgcov)
/Zephyr-latest/cmake/linker/
Dlinker_flags_template.cmake21 # coverage is a property holding the linker flag required for coverage support on the toolchain.
24 set_property(TARGET linker PROPERTY coverage)
/Zephyr-latest/cmake/compiler/clang/
Dcompiler_flags.cmake17 # clang flags for coverage generation
19 set_compiler_property(PROPERTY coverage -fprofile-instr-generate -fcoverage-mapping)
21 set_compiler_property(PROPERTY coverage --coverage -fno-inline)
/Zephyr-latest/tests/kernel/mem_protect/mem_map/
Dtestcase.yaml26 kernel.memory_protection.mem_map.x86_64.coverage:
34 kernel.memory_protection.mem_map.x86_64.coverage.exec:
/Zephyr-latest/tests/boards/nrf/coresight_stm/
Dtestcase.yaml39 boards.nrf.coresight_stm.dict.coverage:
53 boards.nrf.coresight_stm.coverage:

123456