OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/Kconfig

46 lines
1.1 KiB
Plaintext
Raw Normal View History

tests: Add a generic testing framework This framework makes testing in most parts a lot easier, since it gives an unified base to work with, removing a lot of unnecessary code from tests. This framework currently features simple assertions and basic mocking support. The framework works both with and without Zephyr running, so it can be used for real unit testing. Origin: Original Change-Id: I8c5bf2e6b8d6656b6197ee91699b61e730c1cfe3 Signed-off-by: Jaakko Hannikainen <jaakko.hannikainen@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-08-22 19:51:46 +08:00
#
# Copyright (c) 2016 Intel Corporation
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
tests: Add a generic testing framework This framework makes testing in most parts a lot easier, since it gives an unified base to work with, removing a lot of unnecessary code from tests. This framework currently features simple assertions and basic mocking support. The framework works both with and without Zephyr running, so it can be used for real unit testing. Origin: Original Change-Id: I8c5bf2e6b8d6656b6197ee91699b61e730c1cfe3 Signed-off-by: Jaakko Hannikainen <jaakko.hannikainen@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-08-22 19:51:46 +08:00
#
menu Testing
source "tests/ztest/Kconfig"
tests: add CONFIG_TEST for marking tests Mark tests with CONFIG_TEST to allow for test specific setup and configuration. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-07 05:15:53 +08:00
config TEST
bool "Mark project as a test"
default n
tests: enable coverage coverage option was dropped by mistake moving away from IS_TEST. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-09 23:46:07 +08:00
select COVERAGE if NATIVE_APPLICATION
tests: add CONFIG_TEST for marking tests Mark tests with CONFIG_TEST to allow for test specific setup and configuration. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-07 05:15:53 +08:00
help
Mark a project or an application as a test. This will enable a few
test defaults.
tests: Introduced new config option to add extra stack size for tests. This option is added in order to support Xtensa, which needs more stack than other architecture. This allows having a centralized way to change stack requirements for all tests. This extra stack size is eaqual to 0 for most architectures, except Xtensa which requires additional 768 bytes for each stack. Change-Id: Ie5dcae1dfd29018d36ef35dae22dc4c1a2ecdc14 Signed-off-by: Mazen NEIFER <mazen@nestwave.com>
2017-02-01 06:05:18 +08:00
config TEST_EXTRA_STACKSIZE
tests: Kconfig: add proper description to config option Add proper description to the TEST_EXTRA_STACKSIZE config option prompt message. Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
2018-01-30 23:39:12 +08:00
int "Test function extra thread stack size"
tests: Introduced new config option to add extra stack size for tests. This option is added in order to support Xtensa, which needs more stack than other architecture. This allows having a centralized way to change stack requirements for all tests. This extra stack size is eaqual to 0 for most architectures, except Xtensa which requires additional 768 bytes for each stack. Change-Id: Ie5dcae1dfd29018d36ef35dae22dc4c1a2ecdc14 Signed-off-by: Mazen NEIFER <mazen@nestwave.com>
2017-02-01 06:05:18 +08:00
default 0
default 768 if XTENSA
tests: add help text for TEST_EXTRA_STACKSIZE Add a description of the configuration option. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-08 00:54:38 +08:00
help
Additional stack for tests on some platform where default is not
enough.
tests: Introduced new config option to add extra stack size for tests. This option is added in order to support Xtensa, which needs more stack than other architecture. This allows having a centralized way to change stack requirements for all tests. This extra stack size is eaqual to 0 for most architectures, except Xtensa which requires additional 768 bytes for each stack. Change-Id: Ie5dcae1dfd29018d36ef35dae22dc4c1a2ecdc14 Signed-off-by: Mazen NEIFER <mazen@nestwave.com>
2017-02-01 06:05:18 +08:00
testing: add option to generate coverage reports With the native port we are able to generate coverage reports, add the needed options to the compliler and add a kconfig option to enable this on the supported architectures. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-11-22 21:28:52 +08:00
config COVERAGE
bool "Create coverage data"
tests: coverage depends on native applications Build with coverage enabled for any other boards or applications is useless at least right now. Make sure we only enable coverage for native applications. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-01-04 01:22:40 +08:00
depends on NATIVE_APPLICATION
testing: add option to generate coverage reports With the native port we are able to generate coverage reports, add the needed options to the compliler and add a kconfig option to enable this on the supported architectures. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-11-22 21:28:52 +08:00
default n
help
This option will build your application with the -coverage option
which will generate data that can be used to create coverage reports.
Currently this is fully supported only on the native POSIX port.
tests: Kconfig: Added a new kconfig. A new Kconfig to help test the userspace mode. Needed for devices which have userspace capabilities but are not enabled by default. This kconfig enables the userspace for the devices which have CONFIG_ARCH_HAS_USERSPACE enabled. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-03-19 16:47:55 +08:00
config TEST_USERSPACE
bool "Enable userspace if available"
depends on ARCH_HAS_USERSPACE
select USERSPACE
select APPLICATION_MEMORY
default n
help
This option will help test the userspace mode. This can be enabled
only when CONFIG_HAS_USERSPACE is set.
tests: Add a generic testing framework This framework makes testing in most parts a lot easier, since it gives an unified base to work with, removing a lot of unnecessary code from tests. This framework currently features simple assertions and basic mocking support. The framework works both with and without Zephyr running, so it can be used for real unit testing. Origin: Original Change-Id: I8c5bf2e6b8d6656b6197ee91699b61e730c1cfe3 Signed-off-by: Jaakko Hannikainen <jaakko.hannikainen@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-08-22 19:51:46 +08:00
endmenu