every driver needs to at least test that the firmware commands generated for a given function call match what is verified on the hardware
right now, there are many different implementations for these tests such as "_FakePySerial", unittest.mock, etc.
However, all devices call the io layer for comms. Similar to that, there is room for a good abstraction here on that same level but for testing.
I like the unittest.mock APIs, and this project will probably use it or look like it
good first issue: with agent help it's a good first issue, but it requires some taste and thinking so dont just paste into codex
every driver needs to at least test that the firmware commands generated for a given function call match what is verified on the hardware
right now, there are many different implementations for these tests such as "_FakePySerial",
unittest.mock, etc.However, all devices call the
iolayer for comms. Similar to that, there is room for a good abstraction here on that same level but for testing.I like the
unittest.mockAPIs, and this project will probably use it or look like itgood first issue: with agent help it's a good first issue, but it requires some taste and thinking so dont just paste into codex