From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: What test suites can you tell me about?
Date: Sat, 06 Jan 2001 23:21:31 +0000 [thread overview]
Message-ID: <3A57A87B.BA60FF9B@goingware.com> (raw)
Can you tell me about any ready-to-use test suites, for any software package
that should run under Linux, that I can build and run to test the new kernel?
Besides running all these tests myself on my machine, I'm going to document them
in an article at:
http://linuxquality.sunsite.dk/articles/
(there are no articles there yet but I'm composing a couple that will be posted
soon)
For example, if you build Python (http://www.python.org) and say "make check",
it will run a bunch of python programs that test the correctness of the
programming language.
This is of interest in part because lots of the Python tests make system calls,
but also because it tests that the compilers generate correct code under the new
kernel (another test I do is, after I boot off a new kernel, I do "make clean",
build it again and boot off _that_).
"make exec" under the Mesa 3.4 library builds a bunch of graphics demos, a few
of which are kind of whizzy but most of which exercise a few basic functions in
OpenGL. So one can watch that they don't crash, that the images look correctly
drawn and so on. This enabled me to realize that DRI wasn't working under 2.4.0
but it was under 2.4.0-prerelease-ac5, which I've detailed in a separate
message.
Another test suite I know about comes with Kaffe (http://www.kaffe.org) and
verifies that Kaffe's implementation of Java is running correctly on your
system.
One I read about somewhere but have no clue where to get it is this memory
stress-testing tool that does lots of DMA and stuff off of the disks.
There must be a lot of these tools available, if only we had them listed all in
one place.
If you maintain such a test tool, it would be helpful if you provided the option
to run the whole suite completely unattended. Mesa provides a good test for
lots of functions of the kernel, but one problem is that one has to quit the
tests after each one runs, usually by pressing the ESC key. Unattended testing
also allows one to run lots of tests simultaneously to test a heavily loaded
system.
In some cases, the tests really do need to have some user input, like navigating
around a 3D world or turning various rendering options on and off, but it's
possible the tests could be extended to allow this input from a script (Python
provides a nice way to bolt a script interpreter to any application).
Mike
--
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-07 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 23:21 Michael D. Crawford [this message]
2001-01-07 19:56 ` What test suites can you tell me about? Nathan Straz
-- strict thread matches above, loose matches on Subject: below --
2001-01-07 5:34 Dan Kegel
2001-01-07 17:46 Michael D. Crawford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A57A87B.BA60FF9B@goingware.com \
--to=crawford@goingware.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox