This is part-1 of the talk "Testing of Event-Driven Embedded Software with Python" that Miro Samek presented at the [Embedded Online Conference in May 2022](https://embeddedonlineconference.com/session/Testing_of_Event_Driven_Embedded_Software_with_Python)

This part starts with the general strategy for testing event-driven software. Next, at 5:35, you'll get a clear explanation of the traditional approach based on the Mock Objects illustrated with an example.

Finally in this part, at 13:00, you'll get introduced to the concept of Software Tracing, which conceptually is similar to "Testing with printf".

NOTE:
All code presented in this video is available on GitHub in the qpc repository:
https://github.com/QuantumLeaps/qpc/tree/master/examples/qutest

Quantum Leaps

A presentation comparing traditional unit testing with mocking versus software tracing for event-driven embedded systems. Using an LED bar gizmo example, it demonstrates how mock objects work with the Unity framework and CMock, then introduces software tracing as a simpler alternative to mocking. The talk covers QP/Spy, a binary-format software tracing system for embedded C, showing how it replaces printf-based debugging with efficient binary trace records that can run on both host machines and embedded targets like STM32 Nucleo boards. Part 1 sets up the foundation for an automated testing system based on software tracing (QTest) to be shown in Part 2.

Testing of Event-Driven Embedded Software with Python Part-1