Unit testing for xDots
- This topic has 0 replies, 1 voice, and was last updated 6 years, 8 months ago by
.
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
Tagged: mbed, unittesting, xDot
Daniel Yang.
Daniel YangI’m attempting to put together a unit testing framework for the xDot AT-Firmware using Unity and I’m having difficulty compiling the executable for the CommandTerminal.cpp and TestCommandTerminal.cpp files.
To compile the .o files, mbed issues the arm-none-eabi-g++ command with many arguments including a generated file that contains all the includes. Using this command without the -o argument and adding the Unity and test files (.\..\test\TestCommandTerminal.c .\..\unity\src\unity.c), I get a file that appears to be in ELF as an output. It seems that linking all of the other .o files are needed since CommandTerminal.h has many dependencies.
At this point, linking all of the files to get a test executable feels extremely tedious. I’m wondering if anyone has been able to get a unit test framework, Unity or something else, running on the AT firmware or any pointers on compiling a test executable.