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

64 lines
1.6 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"
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 768 if XTENSA
Kconfig: Use the first default with a satisfied condition Up until now, Zephyr has patched Kconfig to use the last 'default' with a satisfied condition, instead of the first one. I'm not sure why the patch was added (it predates Kconfiglib), but I suspect it's related to Kconfig.defconfig files. There are at least three problems with the patch: 1. It's inconsistent with how Kconfig works in other projects, which might confuse newcomers. 2. Due to oversights, earlier 'range' properties are still preferred, as well as earlier 'default' properties on choices. In addition to being inconsistent, this makes it impossible to override 'range' properties and choice 'default' properties if the base definition of the symbol/choice already has 'range'/'default' properties. I've seen errors caused by the inconsistency, and I suspect there are more. 3. A fork of Kconfiglib that adds the patch needs to be maintained. Get rid of the patch and go back to standard Kconfig behavior, as follows: 1. Include the Kconfig.defconfig files first instead of last in Kconfig.zephyr. 2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of last in arch/Kconfig. 3. Include arch/<arch>/soc/*/Kconfig first instead of last in arch/<arch>/Kconfig. 4. Swap a few other 'source's to preserve behavior for some scattered symbols with multiple definitions. Swap 'source's in some no-op cases too, where it might match the intent. 5. Reverse the defaults on symbol definitions that have more than one default. Skip defaults that are mutually exclusive, e.g. where each default has an 'if <some board>' condition. They are already safe. 6. Remove the prefer-later-defaults patch from Kconfiglib. Testing was done with a Python script that lists all Kconfig symbols/choices with multiple defaults, along with a whitelist of fixed symbols. The script also verifies that there are no "unreachable" defaults hidden by defaults without conditions As an additional test, zephyr/.config was generated before and after the change for several samples and checked to be identical (after sorting). This commit includes some default-related cleanups as well: - Simplify some symbol definitions, e.g. where a default has 'if FOO' when the symbol already has 'depends on FOO'. - Remove some redundant 'default ""' for string symbols. This is the implicit default. Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and BT_L2CAP_TX_MTU (caused by confusing inconsistency). Piggyback some fixes for style nits too, e.g. unindented help texts. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
default 0
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
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
tests: enable user mode by default Many boards do not enable user mode in their default configuration even though they support it. However for purposes of our unit testing we really do want it on all the time. It's not enough to just flip on CONFIG_USERSPACE, the tests largely assume that CONFIG_APPLICATION_MEMORY and CONFIG_DYNAMIC_OBJECTS are enabled. Update CONFIG_TEST_USERSPACE to be on by default if CONFIG_TEST is active, and hang CONFIG_DYNAMIC_OBJECTS on it too. This problem was not previously detected as qemu_x86 has the user mode options in its defconfig and it is currently the only user mode compatible platform which runs in emulation. Fixes #7692 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-22 03:44:38 +08:00
depends on TEST
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
select USERSPACE
select APPLICATION_MEMORY
tests: enable user mode by default Many boards do not enable user mode in their default configuration even though they support it. However for purposes of our unit testing we really do want it on all the time. It's not enough to just flip on CONFIG_USERSPACE, the tests largely assume that CONFIG_APPLICATION_MEMORY and CONFIG_DYNAMIC_OBJECTS are enabled. Update CONFIG_TEST_USERSPACE to be on by default if CONFIG_TEST is active, and hang CONFIG_DYNAMIC_OBJECTS on it too. This problem was not previously detected as qemu_x86 has the user mode options in its defconfig and it is currently the only user mode compatible platform which runs in emulation. Fixes #7692 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-22 03:44:38 +08:00
select DYNAMIC_OBJECTS
default y
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
help
This option will help test the userspace mode. This can be enabled
tests: enable HW stack protection by default Userspace doesn't necessarily imply stack overflow protection for supervisor threads. Enable this as well if the hardware supports it. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-25 13:14:20 +08:00
only when CONFIG_ARCH_HAS_USERSPACE is set.
config TEST_HW_STACK_PROTECTION
bool "Enable hardware-based stack overflow detection if available"
depends on ARCH_HAS_STACK_PROTECTION
depends on TEST
select HW_STACK_PROTECTION
default y
help
This option will enable hardware-based stack protection by default
for all test cases if the hardware supports it.
tests: Kconfig: Added a new Kconfig for qemu_x86 The qemu doesn't have any flash drivers present in the drivers/flash folder. When building the tests/subsys/fs/nffs_fs_api the qemu picks up a local file to emulate the drivers. This setup was causing the failures in mapping required dependencies. This patch creates a new kconfig which can be used to test out the flash drivers. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-04-02 18:26:55 +08:00
config TEST_FLASH_DRIVERS
bool "Test flash drivers"
depends on BOARD_QEMU_X86
select FLASH_HAS_DRIVER_ENABLED
select FLASH_HAS_PAGE_LAYOUT
help
This option will help test the flash drivers. This should be enabled
only when using qemu_x86.
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