GLib Mock (glib-mock), Mocking framework, MVP stage

[otaxhu (Oscar Pernia)]

A few days ago, I created this post about an idea I had about a mocking framework for GLib.

Mocking framework for GLib

Hi everyone, I’ve been thinking about the current state of unit testing within the GLib ecosystem, specifically regarding how we handle mocking, as of now, there is no standardized way to mock non-GObject modules. Mocking in GObject Currently in GObject, mocking can be succesfully implemented by deriving the object class and overriding the virtual methods (provided the class has them) with a mocked version. However, when you need to test a module that depends on more complex functions—such as …

I immediately started development of it as a separate project, and today, it has reached an MVP stage, Linux is officially supported and tests are passing, unfortunately, Windows is not passing tests, I thought that Windows was going to work as well following the Linux approach (let the loader “automagically” link the mock function instead of the original), but no, the DLLs and the EXE have different IAT addresses/locations, so IAT hooking must be implemented for Windows.

Help is needed and very much appreciated for MacOS tests (:

Official repository:

otaxhu / glib-mock · GitLab

[otaxhu (Oscar Pernia)]

Andddd Windows test are passing! IAT hooking has been implemented!

Now I need to somehow find a way to test MacOS, even though I don’t have a MacOS PC.

EDIT: Installing _hackintosh in order to continue with testing

[otaxhu (Oscar Pernia)]

Anddd macOS tests are passing as well!

Now, the 3 main OS platforms are supported, as well as the Cygwin distro on Windows.