3 A lot of the tests written in C use assert(), only printing 'ok' at the end
4 of the program if none of the assert()s fired.
6 This is wrong. They should do the test outside of an assert(), and print
7 'ok' or 'not ok' as appropriate, instead of bailing out part way through.
8 That way if a test starts failing we'll know exactly which one failed, and
9 the other tests can continue.
11 This probably means a simple libtest.so that they can link against to
12 provide an ok() function (the non-fatal assert), probably with some helper
13 functions to keep track of test numbers and so on.
17 Any of the tests written in C should link against the libraries under
18 /usr/obj rather than using the system libraries.
22 Not everything's been converted to the new style. In particular;
35 needs to be converted. And fsx/ and gaithrstress/ are (I think) standalone
36 programs rather than individual tests, so aren't amenable to this sort of