Re: [web-audio-api] Browser support tests

Hi Chris,
Thanks for your feedback and the information!

I've looked through the web-platform-tests repository, trying to see
how/if the tests I wrote could fit in.
It seems like my tests are a bit redundant to the Web IDL tests role,
testing only the interface definition. When I looked at those those
tests briefly before, I assumed they are just parsing tests for the
IDL parts of the specification.

My tests rely on a definition of (a small subset of) spec, defined in
It is also much less strict than those tests, allowing to give
alternative names to attributes, and not checking the prototype, but
just the instances.
Overall, it's more about checking the common functionality in
implementation, and less the strict adherence to the spec. It's also
written in a way that allows easy feature detection (i.e. checking
something like
webAudioCapabilites("AudioContext.createOscillator.type.isEnum")), and
reporting the results to an external source.

So perhaps it's better to extend the web platform IDL tests. Am
looking at this now, will have a follow up on a different thread.
However, augmenting the tests I've created and integrating them would
probably be something I can get done earlier. Are all tests expected
to use W3C's test harness?

Regarding the other idea, synthesizing the results into a caniuse like
report, some questions (some are pretty open):
Is there now a single runner for all the tests?
Should something like this be part of the web platform tests?
What might be a good subset tests to synthesize such a feature support list?


On Mon, Oct 21, 2013 at 4:33 PM, Chris Lowis <> wrote:
> Hi Amitay,
> Fantastic work! Thanks for sharing.
> We'd be delighted for some more help in testing the web audio API.
> There's some basic instructions and the repo here:
> There's also a few tests of the GainNode to show the testing style.
> Perhaps you could have a quick poke through the repo first before we
> chat more, but the basic procedure is
> 0) Ask on this list first in case anyone else is working on something
> [optional, but could save wasted effort]
> 1) Fork the repo and add your tests in a feature branch
> 2) Send a pull request
> 3) Someone from the WG (currently me) will review your PR
> There's a large existing body of tests in the webkit/blink repo and
> the mozilla repo that we would like to port over, so incorporating
> some of those with your tests would be a great place to start - I can
> help you with that once you've taken a look.
> Also - it would be great to synthesise the test results into a simple
> "can I use this"-type report, similar to what you have done, so
> perhaps we can work on that too in the future.
> Cheers,
> On 18 October 2013 18:18, Amitay Dobo <> wrote:
> > Hello,
> > I've created a small test suite to test and collect test results for Web
> > Audio API support in browsers:
> >
> > The code is available at
> >
> > It is intended to test the existence and structure of the API (currently a
> > subset of it). I've tried to make it in a way that will allow to declare a
> > larger portion of the API.
> >
> > Would be happy to hear some feedback. I'd also like to hear if it is
> > something that should be integrated in the Web Platform tests. If so, any
> > suggestions as to what and how are be welcomed.
> >
> > Cheers,
> > Amitay Dobo

Received on Monday, 21 October 2013 19:31:33 UTC