>>>>> "rw" == Richard Welty <[EMAIL PROTECTED]> writes:
rw> what kinds of testing do you generally want to see done to
rw> verify that cmucl works on a particular platform?
rw> i'd be happy to run some tests if i knew what the requirements
rw> were; i might even volunteer to help out with a canned testing
rw> suite if it were viewed as desirable.
good question, and it would be useful to have a well-defined procedure
for this. Being able to rebuild itself is quite a good test: it means
that the FFI works, the compiler isn't completely broken, it survives
garbage collection (so signal handling probably works), and genesis
works.
Here are some further points that aren't covered by a rebuild:
- undefined-symbol-handler: check that typing an undefined symbol
into the listener signals the right error
- LOAD-FOREIGN mechanism: try loading a .a library, a .so library
without dependencies, and a .so library with dependencies, and
check that you can call functions from each
- check that each of the commandline options works as advertised
- play around with the debugger (esp with the CMUCL source code
installed) and check that "stuff" works
- check that CLX works with your X11 server and window manager (for
example try running Fred Gilham's inspector [1])
- check that the Motif interface works, for example by playing
around with the Motif inspector or debugger
- check that SERVE-EVENT works ok (eg using a tcp-forwarding
program [2])
- check that the internet-networking functionality works (eg make a
HEAD request to a web server)
- testing the FFI: try the tcl-callback example from the CMUCL web
site
- as a stress test, try running the cl-bench performance benchmarks [3]
and check that performance hasn't degraded catastrophically
- as an integrity check, try certifying the books in the ACL2 proof
assistant [4]
You might also be interested in some elements of the SBCL test suite,
that includes automated functional, non-regression and stress tests.
[1] clos-inspect <URL:http://www.mail-archive.com/[email protected]/msg00423.html>
[2] tcp-forwarding <URL:http://www.chez.com/emarsden/downloads/>
[3] cl-bench <URL:http://www.cons.org/cmucl/benchmarks/>
[4] ACL2 <URL:http://www.cs.utexas.edu/users/moore/acl2/>
--
Eric Marsden <URL:http://www.laas.fr/~emarsden/>
