The library is a collection of objects files and by replacing one or more of these, the behavior of testape can be changed. You need to compile our own versions of these and replace them in testape library.
If you choose to make a copy of the library, please notice that it is important that the library ends with
my_os_testape.a is ok, but
testape_for_my_os.a is not ok. If the library name do
not end with testape.a it will not trigger the testape instrumentation when used on commandline.
If the name is correct, the instrumenter will analyze and generate some instrumentation code, and as its final
task, it will link this code (found in
testape.o) with your tests and the testape library.
It will by default link with the standard c library, but if you're building a bare metal configuraton this
is most likely not what you want. You can ask the testape instrumenter to skip the final link task by passing
It has been a long time since last official release and the list of bugfixes, features and supported platforms accumulating in the beta has grown substantially. I am happy to annouce that a new release is ready.more
New beta version is now available for download.more
New is this release are support for floating point validations and function mocking. Also, MinGW has been added to the list of supported platforms.more
TestApe forum is now hosted on Proboards. Support questions can be posted here or send directly on email. Due to ...more
TestApe can now be used with MinGW GCC on windows. Also supported in this beta are floating point types in validations or when mocking functionsmore
A small fix for webtty scripts, to allow the usage from Apple IPads. Tab on textarea to bring up IPad keyboard - you may have to scroll webpage beneath keyboard, in order to actually see what you're typing.
This release contains a new flexible mocking system with default mocks automatically generated for unresolved functions. Installation packages are available for GCC/Linux, GCC/CygWin as well Visual Studio 2009/Windows XP or Vista.more