Portability improvements and ease-of-use

• Add warnings for files that are missing test cases
• Add warnings for left-over test cases for removed files
• Segfault-recovery (error-status)
• Support for automatic stubbing/mocking on PowerPC
• Clang support
• Bug-fix for error/fail output in the JUnit format
• Support for -fsanitize (works best for clang, currently)
• GCC 4 portability
• Aproximate calls to real functions with variadic arguments, like printf, sprintf, fprintf in module tests

Release work flow fix, skipping and output fix

• Fixed the documentation generator to be run before release
• Made the release build more determenistic and reduced text output
• Reduced coverage text report to console to only show non-covered
• Enabled coverage reports also when running test through valgrind

Type agnostic here, type agnostic there

This is the second release of The CUTest Framework which makes it version 1.0.1.

• Fixed release date and documentation
• Improved Makefile for release handling
• Lenient (type-agnostic) asserts enabled by default
• Refactored the assert_eq mechanism
• Allow for higher warning level by default when lenient asserts are used

Please contribute or give feedback - That's the only way this framework will evolve.

First release

I am very happy to be able to release version 1.0.0 of The CUTest Framework! A lot of work has gone in and hopefully it will ease your work with C-programming in a Test Driven Development environment.

This release contains:

• Implementation of pure C programs to generate suite specific frameworks in the src-directory
• Implementation of the testing framework and easy-to-read examples in the examples-directory
• Development of "includable" Makefiles for test-running and code coverage calculations
• Authoring of a full documentation

Please contribute or give feedback - That's the only way this framework will evolve.