Home
last modified time | relevance | path

Searched refs:coverage (Results 1 – 25 of 80) sorted by relevance

1234

/Zephyr-Core-3.7.0/tests/bsim/
Dgenerate_coverage_report.sh47 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
51 genhtml ${OUTPUT_DIR}/coverage.info ${TWISTER_COVERAGE_FILE} --output-directory \
52 ${OUTPUT_DIR}/lcov_html -q --ignore-errors source --branch-coverage --highlight --legend
/Zephyr-Core-3.7.0/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.rst13 coverage
/Zephyr-Core-3.7.0/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-Core-3.7.0/scripts/tests/twister/
DREADME.md25 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-Core-3.7.0/scripts/pylib/pytest-twister-harness/
D.gitignore27 # Unit test / coverage reports
31 .coverage
32 .coverage.*
35 coverage.xml
/Zephyr-Core-3.7.0/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-Core-3.7.0/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
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
50 bool "Host compiler gcov based code coverage"
53 Build natively with the compiler standard `--coverage` options,
54 that is with gcov/GCC-compatible coverage
57 bool "Host compiler source 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-Core-3.7.0/cmake/linker/
Dlinker_flags_template.cmake1 # coverage is a property holding the linker flag required for coverage support on the toolchain.
4 set_property(TARGET linker PROPERTY coverage)
/Zephyr-Core-3.7.0/cmake/linker/ld/gcc/
Dlinker_flags.cmake1 # The coverage linker flag is specific for gcc.
7 set_property(TARGET linker PROPERTY coverage -lgcov)
/Zephyr-Core-3.7.0/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-Core-3.7.0/
D.gitignore32 coverage-report
33 doc-coverage.info
/Zephyr-Core-3.7.0/doc/
DLICENSING.rst29 *subsys/testsuite/coverage/coverage.h*
/Zephyr-Core-3.7.0/subsys/testsuite/coverage/
DCMakeLists.txt3 zephyr_sources_ifdef(CONFIG_COVERAGE_GCOV coverage.c)
/Zephyr-Core-3.7.0/boards/qemu/riscv32_xip/
DKconfig.defconfig6 # Use thread local storage by default so that this feature gets more CI coverage.
/Zephyr-Core-3.7.0/boards/qemu/riscv32e/
DKconfig.defconfig6 # Use thread local storage by default so that this feature gets more CI coverage.
/Zephyr-Core-3.7.0/boards/qemu/riscv32/
DKconfig.defconfig6 # Use thread local storage by default so that this feature gets more CI coverage.
/Zephyr-Core-3.7.0/tests/subsys/debug/gdbstub/
Dtest_breakpoints.gdbinit16 # exit main() and continue with code coverage dump, if configured
/Zephyr-Core-3.7.0/scripts/pylib/twister/twisterlib/
Dtwister_main.py18 from twisterlib.coverage import run_coverage
213 if options.coverage:
241 or (options.coverage and not coverage_completed)
/Zephyr-Core-3.7.0/tests/kernel/device/
DCMakeLists.txt11 # However, enabling coverage forces -O0 to disable any compiler
/Zephyr-Core-3.7.0/subsys/testsuite/ztest/
DCMakeLists.txt10 ${ZEPHYR_BASE}/subsys/testsuite/coverage
/Zephyr-Core-3.7.0/scripts/ci/coverage/
Dcoverage_analysis.py29 self.report_json = self.generate_json_report( args.coverage)
231 def generate_json_report(self, coverage): argument
236 with open(coverage, 'r') as file:
374 coverage = 0.0
384 coverage = (hit/lines)*100
386 … worksheet.write_number(row,col+7,coverage,workbook.add_format({'num_format':'#,##0.00'}))
/Zephyr-Core-3.7.0/arch/common/
DCMakeLists.txt102 zephyr_compile_options($<TARGET_PROPERTY:compiler,coverage>)
103 zephyr_link_libraries_ifndef(CONFIG_NATIVE_LIBRARY $<TARGET_PROPERTY:linker,coverage>)

1234