mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-14 12:41:56 +00:00
eb2d8b418c
Code in samples does not follow an standarized format for reporting success or operation failure -- thus we use markup (in file sample.tc) to specify what shall be found in the console to consider execution a success. There is a few functional code modifications that add/extend console messages so verification is possible or easier: - hello_world, synchronization: extend the success message to also print which core is running the testcase - pci_enum: print message on success. Change-Id: Idb6cea03adebe97d97854603f963f4e3d4cb856a Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
14 lines
410 B
Plaintext
14 lines
410 B
Plaintext
# @testcase dynamic
|
|
#
|
|
# @targets \
|
|
# board:(?!arduino_101_sss) \
|
|
# board:(?!quark_se_sss_devboard) \
|
|
#
|
|
# @eval console-rx %(console)s:15 shell>
|
|
# @eval console-tx %(console)s:1 ping\r\n
|
|
# @eval console-rx %(console)s:15 pong
|
|
# @eval console-tx %(console)s:1 ticks\r\n
|
|
# @eval console-rx %(console)s:15 ticks:
|
|
# @eval console-tx %(console)s:1 highticks\r\n
|
|
# @eval console-rx %(console)s:15 highticks:
|