Mike Frysinger 69e5ae8458 second SUSV3 legacy check should be for macros as pointed out by psm 18 years ago
..
args f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago
assert f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago
build e9172f1313 fix license notice 18 years ago
crypt e9172f1313 fix license notice 18 years ago
ctype f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago
dlopen e5657ed358 add some more rpaths to keep the tests happy 18 years ago
inet e9172f1313 fix license notice 18 years ago
malloc e9172f1313 fix license notice 18 years ago
math e9172f1313 fix license notice 18 years ago
misc e9172f1313 fix license notice 18 years ago
mmap e9172f1313 fix license notice 18 years ago
pthread e9172f1313 fix license notice 18 years ago
pwd_grp fbf09abd20 fix license notice 18 years ago
regex e9172f1313 fix license notice 18 years ago
rpc e9172f1313 fix license notice 18 years ago
setjmp 0113e25233 fix from Paul Brook for ISO C violation in terms of handling of modifying automatic local variables between setjmp/longjmp 18 years ago
signal f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago
silly e9172f1313 fix license notice 18 years ago
stat e9172f1313 fix license notice 18 years ago
stdlib e9172f1313 fix license notice 18 years ago
string 69e5ae8458 second SUSV3 legacy check should be for macros as pointed out by psm 18 years ago
termios e9172f1313 fix license notice 18 years ago
time e9172f1313 fix license notice 18 years ago
unistd f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago
Makefile 84f59ea0e0 Move regex tests to their own subdir and dont run them if regex is disabled 18 years ago
README f88a9032ce indent 18 years ago
Rules.mak 1da8fd9223 mips64 patch from Atsushi Nemoto: 18 years ago
Test.mak 4dd72a937a Add CHECK_ONLY option to allow for running the tests on the target instead of attempting to link or compile them. Perhaps I don't fully understand the test structure, but for TLS and NPTL the tests cannot be compiled on the target without a full source tree. 18 years ago
test-skeleton.c 1bfe52d8ef update MMU ifdef check 18 years ago
testsuite.h f79ff0842e fixup my copyright notice, trim stale remnants of older notices which 18 years ago

README

-----------
For: User
-----------

The following make variables may help you in testing:
- UCLIBC_ONLY - only run tests against uClibc
- GLIBC_ONLY - only run tests against glibc
- COMPILE_ONLY - just build the tests, don't run them
- CHECK_ONLY - only run the tests, don't compile or link them
- V / VERBOSE - run tests with a lot of output

So, to just run the uClibc tests, try this:
make check UCLIBC_ONLY=1

----------------
For: Developer
----------------

The structure of this test system is:
test/ toplevel dir containing common test code
test/Rules.mak Common build code
test/Test.mak Runtime test make code
test/subdir/ code specific to a subsystem is stored in a subdir
test/subdir/Makefile describe the tests to run
test/subdir/*.c the tests

Each subdir Makefile must include the toplevel Test.mak file. Before doing so,
you may define the TESTS and TESTS_DISABLED variables. If you do not, TESTS
is built automatically based upon all the .c files in the subdir.
TESTS := foo
TESTS_DISABLED := bar
include ../Test.mak
Each test must use a similar .c name; so the "foo" test needs a "foo.c".

Additionally, the following options further control specific test behavior:
CFLAGS_foo := extra cflags to use to compile test
DODIFF_foo := compare the output of the glibc and uClibc tests (see below)
LDFLAGS_foo := extra ldflags to use to link test
OPTS_foo := extra options to pass to test
RET_foo := expected exit code of test; default is 0
WRAPPER_foo := execute stuff just before test

Or to control all tests in a subdir:
EXTRA_CLEAN := extra files to remove in the clean target
EXTRA_CFLAGS := -DFOO
EXTRA_LDFLAGS := -lpthread
OPTS :=
WRAPPER :=

If you want to compare the output of a test with known good output, then just
create a local file named "foo.out.good" and the output generated by the test
"foo" will be automatically stored in "foo.out" and compared to "foo.out.good".