LibFuzzer
LibFuzzer is LLVM's built-in coverage-guided fuzzer for C and C++. Unlike AFL++, which runs as a separate process, LibFuzzer runs inside your program's process — making it 10-20x faster. It's integrated directly into Clang, requires no external tools, and is used by
Testing
Qt applications are tested with QTest, Qt's built-in unit testing framework. Unlike third-party frameworks bolted onto C++, QTest understands Qt's object model—you can test signals, slots, models, and widgets with purpose-built APIs rather than workarounds. This guide covers QTest setup, unit testing
Testing
Catch2 is popular for desktop C++ testing, but embedded developers often hit its limits when dealing with constrained targets. This guide covers advanced Catch2 configurations for bare-metal systems, cross-compilation pipelines, and testing on real or emulated hardware. Catch2 v3 vs v2 for Embedded Catch2 v3 is a header
Testing
Embedded C++ development presents unique testing challenges: hardware dependencies, limited resources, and real-time constraints make traditional unit testing difficult. GoogleTest, when configured correctly, handles all of these—letting you test firmware logic on your development machine before it ever touches silicon. Why GoogleTest for Embedded C++ GoogleTest (GTest) is
C++
ThreadSanitizer (TSan) is a dynamic analysis tool built into Clang and GCC that detects data races, deadlocks, and other concurrency bugs in C++ programs. It instruments your binary at compile time and reports races with precise stack traces. Enabling TSan Compile with -fsanitize=thread and link with the same flag:
Testing
ZeroMQ is a brokerless messaging library — there's no server to start, which makes testing both easier and harder. Easier because you can test sockets in the same process. Harder because ZeroMQ's asynchronous socket behavior creates timing issues that require careful test design. This guide covers testing
C++
ThreadSanitizer (TSan) is a runtime data race detector for C and C++ built into GCC and Clang. It instruments your code to track memory accesses and reports races the moment they occur. Unlike manual code review, TSan catches actual races with exact stack traces pointing to the lines that raced.
Testing
Memory bugs in C/C++ are notoriously hard to reproduce — use-after-free, buffer overflows, and memory leaks often cause failures far from their origin. Valgrind and AddressSanitizer (ASan) catch these at the point of occurrence with precise diagnostics. This guide shows you how to use both tools and integrate
Testing
Google Mock (GMock) is the mocking library bundled with Google Test. It lets you define mock objects from interfaces, set expectations on method calls, control return values, and verify interactions — all within your existing gtest suite. This guide covers everything from basic MOCK_METHOD to advanced argument matching. Why Mocking?
Testing
Unity is a lightweight C testing framework built for embedded systems. CMock auto-generates mock implementations from C headers, enabling you to test firmware logic without real hardware. Together they form the standard testing stack for embedded C — run on host before flashing to device. The Embedded Testing Problem Testing
Testing
CTest is CMake's built-in test runner. It discovers and executes tests defined in your CMakeLists.txt, reports results uniformly regardless of the underlying test framework (gtest, Catch2, Boost.Test, or a plain executable), and integrates with CI via standard exit codes and XML reports. What CTest Is
Testing
Catch2 is the modern C++ testing framework that prioritizes natural expression over boilerplate. Its SECTION model eliminates test fixture overhead, expression decomposition shows you actual values on failure without custom assertion messages, and BDD-style macros make test intent self-documenting. Catch2 vs Google Test: When to Choose Which Both