Csmith is a random generator of C programs. It's primary purpose is to find compiler bugs with random programs, using differential testing as the test oracle. Csmith can be used outside of the field of compiler testing. If your application needs a test suite of C programs and you don't bother to write them, feel free to give Csmith a try. Csmith outputs C programs free of undefined behaviors (believe us, that's not trivial), and the statistics of each generated program. 

modm: a C++20 library generator for AVR and ARM Cortex-M devices

modm (pronounced like dial-up "modem") is a toolbox for building custom C++20 libraries tailored to your embedded device. modm generates startup code, HALs and their implementations, communication protocols, drivers for external devices, BSPs, etc… in a modular, customizable process that you can fine-tune to your needs. This project also has a forum for discussions and a technical blog to document larger design concepts. modm is optimized for the harsh requirements of the Eurobot competition, where our robots need to run reliably and completely autonomously for the game's 100 second duration. Our robots contain a lot of different microcontrollers, some without a lot of resources, so modm needs to fulfill a diverse set of objectives, like small code size with small memory consumption, predictable program flow, extreme portability. The library source code is licensed as MPLv2 with any external source code under compatible licenses (BSD, Apache2, MIT). So feel free to fork this project and adapt it to your needs. The only thing we ask of you is to contribute your changes back so everyone can benefit. Efficient and fast object-oriented C++20 API. Support for thousands of AVR and ARM Cortex-M microcontrollers from Microchip, STMicroelectronics and Raspberry Pi. Build system agnostic: Choose SCons, CMake, Makefile or use your own. Modular, data-driven, target-specific HAL generation using the lbuild code generator. No memory allocations in HAL with very low overall RAM consumption. Highly configurable modules with sensible defaults and lots of documentation. Cross-platform peripheral interfaces incl. bit banging:  GPIO, External Interrupt and IO expanders. ADC, DAC and Comparators. UART, I2C, SPI, CAN and Ethernet. Interfaces and drivers for many external I2C and SPI sensors and devices. Debug/logging system with IOStream and printf interface. Lightweight, stackless threads and resumable functions using cooperative multitasking. Functional (partial) libstdc++ implementation for AVRs. Useful filter, interpolation and geometric algorithms. Lightweight unit testing system (suitable for AVRs). Hundreds of tests to ensure correct functionality. Integration of useful third-party software:  FreeRTOS and FreeRTOS+TCP. CMSIS and CMSIS-DSP. ETL. TinyUSB. FatFS. ROSserial. CrashCatcher. 

CMock is a mock and stub generator and runtime for unit testing C. It's been designed to work smoothly with Unity Test, another of the embedded-software testing tools developed by ThrowTheSwitch.org. CMock automagically parses your C headers and creates useful and usable mock interfaces for unit testing. Give it a try!. If you don't care to manage unit testing builds yourself, consider checking out Ceedling, a test-centered build manager for unit testing C code. 

Sysmon event simulation utility which can be used to simulate the attacks to generate the Sysmon Event logs for testing the EDR detections and correlation rules by Blue teams.

SysmonSimulator is an Open source Windows event simulation utility created in C language, that can be used to simulate most of the attacks using WINAPIs. This can be used by Blue teams for testing the EDR detections and correlation rules. I have created it to generate attack data for the relevant Sysmon Event IDs. 

Fast multi-dimensional generalized histogram with convenient interface for C++14

Coded with ❤. Powered by the Boost community and the Scikit-HEP Project. Licensed under the Boost Software License. Supported compiler versions gcc &gt;= 5.5, clang &gt;= 3.8, msvc &gt;= 14.1 Supported C++ versions 14, 17, 20. Boost.Histogram is a very fast state-of-the-art multi-dimensional generalised histogram class for the beginner and expert alike. Check out the full documentation. 💡 Boost.Histogram is a mature library with 100 % of code lines covered by unit tests, is benchmarked for performance, and has extensive documentation. If you still find some issue or find the documentation lacking, tell us about it by submitting an issue. Chat with us on the Boost channel on Slack and Gitter. Extremely customisable multi-dimensional histogram Simple, convenient, STL and Boost-compatible interface Counters with high dynamic range, cannot overflow or be capped [1] Better performance than other libraries (see benchmarks for details) Efficient use of memory [1] Hand-crafted C++17 deduction guides for axes and histogram types Support for custom axis types: define how input values should map to indices Support for under-/overflow bins (can be disabled individually to reduce memory consumption) Support for axes that grow automatically with input values [2] Support for weighted increments Support for profiles and more generally, user-defined accumulators in cells [3] Support for completely stack-based histograms Support for compilation without exceptions or RTTI [4] Support for adding, subtracting, multiplying, dividing, and scaling histograms Support for custom allocators Support for programming with units [5] Optional serialization based on Boost.Serialization 

A collection of awful archetypes to ease the testing of generic C++ libraries

When writing a generic library, one often needs to test generic components with types having infrequent characteristics. This is to make sure that a generic component is not assuming more about its inputs than it should. libawful is a collection of types with unusual properties that can be used to check for corner cases when implementing generic components. The project contains a single header, &lt;awful.hpp&gt;, which defines all the archetypes. 

Tool that generates unit test by C/C++ source code, trying to reach all branches and maximize code coverage

UTBotCpp generates test cases by code, trying to cover maximum statements and execution paths. We treat source code as source of truth assuming that behavior is correct and corresponds to initial user demand. Generated tests are placed in so-called regression suite. Thus, we fixate current behavior by generated test cases. Using UTBotCpp developers obtain full control of their code. No future change can break the code without being noticed once it's covered with tests generated by UTBot. This way, modifications made by developers to an existing code are much safer. Hence, with the help of generated unit tests, UTBot provides dramatic code quality improvement. 