All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Q: Is there a testsuite?
Date: Wed, 11 May 2005 15:27:31 +0200	[thread overview]
Message-ID: <s5hll6l28qk.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050510175307.09923120.erikd-alsa@mega-nerd.com>

At Tue, 10 May 2005 17:53:07 +1000,
Erik de Castro Lopo wrote:
> 
> 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.

Right, but a problem is that the audio test is not always self
consistent.

Anyway, a set of sample audio data (or wave/noise generators) in
different settings (rates, formats, channels, etc) would be useful for
playback tests.  Any volunteers?

But the capture tests are more difficult (from the generalization
perspective)...


Takashi


-------------------------------------------------------
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

      reply	other threads:[~2005-05-11 13:27 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
2005-05-11 13:27     ` Takashi Iwai [this message]

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=s5hll6l28qk.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=erikd-alsa@mega-nerd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.