From: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Q: Is there a testsuite?
Date: Tue, 10 May 2005 17:53:07 +1000 [thread overview]
Message-ID: <20050510175307.09923120.erikd-alsa@mega-nerd.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0505091042490.20877-100000@studcom.urz.uni-halle.de>
Clemens Ladisch wrote:
> P. Christeas wrote:
> > I was wondering if there is some ALSA testsuite,
>
> There are some programe in alsa-lib/test/, but those are for testing
> the ALSA library.
>
> > that will detect if -my- soundcard covers all the ALSA
> > functionality it exports with some X kernel.
>
> Sound card capabilities are too different to be able to create a test
> suite that fits all.
A test suite is well within the realms of possibility and saying
its not possible only discourages people from trying.
A generalised test suite would be of great benefit to the ALSA
project.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"I could never learn to use C++, because of the completely
overwhelming desire to redesign the language every time I tried
to use it, but this is the normal, healthy reaction to C++."
-- Erik Naggum
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
next prev parent reply other threads:[~2005-05-10 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 9:31 Q: Is there a testsuite? P. Christeas
2005-05-09 9:30 ` Clemens Ladisch
2005-05-10 7:53 ` Erik de Castro Lopo [this message]
2005-05-11 13:27 ` Takashi Iwai
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=20050510175307.09923120.erikd-alsa@mega-nerd.com \
--to=erikd-alsa@mega-nerd.com \
--cc=alsa-devel@lists.sourceforge.net \
/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