Unit testing with Unity and SoftDevice

RE: Unit testing with Unity and SoftDevice

Hung Bui — Mon, 23 Oct 2017 15:18:26 GMT

Hi Marcus,

Seems that you are doing system level test. For that purpose I would suggest you do what we do to test fds at system level:

Create a simple application that take input from UART or RTT for configuration test case and data.
In that application, you init the softdevice and use the data from input to run the module under test to manipulate the flash.
After the operation is finished, you can use nrfjprog to verify the flash.
We created a python script to automate providing test input and check flash output.
We don't use Unity for testing at system level.

With what you provided and the error log, seems that the softdevice init wasn't run properly. You may want to check if there is any error code when you call softdevice_enable() and softdevice_sys_evt_handler_set(). Have you made sure you configure RAM correctly ? softdevice_app_ram_start_get() only return the application RAM start address configured in the compiler, not the actual RAM needed fort the softdevice.

RE: Unit testing with Unity and SoftDevice

Marcus — Mon, 23 Oct 2017 12:17:29 GMT

Hi Hung,

I would agree that normally a unit test should isolate the module in question by replacing the interfaces it has with other modules with mock functions.

However the module in question is a low-level flash driver which makes use of the FDS from the SDK to perform memory transactions in flash. To test that the memory contents are correctly being manipulated, the SoftDevice is required, and without having performed these tests I would argue that the module hasn't been properly tested.

Mocking SoftDevice function calls so that they retain their core functionality is an option, but would probably take a lot of work. I suppose you could also argue that, as Nordic are already unit testing the SDK modules, that there's no need for me to go that low-level with my tests and I can just drop the calls in as-is - but that seems a little risky in my opinion.

RE: Unit testing with Unity and SoftDevice

Hung Bui — Thu, 19 Oct 2017 13:19:55 GMT

Hi Marcus,

Normally, when you unit test a module, you would need to create mock functions outside of the module that being tested. This is applied also for the softdevice API called from the module.

That's what we do when we do unit test for our SDK. We check the params passed to the Softdevice API are correct, check if the APIs called correct number of time and in correct order, etc.

I assume in your case, you are doing on-target testing and you actually need the device to operate to test ? shouldn't it be at system level test, not unit test ? Could you share some more information ?

RE: Unit testing with Unity and SoftDevice

Yaniv Nis — Tue, 17 Oct 2017 15:26:36 GMT

Hi,

We are working at Jumper on a virtual device framework that enables what you need. Contact me at yaniv@jumper.io so I'll better understand your needs and I'll add you to our free beta program.

Best,

Yaniv