Why Coco is how it is | #SquishDays2021
This talk provides a high-level view on Coco for C and C++, describing how Coco works and why it is designed as it is. It explains why Coco must run as part of the compilation process and what it actually does when a compilation runs. This includes how Coco changes the source code during instrumentation, what is special about header files, and how the data about the code coverage are handled.
Oh, here is more
Webinar: Beyond the Dashboard: Efficient GUI Testing for Android Automotive with Squish
The rapid evolution of Android Automotive is reshaping in-vehicle software experiences and testing i...
Watch videoWebinar: Automated Testing of Qt Quick Ultralite Apps on MCUs
Master GUI Testing in Resource-Constrained Environments with Squish for MCUs Automated GUI testing o...
Watch videoCUDA in regulated environments – Roundtable Talk
Can CUDA be safely utilized in regulated or safety-critical software development? Join our experts t...
Watch videoWebinar: Software Architecture Checks of classic AUTOSAR projects
In classic AUTOSAR projects, dependencies between software components are implemented by a generated...
Watch video