Searched full:coverage (Results 1 – 25 of 134) sorted by relevance
123456
| /Zephyr-Core-3.6.0/.github/workflows/ |
| D | codecov.yaml | 1 name: Code Coverage with codecov
91 mkdir -p coverage/reports
93 …rce-color -N -v --filter runnable -p ${{ matrix.platform }} --coverage -T tests --coverage-tool gc…
100 - name: Rename coverage files
103 cp twister-out/coverage.json coverage/reports/${{ matrix.platform }}.json
105 - name: Upload Coverage Results
109 name: Coverage Data (Subset ${{ matrix.platform }})
110 path: coverage/reports/${{ matrix.platform }}.json
113 name: "Publish Coverage Results"
127 path: coverage/reports
[all …]
|
| D | doc-publish.yml | 35 tar xf api-coverage/api-coverage.tar.xz -C api-coverage
56 …aws s3 sync --quiet api-coverage/coverage-report/ s3://docs.zephyrproject.org/api-coverage/${VERSI…
|
| D | doc-publish-pr.yml | 49 tar xf api-coverage/api-coverage.tar.xz -C api-coverage
65 aws s3 sync --quiet api-coverage/coverage-report/ \
66 … s3://builds.zephyrproject.org/${{ github.event.repository.name }}/pr/${PR_NUM}/api-coverage \
|
| D | doc-build.yml | 106 # API documentation coverage
107 …-m coverxygen --xml-dir doc/_build/html/doxygen/xml/ --src-dir include/ --output doc-coverage.info
109 lcov --remove doc-coverage.info \*/deprecated > new.info
110 genhtml --no-function-coverage --no-branch-coverage new.info -o coverage-report
116 tar cfJ api-coverage.tar.xz coverage-report
124 - name: upload-api-coverage
127 name: api-coverage
128 path: api-coverage.tar.xz
137 API_COVERAGE_URL="https://builds.zephyrproject.io/${REPO_NAME}/pr/${PR_NUM}/api-coverage/"
142 …echo "API Coverage Report will be available shortly at: ${API_COVERAGE_URL}" >> $GITHUB_STEP_SUMMA…
|
| /Zephyr-Core-3.6.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)
9 zephyr_include_directories_ifdef(CONFIG_COVERAGE_GCOV ${zephyr_BASE}/subsys/testsuite/coverage)
|
| /Zephyr-Core-3.6.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.6.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 | 63 Test coverage and BabbleSim
67 POSIX architecture, you can easily collect test coverage information.
70 coverage report from tests.
72 Check :ref:`the page on coverage generation <coverage_posix>` for more info.
|
| D | index.rst | 12 coverage
|
| /Zephyr-Core-3.6.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.6.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.6.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.6.0/scripts/pylib/twister/twisterlib/ |
| D | coverage.py | 25 """ Base class for every supported coverage tool
40 logger.error("Unsupported coverage tool specified: {}".format(tool))
43 logger.debug(f"Select {tool} as the coverage tool...")
60 # Loop until the coverage data is found.
84 # if kobject_hash is given for coverage gcovr fails
122 with open(os.path.join(outdir, "coverage.log"), "a") as coveragelog:
126 … "html": "HTML report generated: {}".format(os.path.join(outdir, "coverage", "index.html")),
127 … "lcov": "LCOV report generated: {}".format(os.path.join(outdir, "coverage.info")),
128 … "xml": "XML report generated: {}".format(os.path.join(outdir, "coverage", "coverage.xml")),
129 … "csv": "CSV report generated: {}".format(os.path.join(outdir, "coverage", "coverage.csv")),
[all …]
|
| /Zephyr-Core-3.6.0/boards/x86/qemu_x86/ |
| D | qemu_x86_tiny_768.conf | 4 # Enable coverage regardless since this config for coverage only.
7 # Need more stack space due to coverage being enabled.
|
| /Zephyr-Core-3.6.0/scripts/pylib/pytest-twister-harness/ |
| D | .gitignore | 27 # Unit test / coverage reports
31 .coverage
32 .coverage.*
35 coverage.xml
|
| /Zephyr-Core-3.6.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
|
| /Zephyr-Core-3.6.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.6.0/tests/kernel/mem_protect/mem_map/ |
| D | testcase.yaml | 21 kernel.memory_protection.mem_map.x86_64.coverage:
29 kernel.memory_protection.mem_map.x86_64.coverage.exec:
|
| /Zephyr-Core-3.6.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.6.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.6.0/doc/ |
| D | LICENSING.rst | 29 *subsys/testsuite/coverage/coverage.h*
|
| /Zephyr-Core-3.6.0/tests/kernel/mem_protect/stackprot/boards/ |
| D | qemu_x86_tiny_768.conf | 4 # This is needed for coverage.
|
| /Zephyr-Core-3.6.0/tests/kernel/mbox/mbox_api/boards/ |
| D | qemu_x86_tiny_768.conf | 4 # Need quite some space for coverage.
|
123456
