// ... call test code here? // ... some code here?

Embedded / IoT systems often require testing of code that interacts with hardware. Several approaches are used for this:

• Unit testing with mocks: hardware interfaces are replaced with dummy objects to test logic without real hardware.
• Integration testing on emulators or test benches: code is run in an environment as close as possible to the real device.
• Testing on the target device: performed directly on the hardware to verify interaction with peripherals.

Example of calling test code with mocks in C++:

class SensorInterface {
public:
    virtual int ReadValue() = 0;
};

class SensorMock : public SensorInterface {
public:
    int ReadValue() override { return 42; } // fixed value for testing
};

void TestSensorProcessing(SensorInterface& sensor) {
    int val = sensor.ReadValue();
    // logic check of val
}

int main() {
    SensorMock mock;
    TestSensorProcessing(mock);
    return 0;
}

Thus, the test code is called using mock objects that simulate hardware interfaces.