Updated ITP: Check (was: Re: Check: A unit test framework for C)

Gerrit P. Haase gp@familiehaase.de
Sat Sep 27 18:11:00 GMT 2003

Hallo Ronald,

On 25. Sep 2003 at 12:26 you wrote:

> This has my vote, but:

> * the binary package doesn't follow the now-canonical directory layout (i.e.
>   the docs are not in usr/share/doc


> * it might be a good idea to convert tutorial.lyx to something more readable
>   (like plain text)

I'll include the HTML docs which are already provided in the source
package since I cannot find sgml2html or similar up and running and I
don't want to figure out how to do it with a more recent docbook toolchain.

> * AFAIK, source packages (like binary packages) should be bzip2 compressed - 
>   not gzip compressed

Fixed, using also the canonical buildscript now.

> * The Cygwin-specific README is missing from the binary (and source) package,
>   AFAIK it's required

I added a README.

> and a question: 
> when I rebuild from source, I get failures in all of the tests when doing
> a `make check'. What are your results like?

Similar, when building oputside the souretree, well I didn't saw
yours, but I figured the following: 
Check is tested and it should report errors when there are errors, so
the testsuite tries to find some real errors, but there are obviously
bugs which makes it impossible to run the testsuite when building
outside the sourcetree.  Here is the second part of the testsuite
output, where we see that the output is the same besides the path, so
it seems that this test basically passed but reports failures because
I ran `make check` in an object directory which is not the source
directory.  The FAIL & Problem at the end is with the script checking
the 'expected' against the 'got' output and it reports FAIL because it
is not exactly similar:

xRunning suite(s): Master
33%: Checks: 3, Failures: 1, Errors: 1
ex_output.c:13:F:Core: Failure
ex_output.c:17:E:Core: (after this point) Early exit with return value 1
xRunning suite(s): Master
33%: Checks: 3, Failures: 1, Errors: 1
/tmp/expat/check-0.8.4/tests/ex_output.c:13:F:Core: Failure
/tmp/expat/check-0.8.4/tests/ex_output.c:17:E:Core: (after this point) Early exit with return value 1
FAIL: test_output.sh
Problem with ex_log_output 

More interesting is the first part, but it seems that all errors here
are also only happening when building outside the source directory.

When I build inside the source tree, I get this result:

Ran 10 tests in subordinate suite
Running suite(s): Master Lists Msg Log Limit Fork Fixture Pack
100%: Checks: 53, Failures: 0, Errors: 0
PASS: check_check
PASS: test_output.sh
PASS: test_log_output.sh
All 3 tests passed

Which is the same as I recalled from memory when I told you that I
thought all went well in my first check build.

Uploaded now to:

# setup.hint file for Check
sdesc: "Check: A unit test framework for C"
ldesc: "Check is a unit test framework for C. It features a simple interface
for defining unit tests, putting little in the way of the
developer. Tests are run in a separate address space, so Check can
catch both assertion failures and code errors that cause segmentation
faults or other signals. The output from unit tests can be used within
source code editors and IDEs.

See http://check.sourceforge.net/ for more information, including a

There are no executables, so it doesn't directly require any other


More information about the Cygwin-apps mailing list