Re: ztest and code coverage on actual hardware

Perkowski, Maciej

Hi Jamie,

I am not sure what are you referring to. I am running daily on-target tests on quite a big setup internally at Nordic and I haven’t observed any major breakdown. You can find the on-target results here: The latest one with Nordic boards is this one:

I cannot access the devzone link you’ve added (waiting to get a proper permission). If we move the discussion to the zephyr’s official discord, to the testing channel I will try to provide some more direct help to you.


Maciej Perkowski | Software Test Developer
M +48 728 395 111 | Kraków, Poland |



From: Cufi, Carles <Carles.Cufi@...>
Sent: Tuesday, November 23, 2021 10:27 AM
To: jamie.mccrae@...; devel@...; garrett@...; Perkowski, Maciej <Maciej.Perkowski@...>
Subject: RE: [Zephyr-devel] ztest and code coverage on actual hardware


+ Maciej


From: devel@... <devel@...> On Behalf Of lairdjm via
Sent: 23 November 2021 10:25
To: devel@...; garrett@...
Subject: Re: [Zephyr-devel] ztest and code coverage on actual hardware



After going back and forth between nRF connect SDK 1.7.1 and current top of zephyr, it seems that something in the test system when running on actual hardware has been majorly broken in the current mainline zephyr version. As of right now I can't get anything working on real hardware and at this point I'm considering using a different test system altogether. @Nasif can you comment on these issues? Things seems to work OK on nRF connect SDK 1.7.1, but on mainline zephyr anything jlink based is broken, anything nordic also seems to be broken.




On Fri, 2021-11-19 at 11:32 -0500, Garrett LoVerde via wrote:

I have no extra insight to provide as I've only ever used Mbed OS's on device automated test infrastructure.


But I will say that I plan to get a device test farm running at some point and will need a solution for Zephyr.


-Garrett LoVerde


Join { to automatically receive all group messages.