Searched full:coverage (Results 1 – 25 of 129) sorted by relevance
123456
| /Zephyr-Core-3.5.0/scripts/tests/twister/ |
| D | README.md | 23 ## 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-Core-3.5.0/tests/bsim/ |
| D | generate_coverage_report.sh | 10 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-Core-3.5.0/.github/workflows/ |
| D | codecov.yaml | 1 name: Code Coverage with codecov
90 mkdir -p coverage/reports
91 …scripts/twister --force-color -N -v --filter runnable -p ${{ matrix.platform }} --coverage -T tests
93 - name: Generate Coverage Report
95 mv twister-out/coverage.info lcov.pre.info
99 -o coverage/reports/${{ matrix.platform }}.info --rc lcov_branch_coverage=1
106 - name: Upload Coverage Results
110 name: Coverage Data (Subset ${{ matrix.platform }})
111 path: coverage/reports/${{ matrix.platform }}.info
114 name: "Publish Coverage Results"
[all …]
|
| /Zephyr-Core-3.5.0/subsys/testsuite/ |
| D | Kconfig | 30 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 …]
|
| D | CMakeLists.txt | 8 add_subdirectory_ifdef(CONFIG_COVERAGE_GCOV coverage)
|
| /Zephyr-Core-3.5.0/doc/develop/test/ |
| D | coverage.rst | 3 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 …]
|
| D | bsim.rst | 62 Test coverage and BabbleSim
66 coverage information.
69 coverage report from tests.
71 Check :ref:`the page on coverage generation <coverage_posix>` for more info.
|
| D | index.rst | 12 coverage
|
| /Zephyr-Core-3.5.0/tests/benchmarks/sys_kernel/ |
| D | README.txt | 19 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-Core-3.5.0/scripts/pylib/twister/twisterlib/ |
| D | coverage.py | 18 """ Base class for every supported coverage tool
33 logger.error("Unsupported coverage tool specified: {}".format(tool))
36 logger.debug(f"Select {tool} as the coverage tool...")
53 # Loop until the coverage data is found.
76 # if kobject_hash is given for coverage gcovr fails
100 with open(os.path.join(outdir, "coverage.log"), "a") as coveragelog:
104 … "html": "HTML report generated: {}".format(os.path.join(outdir, "coverage", "index.html")),
105 … "lcov": "LCOV report generated: {}".format(os.path.join(outdir, "coverage.info")),
106 … "xml": "XML report generated: {}".format(os.path.join(outdir, "coverage", "coverage.xml")),
107 … "csv": "CSV report generated: {}".format(os.path.join(outdir, "coverage", "coverage.csv")),
[all …]
|
| /Zephyr-Core-3.5.0/cmake/linker/ld/clang/ |
| D | linker_flags.cmake | 1 # 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.5.0/scripts/pylib/pytest-twister-harness/ |
| D | .gitignore | 27 # Unit test / coverage reports
31 .coverage
32 .coverage.*
35 coverage.xml
|
| /Zephyr-Core-3.5.0/scripts/ |
| D | requirements-build-test.txt | 3 # things used by twister or other things like code coverage or python
12 # used for code coverage
14 coverage
|
| D | .gitignore | 7 tests/twister/.coverage
|
| D | gen_gcov_files.py | 29 # Loop until the coverage data is found.
50 # if kobject_hash is given for coverage gcovr fails
|
| /Zephyr-Core-3.5.0/cmake/linker/ |
| D | linker_flags_template.cmake | 1 # 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.5.0/boards/x86/qemu_x86/ |
| D | qemu_x86_tiny_768.conf | 4 # Enable coverage regardless since this config for coverage only.
|
| /Zephyr-Core-3.5.0/tests/kernel/mem_protect/mem_map/ |
| D | testcase.yaml | 19 kernel.memory_protection.mem_map.x86_64.coverage:
27 kernel.memory_protection.mem_map.x86_64.coverage.exec:
|
| /Zephyr-Core-3.5.0/cmake/linker/ld/gcc/ |
| D | linker_flags.cmake | 1 # The coverage linker flag is specific for gcc.
7 set_property(TARGET linker PROPERTY coverage -lgcov)
|
| /Zephyr-Core-3.5.0/cmake/compiler/clang/ |
| D | compiler_flags.cmake | 17 # 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.5.0/tests/kernel/mem_protect/stackprot/boards/ |
| D | qemu_x86_tiny_768.conf | 4 # This is needed for coverage.
|
| /Zephyr-Core-3.5.0/tests/kernel/mbox/mbox_api/boards/ |
| D | qemu_x86_tiny_768.conf | 4 # Need quite some space for coverage.
|
| /Zephyr-Core-3.5.0/boards/riscv/qemu_riscv32/ |
| D | Kconfig.defconfig | 12 # this feature gets more CI coverage.
|
| /Zephyr-Core-3.5.0/doc/safety/ |
| D | safety_overview.rst | 103 c. Test coverage
146 Test coverage
149 A high test coverage, in turn, is evidence of safety that the code conforms precisely to what it
151 and has a high (ideally 100%) test coverage, it has the additional advantage of quickly detecting
153 requirements apply to safety for test coverage, and various metrics must be considered, which are
157 * Structural test coverage (entry points) 100%
158 * Structural test coverage (statements) 100%
159 * Structural test coverage (branches) 100%
161 If the 100% cannot be reached (e.g. statement coverage of defensive code) that part needs to be
|
| /Zephyr-Core-3.5.0/boards/arc/qemu_arc/ |
| D | arc_mpu_regions.c | 19 /* Region Coverage */
20 MPU_REGION_ENTRY("COVERAGE",
|
123456
