GTest with QNX RTOS

[salih-aydogan]

GTest is cross-compilable, which is especially useful for platforms like QNX. Also, the fact that there is a port support for QNX confirms that unit tests can be run on virtual machines with QNX installed. However, the situation regarding GMock support for integration tests seems a bit unclear. Can I use Gmock if I have an RTOS system when I want to test the integration between multiple modules?

[bmaxdk]

I am sure you can use GMock on a QNX RTOS to perform integration tests between multiple modules. Both GTest and GMock are designed to be portable and can be cross-compiled for various platforms, including RTOS environments like QNX. However, It will be tedious to make it work. You need to make minor modifications to the GMock source code or its build config to accommodate QNX-specific nuances. Their usage of threading features that need to be supported by QNX and verifying that the QNX threading model is compatible with GMock's requirements and also c++ standard library implementation available on QNX supports all the necessary features used by GMock will be challenging tho

[salih-aydogan]

Thanks for your feedback. Is there another framework you could suggest to help you overcome this situation? How can I run integration tests in the QNX RTOS environment?

[bmaxdk]

I can suggent cpputest. Since ti is easily cross-compilable for QNX and also supports both unit and integration tests with mocking capabilities, I think this can be good to try. I am sure there must be better frameworks for sure.

[Migelius941]

Yes, you can use GMock for integration testing on an RTOS like QNX, but there are some considerations:

1. Cross-Compilation:
   GMock, like GTest, is cross-compilable. Ensure you configure the build system to compile GMock for QNX, including the necessary platform-specific flags.

2. Dependencies:
   GMock relies on GTest, so ensure that GTest is also correctly built and linked for QNX.

3. RTOS Constraints:

   • Mocking in GMock involves dynamic memory allocations and STL usage, which may require additional configuration for real-time environments.
   • Performance constraints on RTOS systems might impact test execution, so keep the mocks lightweight.

4. Virtual Environment Testing:
   For integration testing between multiple modules, running GMock on a QNX virtual machine or emulator is a viable approach. Ensure the environment mimics the target RTOS as closely as possible.

5. Direct Hardware/RTOS Interaction:
   For testing modules directly interacting with hardware or RTOS APIs, use dependency injection and mock hardware abstractions to maintain test isolation.

By addressing these points, you can effectively use GMock for integration testing in an RTOS environment.