My co-worker figured out the solution. The directions should read: Build command: west build -p auto -b qemu_x86_64 samples/drivers/uart/echo_bot Run command: west build -t run That is, instead of "-b

#test #uart

Hi, I've tried the 3 samples under samples/subsys/console (echo, getchar, getline) and they all have a very similar problem: no echo of my input and no error displayed when I run after building for qe

#test #uart

Hi, I'm trying to run the samples/drivers/uart/echo_bot sample on qemu_x86 under Ubuntu. I can run this sample on my hardware when I build for that board, so I believe I am operating it ok. But when I

#test #uart

How are you invoking twister? You can do the following for new boards: ./scripts/twister -p <NEW BOARD NAME> That will limit twister to just build tests for the new board you are adding. You can also

#nrf5 #test #nrf52 #nrf53

Greetings, I'm preparing some PRs to add our u-blox nRF52 and nRF53 EVK boards to Zephyr. I'd like to run twister locally and seem to have things working. I'm running out of drive space due to the siz

#nrf5 #test #nrf52 #nrf53

Hi Stefan, Why not join the testing working group and share your input there as well? https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#testing-working-grou

#test #ztest

Thanks for the information and feedback. In my eyes it would be perfect if, on the long run, a formalized test system is available. I think for the users it would be perfect to have the possibility to

#test #ztest

Really quickly, I’m not sure if we’ve done anything like this. Typically the testing support has been focused on what we’d use as a developer community for the zephyr project. So we have things like t

#test #ztest

Hey, I like to do some code tests for parts of my firmware. I struggling to find out how to setup testing. There is some explanation at https://docs.zephyrproject.org/1.12.0/subsystems/test/ztest.html

#test #ztest