All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schweikert <rschweikert@novell.com>
To: alsa-devel@alsa-project.org
Subject: LSB inclusion of ALSA
Date: Fri, 12 Jun 2009 13:56:32 -0400	[thread overview]
Message-ID: <4A3296D0.4080701@novell.com> (raw)

Hi,

Currently ALSA is a trial use module for LSB
(http://www.linuxfoundation.org/collaborate/workgroups/lsb) 4.0 and it
is the intention to make ALSA mandatory with the LSB 4.1 release
targeted for Q1 2010. One of the requirements of a mandatory module is
the existence of a test suite for the module that covers a good chunk of
the interfaces provided by the LSB spec. An initial exploratory look at
the existing test cases showed that tests appear to be tied to hardware
drivers and are interactive.

Is this initial impression correct?

>From an LSB testing perspective, interface testing is  very important;
i.e. I call the interface with the arguments required and I get the
expected result back. Further the tests need to run in an automated
fashion and produce a certain output (automated processing). The output
can be created by retrofitting existing tests or by specifically writing
tests within the LSB test framework.

IMHO it would be best to have tests that are useful to both, the project
and the LSB and in a best case scenario we wouldn't have to start over
as the existing tests already cover a good part of the interface.

With this as background there are a few questions that have been raised
while discussing this during LSB workgroup sessions.

1.) Is there interest from the community side to participate in this
effort and accept patches?
2.) Is it reasonable to expect that the existing tests can be used in
some way by using a dummy sound device or a sound loop device to verify
output?
One requirement for LSB testing is that a test has only two states, pass
or fail, and a recovery or try again mode is not supported. Further a
test must pass or fail.
3.) Would the community be more comfortable if this is an effort that
creates new tests separate from the existing HW focused tests?
4.) Is anyone interested in helping with this effort, writing tests,
answering questions about ALSA for those not familiar with the interface
and or sound in general?

Comments, thoughts, etc. are much appreciated.

Thanks,
Robert

-- 
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
Software Engineer Consultant                          LINUX
rschweikert@novell.com 
781-464-8147

Novell
Making IT Work As One

             reply	other threads:[~2009-06-12 17:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 17:56 Robert Schweikert [this message]
2009-06-16 11:59 ` LSB inclusion of ALSA Clemens Ladisch
2009-06-17  8:16   ` Takashi Iwai
2009-06-17  8:52     ` Clemens Ladisch
2009-06-19 12:07       ` Robert Schweikert
2009-06-19 12:45       ` Theodore Tso
2009-06-19 13:43         ` Clemens Ladisch
2009-06-19 11:39   ` Robert Schweikert
2009-06-19 13:43     ` Clemens Ladisch

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=4A3296D0.4080701@novell.com \
    --to=rschweikert@novell.com \
    --cc=alsa-devel@alsa-project.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 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.