OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/subsys/debug/gdbstub/testcase.yaml

69 lines
2.0 KiB
YAML
Raw Normal View History

tests: samples: gdbstub: make test out of the sample Clone samples/subsys/debug/gdbstub to tests and convert it back to a build-only sample aligned with documentation. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 17:09:01 +08:00
#
tests: gdbstub: Improve test case Gdbstub test improvements: using pytest fixtures, parametrization, and expected pattern matching on outputs from GDB and the test application. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 19:17:52 +08:00
# Copyright (c) 2020, 2023 intel Corporation.
tests: samples: gdbstub: make test out of the sample Clone samples/subsys/debug/gdbstub to tests and convert it back to a build-only sample aligned with documentation. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 17:09:01 +08:00
#
# SPDX-License-Identifier: Apache-2.0
#
tests: gdbstub: minor refactor to the testcase.yaml Change the `platform_allow` to multi-line format so that newly supported archs/boards can be added as a new line. Refactor the tags out to `common`, and add `CONFIG_ARCH_HAS_GDBSTUB` filter Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-07-23 12:53:01 +08:00
common:
tags:
- debug
- gdbstub
filter: CONFIG_ARCH_HAS_GDBSTUB
tests: samples: gdbstub: make test out of the sample Clone samples/subsys/debug/gdbstub to tests and convert it back to a build-only sample aligned with documentation. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 17:09:01 +08:00
tests:
tests: gdbstub: add build-only test Add build-only test for existing boards. Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-07-23 13:16:13 +08:00
# Basic build-only test for all platforms supporting gdbstub
debug.gdbstub.build_only:
platform_allow:
- qemu_x86
- qemu_cortex_a9
build_only: true
tests: gdbstub: qemu: Cross-validate test behavior Add a testcase to run the same test application and GDB script which we use for Zephyr GDB stub testing, but now with the GDB stub enabled at QEMU itself using it as a reference RDP backend implementation. This allows to check the Zephyr's gdbstub implementation has similar behavior as the reference. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-10 03:31:41 +08:00
# Connect to Zephyr gdbstub and run a simple GDB script
tests: gdbstub: Improve test case Gdbstub test improvements: using pytest fixtures, parametrization, and expected pattern matching on outputs from GDB and the test application. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 19:17:52 +08:00
debug.gdbstub.breakpoints:
tests: gdbstub: minor refactor to the testcase.yaml Change the `platform_allow` to multi-line format so that newly supported archs/boards can be added as a new line. Refactor the tags out to `common`, and add `CONFIG_ARCH_HAS_GDBSTUB` filter Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-07-23 12:53:01 +08:00
platform_allow:
- qemu_x86
tests: samples: gdbstub: make test out of the sample Clone samples/subsys/debug/gdbstub to tests and convert it back to a build-only sample aligned with documentation. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 17:09:01 +08:00
harness: pytest
tests: gdbstub: Improve test case Gdbstub test improvements: using pytest fixtures, parametrization, and expected pattern matching on outputs from GDB and the test application. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-08 19:17:52 +08:00
harness_config:
pytest_root:
- "pytest/test_gdbstub.py"
tests: gdbstub: Add GDB remote target parameter Add `gdb_target_remote` test parameter for GDB `target remote` command instead of its hardcoded value to allow different types of gdbstub serial interfaces as well as different TCP ports in gdbstub test suites possibly run in parallel on the same host. Move all GDB log configuration parameters from GDB script to the fixture code. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-09 21:09:26 +08:00
pytest_args:
- "--gdb_timeout"
- "20"
- "--gdb_script"
- "test_breakpoints.gdbinit"
- "--gdb_target_remote"
tests: gdbstub: qemu: Cross-validate test behavior Add a testcase to run the same test application and GDB script which we use for Zephyr GDB stub testing, but now with the GDB stub enabled at QEMU itself using it as a reference RDP backend implementation. This allows to check the Zephyr's gdbstub implementation has similar behavior as the reference. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-10 03:31:41 +08:00
- "tcp::5678"
tests: gdbstub: Add GDB remote target parameter Add `gdb_target_remote` test parameter for GDB `target remote` command instead of its hardcoded value to allow different types of gdbstub serial interfaces as well as different TCP ports in gdbstub test suites possibly run in parallel on the same host. Move all GDB log configuration parameters from GDB script to the fixture code. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-09 21:09:26 +08:00
extra_configs:
# Make sure the gdbstub port chosen is unique for this test to avoid conflicts
# when Twister runs tests in parallel on the same host.
tests: gdbstub: qemu: Cross-validate test behavior Add a testcase to run the same test application and GDB script which we use for Zephyr GDB stub testing, but now with the GDB stub enabled at QEMU itself using it as a reference RDP backend implementation. This allows to check the Zephyr's gdbstub implementation has similar behavior as the reference. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-10 03:31:41 +08:00
- CONFIG_QEMU_EXTRA_FLAGS="-serial tcp::5678,server"
# Connect to QEMU gdbstub backend and run the same GDB test script
# to check it against a reference RDP backend implementation expecting
# similar behavior as for Zephyr's gdbstub.
# Use non-default QEMU gdbstub port 1235 for this test to avoid conflicts
# with some other test on QEMU running in parallel.
debug.gdbstub_qemu.breakpoints:
tests: gdbstub: minor refactor to the testcase.yaml Change the `platform_allow` to multi-line format so that newly supported archs/boards can be added as a new line. Refactor the tags out to `common`, and add `CONFIG_ARCH_HAS_GDBSTUB` filter Signed-off-by: Yong Cong Sin <ycsin@meta.com> Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
2024-07-23 12:53:01 +08:00
platform_allow:
- qemu_x86
tests: gdbstub: qemu: Cross-validate test behavior Add a testcase to run the same test application and GDB script which we use for Zephyr GDB stub testing, but now with the GDB stub enabled at QEMU itself using it as a reference RDP backend implementation. This allows to check the Zephyr's gdbstub implementation has similar behavior as the reference. Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>
2023-10-10 03:31:41 +08:00
harness: pytest
harness_config:
pytest_root:
- "pytest/test_gdbstub.py"
pytest_args:
- "--gdb_timeout"
- "20"
- "--gdb_script"
- "test_breakpoints.gdbinit"
- "--gdb_target_remote"
- "tcp::1235"
extra_configs:
# Turn off Zephyr's gdbstub for this test case.
- CONFIG_GDBSTUB=n
- CONFIG_GDBSTUB_SERIAL_BACKEND=n
# Make sure the gdbstub port chosen is unique for this test to avoid conflicts
# when Twister runs tests in parallel on the same host.
- CONFIG_QEMU_EXTRA_FLAGS="-S -gdb tcp::1235"
# Clear QEMU default 'tcp::1234'
- CONFIG_QEMU_GDBSERVER_LISTEN_DEV=""