Bridle for Zephyr
Overview
See tests/bridle for the original scope of tests, its structure and description.
Requirements
You will need an ST-LINK/V2 debug tool adapter already connected to the TiaC Magpie board, which has an already configured UART console connection.
Building and Running
Build and run the tests on target as follows:
$ west twister \
--verbose --jobs 4 --inline-logs \
--enable-size-report --platform-reports \
--device-testing --hardware-map map.yaml \
--alt-config-root bridle/zephyr/alt-config/tests \
--testsuite-root bridle/tests --tag bridle
You should see the following messages on host console:
Device testing on: | Platform | ID | Serial device | |---------------------------|----------|-----------------| | magpie_f777ni/stm32f777xx | DT04BNT1 | /dev/ttyUSB0 | INFO - JOBS: 4 INFO - Adding tasks to the queue... INFO - Added initial list of jobs to queue INFO - 1/1 magpie_f777ni/stm32f777xx bridle/common/bridle.common PASSED (device: DT04BNT1, 3.395s) INFO - 315 test scenarios (315 test instances) selected, 314 configurations filtered (314 by static filter, 0 at runtime). INFO - 1 of 1 executed test configurations passed (100.00%), 0 built (not run), 0 failed, 0 errored, with no warnings in 29.32 seconds. INFO - 1 of 1 executed test cases passed (100.00%) on 1 out of total 876 platforms (0.11%). INFO - 314 selected test cases not executed: 314 filtered. INFO - 1 test configurations executed on platforms, 0 test configurations were only built. Hardware distribution summary: | Board | ID | Counter | Failures | |---------------------------|----------|-----------|------------| | magpie_f777ni/stm32f777xx | DT04BNT1 | 1 | 0 | INFO - Saving reports... INFO - Writing JSON report .../twister-out/twister.json INFO - Writing xunit report .../twister-out/twister.xml... INFO - Writing xunit report .../twister-out/twister_report.xml... INFO - Writing target report for magpie_f777ni/stm32f777xx... INFO - Writing JSON report .../twister-out/magpie_f777ni_stm32f777xx.json INFO - Run completed